-
Notifications
You must be signed in to change notification settings - Fork 90
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Multi forking root saga #1970
Comments
@siepra I didn't notice any improvement in [email protected] (iOS 340). Do you have some other ideas what may be causing this problems? |
Initially I thought it was the problem with web socket client connection, but it's actually the problem with redux persist being purged when leaving community. EDIT: I performed tests including commenting out pausing, flushing and purging redux persist. It seemed to make no impact |
This will affect users leaving and rejoining communities who do not "swipe up" or close the app after leaving and before re-joining a new community. @siepra will add notes about what he's found so far. |
My observation is, once left the community state-manager root saga is being forked multiple times:
It's as though multiple apps were running concurrently, sharing the same UI |
I observed web socket client connecting more than once. I think it has something to do with connection-manager's
The issue appears on both platforms so I assume the problem is not related to lifecycle changes, yet Kinga first observed it on iOS which directly calls It's easiest to reproduce when combined with leaving the community. It executes It looks like even though it closed socket server, it reconnects the old client's socket under certain conditions (which I'm trying to figure out). Is that even possible? @EmiM There's a quicker way to observe this behaviour on iOS (although it probably won't break anything but it'll show results in logs):
Here are shorten logs I got during debugging
Here's a branch containing additional loggings #2154 |
Details moved to #2253 |
* fix: mark redux store ready after leaving community #1970 * test: fix deepLink tests * chore: fix lint * chore: cleanup * chore: update CHANGELOG.md * chore: add debugging logs * fix: reset deep link flag * chore: cleanup iOS * fix: correct redux cleanup order * chore: comment out persistor flushing * chore: add debug log for launching application * chore: log socket id on its lifecycle callbacks * fix: deep link redirection * fix: undo comment out persistor cleanup * fix: tests * fix: lint * chore: undo CHANGELOG.md changes * chore: update CHANGELOG.md * chore: cleanup * chore: cleanup
Version: [email protected]
System: iOS and android (but less common)
What happen - user is stuck at thee beginning of joining proces after very specific conditions are fulfilled
Steps to recreate:
App should recognize that this is the code to join community and proceed with the usual flow)
Edit: Initially I thought that it happens only on ios but I've spotted it on android as well, even without changing to "create community".
Edit2 (29 Nov): it happens especially often when the user leaves and tries to re-join community.
The text was updated successfully, but these errors were encountered: