ยทNew FlutterFlow user August 2024 Deciding if this is my new dev platform.

Are Action Blocks supposed to simply halt all code execution when a Firebase Doc "read" is not found?

Database & APIs

24hrs and no response from FlutterFlow support, so perhaps I'll get a quicker response here. Is > 24hrs normal? Should I have assumed FlutterFlow support is overwhelmed and always post here first?

I have a valid use case where my logic may attempt to read a document via its ID from Firebase and that document may not exist. I have added conditional logic following the "read" to check for document "if exists" however the conditional logic appears to never be reached for me to test the result. Instead, it seems like the action block simply halts and I get no handle or try/catch or any way to continue to handle the scenario. It just drops dead. I have added "Update App State" steps after every "real" step in my action block where I write debugging text into an App State variable (so I can see it in the debugger...it's a lot more reliable than "snackbar"). to pinpoint this issue and I am confident my conditional test for the existence of the requested firebase document is never executing. Is this a known issue, or if this is by design, then why does the "document exists" boolean appear in the selector? (It is difficult to provide a screen-shot since this "Support Request" window kind of has a modal lock on my Flutterflow screen so I can't position my editor window to make the screen-shot." I have reviewed documentation as well as I am able on this.

What have you tried so far?

I added a bunch of debug statements to trace and prove that the action block simply stops executing. I isolated the code for FB read in its own Action block to prove that the entire program stack of action blocks also halts (in other words I could not depend on isolating the FB read that is not finding the document by its ID in its own action block and then catch it from the caller action block). I was hoping to create some type of "try/catch" logic.

Did you check FlutterFlow's Documentation for this topic?
Yes
1
1 reply