The Following actions after Login Auth action (either custom or Flutterflow native) are never executed as these actions are silently skipped/ignored in action flow

[mkhanm0900]

Can we access your project?

• I give permission for members of the FlutterFlow team to access and test my project for the sole purpose of investigating this issue.

Current Behavior

I have an action flow on login button in entry page. the action flow is set-up in such a way to implement one-user-one-device functionality.
When the "Sign In" button is pressed:

the action flow goes through the following checks

1. Both email and password Text fields are set
2. Device has Internet connectivity
3. then happens Firebase Auth by Custom action (because FF native firebase upon error return snackbar that doesn't suits my app).
   The error/issue remains the same if native Firebase auth is used. Action output variable name is returnAuth
4. if returAuth is valid, email verification is checked if invalid, the user is logged out and asked to verify email. If Valid, the user device id is fetched by custom action(Persistent device id), the custom action output variable name is "persistentDeviceIdOutput"
5. then multiple condition are set to find from firestore field "PersistentDeviceId" 1. whether user is logging in for the first time to assign device id, Update AppState "logged In" to true and navigate to Homepage(which is set as logged In page as well), 2. Persisten device id custom action return Null ----> user is asked to check phone permissions and use non-rooted device, 3. if User firestore field "PersistentDeviceId" is not equal to "persistentDeviceIdOutput" ----> user is logged out and asked to signout of previous session. 4. If if User firestore field "PersistentDeviceId" is equal to "persistentDeviceIdOutput" ---->Update AppState "logged In" to true and the user is navigated to Homepage

This is the set-up action flow but it does not happen so. As auth happens and email-verification and custom action(Persistent device id) executes, the following multiple conditions are never executed and ae silently skipped/ignored and the user is navigated to the set-up logged In Page if that action flow demands to navigate to another page than logged in page.
lets suppose my logged In Page in set Page A in setting but I want to navigate the user from log-In Page to Page B by setting some conditions. these conditions are never executed.

Expected Behavior

Action flow on log-In page button must execute all the actions before navigating to the page but it is never a case as action flow silently skip/ignore following actions as that these actions never exist in action flow.

Steps to Reproduce

I have an action flow on login button in entry page. the action flow is set-up in such a way that
When the "Sign In" button is tapped:

1. Check that the email field is non-empty, the password field is non-empty, and both fields have already passed their individual format validation (formEmail and formPassword are true).
2. If all checks pass, verify there's an internet connection.
   • If there is no internet connection, show a dialog telling the user there's a connectivity issue, then stop.
3. If connected, attempt to authenticate with email/password against Firebase. I am using Custom action auth as FF native auth for firebase return snackbar which does not suit my aesthetics
4. If authentication fails (invalid credentials), show a snackbar telling the user their email/password is invalid or they need to sign up.
5. If authentication succeeds, check whether the user's email has been verified.
   • If not verified, sign the user out, clear any redirect location, and show a snackbar asking them to verify their email via the link sent to them.
6. If the email is verified, fetch a device ID for the user current device using custom action. The action output is named as "persistentDeviceIdOutput".
7. Compare that device ID to the one stored on the user's record "PersistentDeviceId" in Firestore:
   • If the user record has no stored device ID yet as the user is logging for the first time, save this device ID to their record, update the Appstate "LoggedIn" (boolean) to true, and navigate to the fully-completed home page(which is Logged In page as well), passing along the device ID from the action output "persistentDeviceIdOutput" .
   • If the fetched device ID came back as literally 'Null' (a failure case), sign the user out, clear the redirect location, and show a "device verification failed" dialog.
   • If Custom action fetched device ID doesn't match the one already stored on the record, sign the user out and show a "dual session" dialog (implying they're logged in elsewhere on a different device). Stop.
   • Otherwise (the stored device ID matches the fetched one), mark the user as logged in, update the Appstate "LoggedIn" (boolean) to true, and navigate to the fully-completed home page, passing along the device ID.

Reproducible from Blank

• The steps to reproduce above start from a blank project.

Bug Report Code (Required)

IT9fl/KAx5NPxcBE7c+BcvlR/WIsJnI/U5I70u5+GA01F77uOpkhe8zVN1ZAXcCmd0I/ImH8/WcczNbMv97xEMc9GC2eRbo7/7oBVwCUZHqtb6nTEs+WYGJ/J95hGmKk5KaskxB7JsRoSFph1FOmfOuRaAvbGrnhDTEvM/qXA5P/n3S4Gx7vUCAw2W8UIRqSBfQyVwuuuMLJ+dAjlI/S/ol8qBVXzoPSwtX1TBKTWVk=

Visual documentation

Environment

- FlutterFlow version: V7.0.16 released July 1,2026
- Platform: FlutterFlow Local Run setup (Desktop)
- Browser name and version:Google Chrome (Desktop)
- Operating system and version affected: Window 11

Additional Information

#7273

[Juansarmi]

Hi , thank you for bringing this up! This issue has already been reported and is being tracked here: #7273 . Please feel free to refer to that thread for future updates.

I'm going to link this issue to the one already mentioned above. To keep things organized and make it easier to track, I'm closing this one as a duplicate so we can centralize all responses in a single place. Thanks for your understanding!