App Crash at launch -> NO_CRASH_STACK (crash log attached)

Developer Tools & Services Xcode
Don_Tharaka_CC OP
Created Jun ’23
Replies 5
Boosts 1
Views 1.6k
Participants 3

App crashes at launch for some of our live users (NOT TESTFLIGHT).

I have managed to extract the error log:

Incident Identifier: B1F06CCD-4AAB-402F-9909-11FA7E1C54F3
Hardware Model:      iPhone14,3
Process:             *** [549]
Path:                /private/var/containers/Bundle/Application/DAE1AAC4-2150-46EF-B7B9-29553EA7346E/***.app/***
Identifier:          com.XX.XX
Version:             9.0 (70)
AppStoreTools:       14E221
AppVariant:          1:iPhone14,3:15
Code Type:           ARM-64 (Native)
Role:                Foreground
Parent Process:      launchd [1]
Coalition:           com.XX [580]

Date/Time:           2023-06-12 15:59:45.2595 +1000
Launch Time:         2023-06-12 15:59:45.2060 +1000
OS Version:          iPhone OS 15.6.1 (19G82)
Release Type:        User
Baseband Version:    1.70.01
Report Version:      104

Exception Type:  EXC_CRASH (SIGABRT)
Exception Codes: 0x0000000000000000, 0x0000000000000000
Exception Note:  EXC_CORPSE_NOTIFY
Termination Reason: DYLD 4 Symbol missing
Symbol not found: (_objc_claimAutoreleasedReturnValue)
Referenced from: '/Volumes/VOLUME/*/***.app/Frameworks/GoogleUtilities.framework/GoogleUtilities'
Expected in: '/usr/lib/libobjc.A.dylib'
(terminated at launch; ignore backtrace)

Triggered by Thread:  0


Thread 0 Crashed:
0   dyld                          	0x00000001034bcb14 __abort_with_payload + 8
1   dyld                          	0x00000001034c26cc abort_with_payload_wrapper_internal + 104 (terminate_with_reason.c:102)
2   dyld                          	0x00000001034c2700 abort_with_payload + 16 (terminate_with_reason.c:124)
3   dyld                          	0x0000000103492a00 dyld4::halt(char const*) + 580 (DyldProcessConfig.cpp:2102)
4   dyld                          	0x000000010348fa20 dyld4::prepare(dyld4::APIs&, dyld3::MachOAnalyzer const*) + 3560 (dyldMain.cpp:0)
5   dyld                          	0x000000010348dd84 start + 488 (dyldMain.cpp:864)


Thread 0 crashed with ARM Thread State (64-bit):
    x0: 0x0000000000000006   x1: 0x0000000000000004   x2: 0x000000016ddc56c8   x3: 0x00000000000000e4
    x4: 0x000000016ddc52c8   x5: 0x0000000000000000   x6: 0x0000000000000000   x7: 0x000000016ddc4d40
    x8: 0x0000000000000020   x9: 0x0000000000000009  x10: 0x000000016ddc53b8  x11: 0x0000000000000108
   x12: 0x0000000000000000  x13: 0x0000000000000035  x14: 0x0000000248f2d99d  x15: 0x000000016ddc47e8
   x16: 0x0000000000000209  x17: 0x00000001034b71c8  x18: 0x0000000000000000  x19: 0x0000000000000000
   x20: 0x000000016ddc52c8  x21: 0x00000000000000e4  x22: 0x000000016ddc56c8  x23: 0x0000000000000004
   x24: 0x0000000000000006  x25: 0x000000016ddc52c8  x26: 0x0000000000000400  x27: 0x0000000000000400
   x28: 0x00000000000000f0   fp: 0x000000016ddc5290   lr: 0x00000001034c26cc
    sp: 0x000000016ddc5250   pc: 0x00000001034bcb14     cpsr: 0x1000
   esr: 0x56000080  Address size fault


Binary Images:
0x103474000 - 0x1034cbfff dyld arm64e  <66e1fb2668f8379ba052eb8b8291b5e1> /usr/lib/dyld

EOF

Any help in fixing this issue with GoogleUtilities.framework/GoogleUtilities will be highly appreciated.

Answered by Don_Tharaka_CC in 756159022

This issue is experienced by users running iOS 15.6.1. Getting them to update the OS did the trick.

@eskimo

Replies  5
Boosts  1
Views  1.6k
Participants  3
DTS Engineer OP
Apple
Jun ’23

Are you building the affect framework from source? Or embedding a pre-built binary?

You mentioned that the problem shows up in product. Does it also show up on TestFlight?

Share and Enjoy
—
Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"

0
Don_Tharaka_CC OP
Jun ’23

@eskimo this issue is experienced by some of our live users. There is no way I can recreate the issue as it works perfectly fine on my development environment, testflight and when downloaded directly from appstore.

And I can find the affected framework "GoogleUtilities" in the pods section but not anywhere else :

0
DTS Engineer OP
Apple
Jun ’23

this issue is experienced by some of our live users. There is no way I can recreate the issue as it works perfectly fine on my development environment, testflight and when downloaded directly from appstore.

Have you been able to test it on the specific iOS version for which you have a crash report?

Share and Enjoy
—
Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"

1
Don_Tharaka_CC OP
Jun ’23
Accepted Answer

This issue is experienced by users running iOS 15.6.1. Getting them to update the OS did the trick.

@eskimo

1
DTS Engineer OP
Apple
Aug ’23

I just had a sigabrt running on my iPad with 16.5.1 that seems likely the same.

I didn’t mentioned a specific OS version, so I suspect you’re referring to the OP.

Regardless, if you have an issue similar to this I recommend that you start a new thread about it. Make sure to include a full Apple crash report, per the instructions in Posting a Crash Report.

Share and Enjoy
—
Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"

0
App Crash at launch -&gt; NO_CRASH_STACK (crash log attached)
First post date Last post date
 
 
Q