App crashing on launch. Device type: iPad and iPhone, OS version: iOS 15.6

Question

Created Aug ’22

Replies 1

Boosts 0

Views 1k

Participants 2

Review team says: We were unable to review your app as it crashed on launch. We have attached detailed crash logs to help troubleshoot this issue.

Review device details:

Device type: iPad and iPhone
OS version: iOS 15.6

But, the app works perfectly and has been tested on some physical devices and simulator(iOS 15.6)

Last Exception Backtrace:

0   CoreFoundation                	       0x1c29d9288 __exceptionPreprocess + 220
1   libobjc.A.dylib               	       0x1db708744 objc_exception_throw + 60
2   CoreFoundation                	       0x1c2ae4318 -[__NSCFString characterAtIndex:].cold.1 + 0
3   CoreFoundation                	       0x1c2aef5d4 -[__NSDictionaryM setObject:forKey:].cold.3 + 0
4   CoreFoundation                	       0x1c298e5f4 -[__NSDictionaryM setObject:forKey:] + 904
5   Senda Rutas                   	       0x102558c18 0x102550000 + 35864
6   Senda Rutas                   	       0x10255783c 0x102550000 + 30780
7   WebKit                        	       0x1d19233e8 ScriptMessageHandlerDelegate::didPostMessage(WebKit::WebPageProxy&, WebKit::FrameInfoData&&, API::ContentWorld&, WebCore::SerializedScriptValue&) + 208
8   WebKit                        	       0x1d1ccbd80 WebKit::WebUserContentControllerProxy::didPostMessage(WTF::ObjectIdentifier<WebKit::WebPageProxyIdentifierType>, WebKit::FrameInfoData&&, unsigned long long, WTF::Span<unsigned char const, 18446744073709551615ul> const&, WTF::CompletionHandler<void (WTF::Span<unsigned char const, 18446744073709551615ul> const&, WTF::String const&)>&&) + 712
9   WebKit                        	       0x1d201318c WebKit::WebUserContentControllerProxy::didReceiveMessage(IPC::Connection&, IPC::Decoder&) + 2384
10  WebKit                        	       0x1d19c9e10 IPC::MessageReceiverMap::dispatchMessage(IPC::Connection&, IPC::Decoder&) + 448
11  WebKit                        	       0x1d1c1616c WebKit::WebProcessProxy::didReceiveMessage(IPC::Connection&, IPC::Decoder&) + 40
12  WebKit                        	       0x1d19af2f0 IPC::Connection::dispatchMessage(std::__1::unique_ptr<IPC::Decoder, std::__1::default_delete<IPC::Decoder> >) + 264
13  WebKit                        	       0x1d19aeb08 IPC::Connection::dispatchIncomingMessages() + 468
14  JavaScriptCore                	       0x1cdbf17f0 WTF::RunLoop::performWork() + 200
15  JavaScriptCore                	       0x1cdbf258c WTF::RunLoop::performWork(void*) + 36
16  CoreFoundation                	       0x1c29fb414 __CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE0_PERFORM_FUNCTION__ + 28
.
.
.

Crash-log.txt

Can someone help me, please.

Boost

Answer 1

DTS Engineer OP

Apple

Aug ’22

Exception Type:  EXC_CRASH (SIGABRT)

This indicates that your app crashed itself by calling abort. The presence of the Last Exception Backtrace confirms that this was caused by an unhandled language exception. Now look at the backtrace there:

Last Exception Backtrace:
0   CoreFoundation  … __exceptionPreprocess + 220
1   libobjc.A.dylib … objc_exception_throw + 60
2   CoreFoundation  … -[__NSCFString characterAtIndex:].cold.1 + 0
3   CoreFoundation  … -[__NSDictionaryM setObject:forKey:].cold.3 + 0
4   CoreFoundation  … -[__NSDictionaryM setObject:forKey:] + 904
5   Senda Rutas     … 0x102550000 + 35864
6   Senda Rutas     … 0x102550000 + 30780
7   WebKit          … ScriptMessageHandlerDelegate::didPostMessage(WebKit…

In frame 7 WebKit is calling your script message handler. Frames 6 and 5 are your code. In frame 4 your code has set a property on a mutable dictionary. There’s something wonky about the parameters you’re passing in, which causes frame 2 to throw a language exception.

Based on same internal analysis, I suspect that the symbolication for frame 2 is kinda bogus and you’re crashing because the object you passed in to -setObject:forKey: is nil.

As to how that came about, the next step is to symbolicate the log to uncover the identity of the code in frames 6 and 5. For advice on that front, see Adding Identifiable Symbol Names to a Crash Report.

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

0