[ECO-4875] fix: out of sync message handlers #537
Merged
+1
−1
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.
Resolves #531
Makes
StreamsChannel#_lastId
field static, because:During hot reloading, the Ably instance can be recreated.
StreamsChannel#_lastId
field is used to create IDs for platform-specific subscriptions, which are used on iOS and Android. Code that used to register subscription handler is a singleton, so two Ably instances overwrite each other, causing the platform implementation to be out of sync with the Flutter message handler.