-
Notifications
You must be signed in to change notification settings - Fork 271
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
[V6] StreamOfflinePluginFactory was set at initialization, but the sdk required it #4717
Comments
Hello @workspace, could you share how you're initializing our SDK? I believe you didn't add the state plugin. |
StreamChatInitializer
AndroidManifest.xml
This capture is a diff of a pull request that tested applying v6. If I open it by tapping the app icon, it works fine. However, there is a problem when opening the app through push notifications. |
Hi @workspace If you are using |
ignoring the result and moving directly to the chat.Then, I am watching initializationState before using ChatClient in the screen. |
Thanks for your reply. |
Thanks for the quick fix, I'm really happy to have contributed to stabilizing the STREAM V6 SDK. I can't wait to get the STREAM V6 SDK into my product. 😃 |
@JcMinarro |
@workspace @JcMinarro Thanks bro this helped me |
Describe the bug
I am initializing ChatClient using jetpack app startup library. After completely shutting down the app, clicking the push notification to run the app, and then calling the state-related method(ex. watchChannelAsState), the following exception appears.
It could be a problem with our app's implementation, but we had no issues with v5.
ChatClient initialization and connection was completed before calling watchChannelAsState
SDK version
To Reproduce
(With our implementation)
I'll try to reproduce with stream-chat-android sample
Expected behavior
in v5, there was no problem.
Device:
The text was updated successfully, but these errors were encountered: