Repository navigation
Simplified code to use FCM token type as default - #727
Conversation
martin-morek
commented
Oct 21, 2021
- fixes #703
- By default FCM token type will be used, deprecated GCM type is kept only for cases when it's loaded from storage
|
This is a breaking change and when users update, they will immediately have to change their code. If we deprecate the original method first, temporarily keep the original for a few releases, and add a new method which users should use instead, users will find the version upgrade process more comfortable. |
|
I believe my changes were done carefully mostly affecting codebase creating a new token witch cannot have |
uxduck
left a comment
There was a problem hiding this comment.
Just a couple of comments, thanks :)
…ecated whole Type enum
- Improves the implementation, moving checks up to the LocalDevice. - Adds test coverages for constant FCM values we rely upon going forwards.
|
Emulation failing. 🙄 ... I'm going to have a play in #738 to see if I can get it more stable, before coming back to this PR. |
|
Emulation run failed: |
|
Emulation run failed: |
|
Given the same test failed twice in a row I think it's back to the drawing board with this PR, alas. 😢 |
Remove deprecated test RegistrationTokenTypeTest Refactor token type usage across LocalDevice as FCM only exist Refactor generateSecret method for better try
|
I have removed all instances and mentions of GCM as it is long past deprecated and removed in 2019. |
Co-authored-by: KacperKluka <62378170+KacperKluka@users.noreply.github.com>
…en received can be in any format