fix: consume direct flow to preserve behvior or app lifecycle observer (WPB-22609) #4508
+32
−28
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.



PR Submission Checklist for internal contributors
The PR Title
SQPIT-764The PR Description
What's new in this PR?
Issues
Observing the user accounts and triggering sync after certain login scenarios does not work.
Causes (Optional)
Introduced while using explicitApi() and hiding repositories from being accessed.
Solutions
Consume an already created raw sessions flow use case to be consumed by the app, instead of using a differenent source.
Dependencies (Optional)
Needs releases with:
Testing
Test Coverage (Optional)
How to Test
Login using sso flow, and the app should not be stuck on welcome screen.
Attachments
Screen_recording_20260107_125246.webm
PR Post Submission Checklist for internal contributors (Optional)
PR Post Merge Checklist for internal contributors
References
feat(conversation-list): Sort conversations by most emojis in the title #SQPIT-764.