This repository has been archived by the owner on Nov 1, 2022. It is now read-only.
Check subscription verification immediately after getting a new push token #7237
Labels
🌟 feature
New functionality and improvements
<push>
Components: concept-push, lib-push-adm, lib-push-firebase, feature-push, feature-sendtab
🔬 Research
Problems without a solution that need research.
Comments
jonalmeida
added
🌟 feature
data-sync-user
changed the title
data-sync-user
changed the title
st3fan
changed the title
|
Moved to bugzilla: https://bugzilla.mozilla.org/show_bug.cgi?id=1796427 Change performed by the Move to Bugzilla add-on. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
When we get a push token, we wait to check our subscriptions when we next re-open the app (with
initialize) and we haven't done a check recently (~24 hours). We could consider doing this check immediately after updating the token in the native layer inonNewToken.I'm a little unsure if we should do this now. If we can verify the system works as expected after #7143 is fixed, we can consider doing this after the Fenix release.
We do however have our
VerificationDelegateto avoid us DDOS-ing our push servers if something goes wrong with our FxA servers, so there is safety there.┆Issue is synchronized with this Jira Task
The text was updated successfully, but these errors were encountered: