Remove utf encoding (it was encoding an already encoded string) #18
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
The current implementation does not allow users to register APNS tokens on iOS.
Flutter is sending an UTF encoded string with the token to the Objective-C code. Objective C is then trying to encode it again and therefore it makes the token invalid.
As an example this APNS token
EEA61818EF32127C34DC65F3C6CE7A61C3EBBB742730292845FC5047D3E1EE3Agets registered in the backend as45454136313831384546333231323743333444433635463343364345374136314333454242423734323733303239323834354643353034374433453145453341which is not valid and delivery fails.