Skip to content

Conversation

@charlotteliang
Copy link
Contributor

@charlotteliang charlotteliang commented Apr 2, 2021

Also use GULSecureCoding to encode/decode. This partially fixes #3686.

Tested with previously installed app and fcm token is persisted correctly.

@google-oss-bot
Copy link

google-oss-bot commented Apr 2, 2021

Coverage Report

Affected SDKs

  • FirebaseMessaging-iOS-FirebaseMessaging.framework

    SDK overall coverage changed from 66.01% (0b508f9) to 65.51% (ecfac34) by -0.50%.

    Filename Base (0b508f9) Head (ecfac34) Diff
    FIRMessagingAPNSInfo.m 87.23% 88.00% +0.77%
    FIRMessagingTokenInfo.m 82.78% 77.18% -5.60%
    FIRMessagingTokenManager.m 42.15% 40.60% -1.55%
    FIRMessagingTokenOperation.m 96.84% 95.57% -1.27%
    FIRMessagingTokenStore.m 68.42% 58.93% -9.49%

Test Logs

Copy link
Member

@paulb777 paulb777 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍

@charlotteliang charlotteliang merged commit 34c4bdb into master Apr 5, 2021
@charlotteliang charlotteliang deleted the fm-secure-token branch April 5, 2021 19:55
charlotteliang added a commit that referenced this pull request Apr 8, 2021
charlotteliang added a commit that referenced this pull request Apr 8, 2021
@firebase firebase locked and limited conversation to collaborators May 6, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Various Firebase types does not conform to NSSecureCoding

3 participants