-
Notifications
You must be signed in to change notification settings - Fork 136
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
Crash in fetchAuthValue when App is Resumed from Background #187
Comments
I’m not sure if this is related, but when I reopen the app after it has been in the background, I see a series of connection state change logs like this:
Is this expected behavior? As I mentioned, this might not be an issue or even related to the crashes, but I thought it was worth noting while troubleshooting. |
which version of the pusher channel flutter library r u using? |
When I reported this issue, I was using version 2.4.0. However, the same behavior occurs with version 2.5.0. |
Thank you for your response and for offering to help! I also suspected that the issue might lie within my onAuthorizer code. However, after reviewing our server logs, it appears that our Pusher auth endpoint was returning the expected response with a 200 status code and the correct authentication object at the time of the last crash. To provide more context, here is my PusherService class implementation:
|
Description
Our Flutter app sometimes crashes when resuming after being in the background for a while. The issue seems to originate from the fetchAuthValue method in the Pusher library. The crash is related to a dynamic cast failure, as seen in the Crashlytics logs (provided below).
I suspect the issue might be caused by an invalid state or incorrect handling of the authorizer object during app lifecycle changes.
Environment Details
Crash Logs
Here is the relevant portion of the Crashlytics log:
If any additional information is needed, please let us know.
Would appreciate any guidance or fixes from the team. Thanks!
Full Crashlytics Log:
The text was updated successfully, but these errors were encountered: