Skip to content
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

Implement activation/ deactivation/ updating lifecycle method #154

Closed
ben-xD opened this issue Aug 20, 2021 · 1 comment
Closed

Implement activation/ deactivation/ updating lifecycle method #154

ben-xD opened this issue Aug 20, 2021 · 1 comment

Comments

@ben-xD
Copy link
Contributor

ben-xD commented Aug 20, 2021

We need to implement a way of checking when activate/ deactivate succeeds/ fails and to find out when an update with Ably fail. In the current PR #140, users won't know if activation succeeds or fails.

In iOS, ARTPushRegistererDelegate is the delegate with 3 methods which are called back:

  • didActivateAblyPush: called when activate succeeds or fails
  • didDeactivateAblyPush: called when deactivate succeeds or fails
  • didAblyPushRegistrationFail: called when updating Ably with new details fails. The point is, it is only called when updating ably (in an internal method called callUpdateFailedCallback), and not during "registration"/ activation.

In Android, there are 3 intents which are created. The user has to listen to these:

  • io.ably.broadcast.PUSH_ACTIVATE
  • io.ably.broadcast.PUSH_DEACTIVATE
  • io.ably.broadcast.PUSH_UPDATE_FAILED

┆Issue is synchronized with this Jira Task by Unito

@ben-xD
Copy link
Contributor Author

ben-xD commented Sep 5, 2021

This was added in #140, and is now documented in https://github.com/ably/ably-flutter/blob/main/PushNotifications.md#device-activation

@ben-xD ben-xD closed this as completed Sep 5, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

1 participant