Remove migration from legacy keychain #5237
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…if user is updating from a very old version of FCM, however
paulb777
reviewed
Mar 31, 2020
paulb777
approved these changes
Mar 31, 2020
pranavrajgopal
pushed a commit
that referenced
this pull request
Apr 8, 2020
ryanwilson
pushed a commit
that referenced
this pull request
Apr 24, 2020
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
This was used to migrate checkin info for users who use a very old version of fcm or gcm to newer version. However, because most users have migrate off gcm and we no longer log substantial data in checkin, so it wouldn't hurt for small amount of users who get a new checkin and accordingly a new refresh token when updating.
This also reduce number of keychain read write operations during first app install.
Also update changelog for release.