Discard any changes before we delete the persistent state #3170
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.



🎯 Goal
Make sure that changed managed object contexts do not trigger adding new data in
removeAllData📝 Summary
In the state layer branch we have a case where channel was not properly deleted on logout. That branch also has additional managed object context which is aggressively merging changes from other contexts (this seems to be related).
🛠 Implementation
Reset contexts when we logout for making sure we discard any active changes and do not try to save them when later the code path calls
writableContext.save.🎨 Showcase
From:

feature/chat-state-layer🧪 Manual Testing Notes
Follow the steps above.
☑️ Contributor Checklist