-
Notifications
You must be signed in to change notification settings - Fork 493
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 notifications are spontaneously disabling themselves #2348
Comments
The last rageshake (https://github.com/matrix-org/riot-ios-rageshakes/issues/2064#issuecomment-477110654) is interesting but we miss logs to determine the issue root. |
element-hq/element-ios#2348 Do not reset MXKAccount.enablePushKitNotifications when trying to refresh pushkit pusher at startup. If the requests fails, the app will consider that push is disabled whereas there is still a pusher on the homeserver. This is visible at element-hq/element-ios-rageshakes#2618 where the user gets pushes whereas the app setting says there are disabled. Old logs of element-hq/element-ios-rageshakes#2615 show the same thing but on the last app update, the user lost pushes probably because of lack of refresh of the pusher because MXKAccount.enablePushKitNotifications was NO for a long time.
The root bug is around the notification setting at the app level. It has been fixed by matrix-org/matrix-ios-kit@8c6ac9b. If your notification setting is on in Riot 0.9.0 and later, it will no more spontaneously disable itself. If your pushes stopped to work when updating to Riot 0.9.0, that means you were impacted by this bug. Re-enable the notification in the app settings. This setting should never go anymore |
We have a regression causing push notifications to silently disable themselves (causing the toggle in Settings to be 'off'). It doesn't seem to be related to updating the app.
Examples i've seen first hand are https://github.com/matrix-org/riot-ios-rageshakes/issues/2157 and https://github.com/matrix-org/riot-ios-rageshakes/issues/2064, although there have been many others. It seems to have started around 0.8.2 or 0.8.1.
The text was updated successfully, but these errors were encountered: