Open kristoflievens opened 1 month ago
Hello!
I haven’t tested this myself yet, but I’ve reviewed the project you provided. Have you tried setting a conditional to check if the ID is set before attempting to read the document? Additionally, after triggering the alert dialog, did you verify if the document exists?
Hi @Alezanello,
The ID exists, but that's not really the point, because the ID is pointing to a non-existing document.
Additionally, after triggering the alert dialog, did you verify if the document exists? -> yes, but that code is never executed, so it is of no use
This issue is stale because it has been open for 7 days with no activity. If there are no further updates, a team member will close the issue.
Hi @Alezanello , do you need additional input on this issue? Are you able to reproduce it?
This issue is stale because it has been open for 7 days with no activity. If there are no further updates, a team member will close the issue.
I'm running into the same issue.
Can we access your project?
Current Behavior
When performing a Firebase read document backend call in an Action flow for a document reference that no longer exists the following excpetion is thrown: DartError: TypeError: null: type 'Null' is not a subtype of type 'Map<String, dynamic>' when reference doesn't exist
The Action flow stops further processing and doesn't allow to handle this error further down the flow.
Expected Behavior
The Firebase read document backend call Action should return null via the Ouput Variable instead of crashing
Steps to Reproduce
Reproducible from Blank
Bug Report Code (Required)
IT4wl8nfsM9NsdtJ7ZPud8dFmioRMjs7ROYe0+t9aCs9f5ToPJYQe8/6P0xoQtfkdFZAPmGmp14epMLSidrIUOwqGEicUaZJwqgJUwr/TnqiacyTF7qwdUd6JJpTf0i75p+rvSJDJrNaZUYf12CmPt+yZHPDQ5iyPno8Sq/LZO4=
Visual documentation
Environment
Additional Information
This bug makes it impossible to properly handle errors related to references between documents in different collections that have been deleted.