iOS Build Environment Help Center

App crash report

append delete LBL

Window version : window 11
Builder version : 3.64
iOS SDK version : 17.2 (xcode 15.2 or xcode 15.3)
Test device ios version : 14.7

Hello, Seller. I am a user who purchased this asset and am trying to use it.

I have successfully built and installed the app, but the app crashes approximately 3 seconds after launching. The cause of the crash is difficult to pinpoint, but it seems to be related to either the Applovin SDK or the Firebase SDK. However, when building with Xcode 14.2 on my old MacBook, with the same environment settings, I confirmed that the app works normally on the same device without any crashes.

This problem only occurs when using the iOS Builder, and it is very difficult to identify the issue. Unfortunately, I couldn’t find any relevant posts regarding this asset, so I’m reaching out to you for help. I would appreciate it if you could help me identify the cause after reviewing the issue.

Here are the details of the error I encountered.
https://drive.google.com/file/d/1LDCFWfxR9vEOSj89gNg4oFzTIdjNexO1/view?usp=sharing

The SDK versions I am using are as follows:

Firebase Analytics: 10.20.0
Firebase Auth: 10.20.0
Firebase Database: 10.20.0
Firebase Messaging: 10.20.0
Applovin SDK: 12.6.0 (Unity ver 6.6.0)
Admob: 10.14.0
IronSource: 7.4.0
Unity Ads: 4.7.1

I would like to purchase the Daemon for using CocoaPods, but payment is disabled in my country, as I live in South Korea.

Reply RSS

Replies

append delete #1. Pierre-Marie Baty

Hello @LBL

I see "Unrecognized selector sent to instance" errors in the debug console log. These errors happen when an app attempts to locate and call an unexistent function that was not compiled in the app code (or in Objective-C gobbledygook, attempts to "send a message" to an "object instance" through an unexistent "selector").

Such errors are very often caused when the necessary -ObjC linker flag was missed. Omitting this flag when it is necessary may cause the app to build, but not work, because even if all the explicit function calls that are detectable at build time will be resolved and linked in, the ones that are called dynamically (i.e. at run time) will be left out. Adding -ObjC makes sure the linker includes *all* the functions from the dependent libraries and framework, even if they don't seem to be called explicitly.

Check if this flag is present in your extra linker flags, and if not, add it. You will probably need to include other frameworks and libraries past this point, because by adding all these functions to your app you'll also add dependencies. Simply resolve them as usuals, until your app builds with the -ObjC flag. This is very likely to fix your problem.

Reply

(Leave this as-is, it’s a trap!)

There is no need to “register”, just enter the same name + password of your choice every time.

Pro tip: Use markup to add links, quotes and more.

Moderators: Pierre-Marie Baty