-
Notifications
You must be signed in to change notification settings - Fork 343
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
type '_$Loading<int, Channel>' is not a subtype of type 'Success<int, Channel>' in type cast #1894
Comments
This issue is stale because it has been open for 20 days with no activity. |
bump |
Having the same issue here |
This issue is stale because it has been open for 20 days with no activity. |
This issue was closed because it has been inactive for 7 days since being marked as stale. |
This issue is stale because it has been open for 20 days with no activity. |
This issue was closed because it has been inactive for 7 days since being marked as stale. |
This issue is stale because it has been open for 20 days with no activity. |
Which packages are you using?
stream_chat, stream_chat_flutter, stream_chat_flutter_core, stream_chat_persistance, stream_chat_localizations
On what platforms did you experience the issue?
iOS, Android
What version are you using?
stream_chat_flutter: 8.0.0-beta.2
stream_chat_localizations: 8.0.0-beta.2
stream_chat_persistence: 8.0.0-beta.2
What happened?
We see this crash in our production apps, but don't know when and why it is occurring:
We use a
StreamChannelListController
to display a list of channels in our app.Steps to reproduce
I can't reproduce this locally at the moment, but in all crashes we see we record a "foreground" or a "DEVICE_IDLE_MODE_CHANGED" (on android) event always right before this crash occurs.
Supporting info to reproduce
This is our my_channels_bloc, which us responsible for getting the list of channels to show
MyChannelsBloc Code
Relevant log output
No response
Flutter analyze output
No response
Flutter doctor output
No response
Code of Conduct
The text was updated successfully, but these errors were encountered: