Login / Signup flow seems broken

[psrsingh]

🐛 Describe the bug

I’m unable to reliably sign up or log in to the app.

When trying to create an account or log in with an existing one, the app sometimes silently fails and returns to the landing screen instead of continuing to onboarding/home.

From debugging, it looks like there may be a race condition in the auth flow:

• AppwriteService.getAccount() can be called before the Appwrite client is initialized
• splash screen navigation may happen before auth state checking finishes
• FCM token update logic during login may also interrupt the flow

Steps to reproduce

1. Open the app
2. Try creating a new account
3. Or log in with an existing account
4. Observe that auth does not complete properly and navigation resets

Observed result

• Login/signup does not consistently succeed
• User may get redirected back to landing
• Session appears to be created sometimes, but auth state/navigation does not complete correctly

Relevant code path

await account.createEmailPasswordSession(
  email: email,
  password: password,
);

await isUserLoggedIn();

There also seems to be an issue where getAccount() accesses _client before initialization is complete.

No clear UI error is shown, so the failure is mostly silent.

[github-actions]

👋 Hello @psrsingh!
Thank you for opening this issue. Our team will review it soon. 🚀

• If you can, please provide more details like steps to reproduce, expected vs. actual behavior, and screenshots (if applicable). 📌

We appreciate your contribution! 💡

[VanshajPoonia]

@Mayank4352 Can I please work on this issue

[Mayank4352]

Hey @VanshajPoonia, @psrsingh has opened this issue and he might be working on this.
Also @psrsingh, I'm not able to reproduce this issue can you share a video for the same??

[VanshajPoonia]

Sounds fair @Mayank4352, is there any doc that I can refer to for the rules for example,

• After what amount of time of inactivity, the issue gets assigned to someone else
• I am coming here from PictoPy, so there, the maintainer explicitly assigns you the issue. In this case, that led to a confusion for me, making me think this was an unassigned issue no one was working on
• Do we have to seek maintainer's permission before working on an issue?
• Is it automatically assumed that the person who opened the issue, is the one working on it?

[Mayank4352]

You can refer to CONTRIBUTING.md. Yes, issues are assigned here. If @psrsingh is inactive and doesn't respond, feel free to work on this issue.

[VanshajPoonia]

@Mayank4352 , it seems like @psrsingh is spamming a lot of PRs in repositories and then eventually closing them. May I work on this issue? It has been 5 weeks since it was opened.

[Mayank4352]

Hey @VanshajPoonia, We're in the middle of architectural migration and this issue is already fixed in that

[VanshajPoonia]

Thanks for letting me know @Mayank4352

[Mayank4352]

closing as resolved

[github-actions]

🔒 Issue Closed - Thank You, @Mayank4352!
This issue has been resolved or is no longer relevant.

• If you have further questions, feel free to open a new issue. 💡

Thanks for helping improve the project! 🚀