-
Notifications
You must be signed in to change notification settings - Fork 25
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Push device deregistration does not clear/ reset device details #1177
Comments
Isn't |
I'm not sure what you're saying @maratal, can you clarify? 🙂 |
@ben-xD couldn't you play with PR branch? push-interactive-app is so lame, it requires a lot of work to fix it (I'm into it now). Thanks. |
I initially didn't understand Marat's comments but he clarified it with me.
He said this is an outdated comment and not relevant anymore.
He wants me to test it in Ably-Flutter because https://github.com/ably/push-example-ios is not well written, and we definitely agree it needs significant improvements. |
Reopening due to #1272 |
…e details) and only resets clientId, since it affects push device registration with a different clientId (after deregistration with previous clientId). This only affects clients that do not restart their apps after deregistration, since clientId is loaded into deviceId once per app launch. This commit resets clientId after deregistration.
…e details) and only resets clientId, since it affects push device registration with a different clientId (after deregistration with previous clientId). This only affects clients that do not restart their apps after deregistration, since clientId is loaded into deviceId once per app launch. This commit resets clientId after deregistration.
…e details) and only resets clientId, since it affects push device registration with a different clientId (after deregistration with previous clientId). This only affects clients that do not restart their apps after deregistration, since clientId is loaded into deviceId once per app launch. This commit resets clientId after deregistration.
Partially fixed by #1832 |
…ar device details) and only resets clientId, since it affects push device registration with a different clientId (after deregistration with previous clientId). This only affects clients that do not restart their apps after deregistration, since clientId is loaded into deviceId once per app launch. This commit resets clientId after deregistration." This reverts commit bff9205.
This is quite low priority, but here it is:
As per RSH3g2a:
Unfortunately, ably-cocoa does not clear local device details.
In Java, this can be seen by:
https://github.com/ably/ably-java/blob/2b8e3c7e65ee7109f225cad115df38d61869fc3f/android/src/main/java/io/ably/lib/push/ActivationStateMachine.java#L483
Ably-cocoa does not even have a method to reset the device details, and so is definitely not calling this.
This can be seen functionality in the Ably flutter app, in the following recording:
Screen.Recording.2021-09-14.at.15.03.47.mov
APNs device token (registration tokens on Android)could be different. The APNs device token on iOS and FCM registration token on Android remains the same. A different APNs device token might be possible on iOS, potentially by callingunregisterForRemoteNotifications
. You could test this.Note on the flutter app: The app is just calling the device method to show the device information.
┆Issue is synchronized with this Jira Bug by Unito
The text was updated successfully, but these errors were encountered: