Signal 7.29 crashes directly when started on iOS 18

signalapp / Signal-iOS

A private messenger for iOS.

https://signal.org

GNU Affero General Public License v3.0

10.83k stars 3.04k forks source link

Signal 7.29 crashes directly when started on iOS 18 #5875

Closed danpfe closed 1 month ago

danpfe commented 1 month 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

App immideatelly closes on an iOS 18-phone (fresh install on new phone). Seems very similar to https://github.com/signalapp/Signal-iOS/issues/5796, but since that seems fixed it may be a different issue when installing fresh on iOS 18.

Steps to reproduce

Install app fresh from App Store
Tap the app icon

Actual result: Crashes/Closes instantly

Expected result: App should open

Screenshots

Device info

Device: iPhone 15 Pro Max

iOS version: 18.0

Signal version: 7.29

Link to debug log

katosdev commented 1 month ago

I also get the same issue, also on an iPhone 15 Pro Max

antoinedesp commented 1 month ago

Same issue, lost all messages conversations and contacts trying to uninstall and reinstall. WTF devs????!!!!

danpfe commented 1 month ago

Managed to get out debug log and see that it segfaults seemingly due to accessing an instance of a class that is not available.

IPS-file in this GIST: https://gist.github.com/danpfe/1abd891c3d8dae3069cc128c0f2ea32a

pete-signal commented 1 month ago

The crash report indicates you're running an iOS18 beta - could you update to the released version of iOS 18.0 and see if this helps?

danpfe commented 1 month ago

@pete-signal Funny, that did the trick. I did see it also in the IPS-file and I was surprised of it myself. I checked several times in the update-dialog if Beta was activated or if there was an update after seeing it but only yesterday it showed another update.

To the others (@antoinedesp @katosdev) having the same problem: Check again, maybe there was something borked up in the roll-out to your phones as well (or accidentally having Beta activated) and something went wrong when you updated previously. It works for me now.