You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Notifications are delivered over Firebase messaging so they require at least sandboxed Google Play services (e.g. on Graphene OS) to work. Token undefined means, that device token can not be retrieved and thus push notifications + data push messages necessary for Nostr Wallet Connect won't work.
data push messages necessary for Nostr Wallet Connect won't work.
Noticed that app ended up after installing with App Battery Usage: Optimized and therefore restricting background activity unless explicitly whitelisted (afaik that is OK for installation).
But noticed that NWC does not succeed at all (no notification is shown for minutes..) unless I do that manually.
(The NWC request originating in one profile and Minibits installed in another one for FMC to work with.)
Will be great if there is more explicit info letting user know - pushing him to do this whitelisting (switching for Unrestricted).
There is sort of a hint but it's hidden behind 'Show more'.
Would like to have this seamless as possible so do not care about battery drain.
Maybe this will help with experience as well (in my case it's must have otherwise with defaults - no zap get through).
Settings menu shows under the "Push notifications" entry:
"Token undefined"
Toggling off/on makes no difference.
Notifications seem to be broken.
The text was updated successfully, but these errors were encountered: