No Push Notifications since upgrade to iOS 13

lorenzhs commented 4 years ago

[x] I have searched open and closed issues for duplicates
[x] I am submitting a bug report for existing functionality that does not work as intended
[x] This isn't a feature request or a discussion topic

Bug description

Since the day of the upgrade to iOS 13, I don't receive push notifications for messages any more. I sometimes get notifications hours later. Upon opening the app, all outstanding messages are received and I get the notifications for them.

This includes sync with the Desktop app: if I have an unread message on iOS (sometimes they do arrive, typically hours late) and open the Desktop app, Signal-iOS does not update its notification state. Only when I do open the iOS app does it update the state, marks the message as read, and syncs any other messages sent (via Desktop) and received in the meantime. (This is not really surprising, since signalling between Desktop and mobile uses the same mechanism, I just wanted to clearly rule out the Desktop app as a cause)

Steps to reproduce

Unclear. I never had issues using iOS 12, but since the day I updated to iOS 13 the issue has been present. There was no point in time where I was using iOS 12 and the issue was there, and at no point since the update to iOS 13 has it not been there, so I suppose (without hard proof) that somehow was the trigger. However, friends who also updated to iOS 13 report that everything works fine for them.

Actual result: Not receiving push notifications

Expected result: Should receive push notifications for incoming messages.

Re-registering for push notifications in the advanced settings tab does not help. A soft wipe of the phone ("Reset all settings") causes Signal to re-request notification permissions from the system, but doesn't help either.

Screenshots

N/A

Device info

Device: iPhone 7

iOS version: 13.4, issue first appeared with 13.0 and was also present in 13.1, 13.2, and 13.3 (including their point releases)

Signal version: 2.43.3.1 – 3.7.1.0, plus some earlier versions

Link to debug log

https://debuglogs.org/58c7e0894ea57f59f53b473ad7c079e5fe77a0e5ed01f69f4d0b41cd66f0a285.zip (it's a few days old, only got around to filing the issue now. It still persists.)

https://debuglogs.org/18e866c013e3fc0f6be7b7954f0d5978c7e9474e9db6b0be537867cbedc77074.zip is a recent minimal example using 2.45.0.

I think 2019/10/02 17:59:25:334 is a good example, where three hours after last sending a message Signal suddenly receives a bulk of outstanding messages, starting with [AppDelegate.m:1186 -[AppDelegate application:performFetchWithCompletionHandler:]]: performing background fetch. ~~To my layman's eyes, this looks like Signal is falling back to websockets instead of the Apple Push mechanism, but I may be wrong.~~

Also, this is unrelated to #3474, #2312, etc – I'm using the official app store app, not a custom build.

stale[bot] commented 2 years ago

Is this still relevant? If so, what is blocking it? Is there anything you can do to help move it forward?

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.

T4cC0re commented 2 years ago

Seems to stil being an issue in #5072

stale[bot] commented 2 years ago

Is this still relevant? If so, what is blocking it? Is there anything you can do to help move it forward?

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.

NiklasBr commented 2 years ago

This is still relevant

stale[bot] commented 1 year ago

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

NiklasBr commented 1 year ago

This is still relevant, annoying bot.

stale[bot] commented 1 year ago

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

NiklasBr commented 1 year ago

If the annoying bot could stop, that would be nice. This is still relevant.

lorenzhs commented 1 year ago

@NiklasBr if you have an old iPhone that still works or know someone who does, you can transfer your signal data to that other phone, reinstall the app locally, and transfer it back. That should fix the notification issue without any data loss. Beware that the transfer can take some time if your message history is large - expect it to take an hour or so. It's tedious, but it's a workaround.

stale[bot] commented 1 year ago

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

T4cC0re commented 1 year ago

I cannot confirm that transferring to a different iPhone helps, as per my previous comment further up.

lorenzhs commented 1 year ago

Then your issue may have similar symptoms, but it's a different issue. This one is about no notifications at all, not just no notifications for some contacts

jimio-signal commented 1 year ago

dropping my note from #5148 on here too:

hey all! we’ve made some improvements to notification reliability recently, and I’m wondering if the folks that were having problems in this thread could update to the latest version from the appstore, launch the app, and see if it puts you back in business 😎

if not, you might also try manually navigating to Settings / Notifications / Re-register Push Notifications

but, we’d love to see some updated debug logs from y’all if the problems persist. thanks! 🙏

signalapp / Signal-iOS