element-ios icon indicating copy to clipboard operation
element-ios copied to clipboard

Element-iOS crashed everytime when I tried to start it.

Open Shiroiame-Kusu opened this issue 2 years ago • 7 comments

Steps to reproduce

  1. Start Element-iOS
  2. See the logo
  3. Crash in 1 second.

Outcome

What did you expect?

Start and work normally

What happened instead?

Crashed.

Your phone model

iPhone 6s / iPhone 12

Operating system version

iOS 15.6.1 / iOS 16.0

Application version

Element version 1.9.5

Homeserver

Synapse 1.65.0

Will you send logs?

Yes

Shiroiame-Kusu avatar Sep 17 '22 02:09 Shiroiame-Kusu

Here are the Crash Logs. Element.zip

Shiroiame-Kusu avatar Sep 17 '22 02:09 Shiroiame-Kusu

Unrelated issue (#6728) Screen Shot 2022-09-19 at 7 59 37 AM

toshanmugaraj avatar Sep 19 '22 05:09 toshanmugaraj

@toshanmugaraj That is a different issue seen when using Xcode 14 instead of 13 and was fixed by #6728.

pixlwave avatar Oct 04 '22 11:10 pixlwave

Extracted from the crash logs:

Last Exception Backtrace:
0   CoreFoundation                	       0x18174bd1c __exceptionPreprocess + 216
1   libobjc.A.dylib               	       0x198f6bee4 objc_exception_throw + 56
2   CoreFoundation                	       0x18181c75c +[NSObject(NSObject) _copyDescription] + 0
3   CoreFoundation                	       0x1816e561c ___forwarding___ + 1472
4   CoreFoundation                	       0x1816e482c _CF_forwarding_prep_0 + 92
5   libswiftCore.dylib            	       0x186014fa4 specialized _withCocoaASCIIPointer<A>(_:requireStableAddress:work:) + 56
6   libswiftCore.dylib            	       0x186015154 _bridgeCocoaString(_:) + 148
7   libswiftCore.dylib            	       0x186015334 String.init(_cocoaString:) + 24
8   libswiftFoundation.dylib      	       0x185b5fe18 static String._unconditionallyBridgeFromObjectiveC(_:) + 32
9   MatrixSDK                     	       0x103bab9a0 @objc MXCoreDataRoomSummaryStore.summary(ofRoom:) + 36
10  MatrixSDK                     	       0x103b5330c -[MXSession roomSummaryWithRoomId:] + 144
11  MatrixSDK                     	       0x103b4b82c -[MXSession updateSummaryDirectUserIdForRooms:] + 264
12  MatrixSDK                     	       0x103b42898 __59-[MXSession handleSyncResponse:completion:storeCompletion:]_block_invoke + 2612
13  MatrixSDK                     	       0x103b4ba08 -[MXSession handleToDeviceEvents:onComplete:] + 204
14  MatrixSDK                     	       0x103b41e04 -[MXSession handleSyncResponse:completion:storeCompletion:] + 820
15  MatrixSDK                     	       0x103b48ef0 __83-[MXSession serverSyncWithServerTimeout:success:failure:clientTimeout:setPresence:]_block_invoke.697 + 968
16  libdispatch.dylib             	       0x18140b094 _dispatch_call_block_and_release + 24
17  libdispatch.dylib             	       0x18140c094 _dispatch_client_callout + 16
18  libdispatch.dylib             	       0x1813b8d44 _dispatch_main_queue_drain + 928
19  libdispatch.dylib             	       0x1813b8994 _dispatch_main_queue_callback_4CF$VARIANT$mp + 36
20  CoreFoundation                	       0x1817070d4 __CFRUNLOOP_IS_SERVICING_THE_MAIN_DISPATCH_QUEUE__ + 12
21  CoreFoundation                	       0x1816c45f8 __CFRunLoopRun + 2544
22  CoreFoundation                	       0x1816d7250 CFRunLoopRunSpecific + 572
23  GraphicsServices              	       0x1a21e2988 GSEventRunModal + 160
24  UIKitCore                     	       0x183ed7a94 -[UIApplication _run] + 1080
25  UIKitCore                     	       0x183c70fd4 UIApplicationMain + 336
26  Element                       	       0x1011c8318 0x100f48000 + 2622232
27  dyld                          	       0x101f8c4d0 start + 444

pixlwave avatar Oct 04 '22 11:10 pixlwave

sorry to say that my Element still crash even after i update it to 1.9.7,should i offer newer crash logs or more details?

Shiroiame-Kusu avatar Oct 07 '22 08:10 Shiroiame-Kusu

Ideally we need more details. From the crash logs alone we don't have enough information to reproduce the problem. Just to double check: Assuming you have another client or the key to restore your keys, have you tried uninstalling and reinstalling the app? If that didn't work, or you can't as you would lose your keys, it seems as though a specific room is causing the crash, so if you're able to dig in deeper to find out that room's ID and then let us know more information about it, it might help us to dig deeper.

pixlwave avatar Oct 07 '22 09:10 pixlwave

Ideally we need more details. From the crash logs alone we don't have enough information to reproduce the problem. Just to double check: Assuming you have another client or the key to restore your keys, have you tried uninstalling and reinstalling the app? If that didn't work, or you can't as you would lose your keys, it seems as though a specific room is causing the crash, so if you're able to dig in deeper to find out that room's ID and then let us know more information about it, it might help us to dig deeper.

How could I offer more details or find the “specific room” which is causing the crash,because my Element-Web and Element-Windows seems working normally,only Element-iOS will crash.

Shiroiame-Kusu avatar Oct 07 '22 10:10 Shiroiame-Kusu

just FYI, I have the same problem on one of my accoutns, one of my iphones and clearly I think this is because too much chans are subscribed or maybe because of the old chans which actually redirect to new chans. And how would you like to transfer the logs? Because it's not like we have a pop afterwards to actually be able to send logs liek we can on other apps on iOS....

ios 16.0.3 element up to date from the app store of course and this is happenning for several iterations of element.

changemenemo avatar Oct 24 '22 17:10 changemenemo