We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
App crash when try to launch on iPhone.
Detail crash info:
Exception Type: EXC_CRASH (SIGABRT) Exception Codes: 0x0000000000000000, 0x0000000000000000 Exception Note: EXC_CORPSE_NOTIFY Termination Description: DYLD, Library not loaded: @rpath/libswiftCore.dylib | Referenced from: /var/containers/Bundle/Application/296B68F4-E0CD-40B1-B726-8CAB4E5DBFC4/xxx.app/GodsStrike | Reason: image not found Triggered by Thread: 0
iPhone Version: iPhoneX iOS 12.1.4
iPhoneX iOS 12.1.4
Xcode Version: 13.1
13.1
AppLovin SDK Version: 11.0.0
11.0.0
Reproduction: true
true
According to integration document already set Build Settings > Always Embed Swift Standard Libraries to YES.
Build Settings
Always Embed Swift Standard Libraries
YES
I found a solution by add /usr/lib/swift to Build Settings -> Runpath Search Paths.
/usr/lib/swift
Runpath Search Paths
Please verify the crash and update the integration document if it is true.
The text was updated successfully, but these errors were encountered:
@chenxi92, looks good to us. We will document that tip on https://dash.applovin.com/documentation/mediation/ios/getting-started/integration.
Sorry, something went wrong.
chauduyphanvu
No branches or pull requests
App crash when try to launch on iPhone.
Detail crash info:
iPhone Version:
iPhoneX iOS 12.1.4
Xcode Version:
13.1
AppLovin SDK Version:
11.0.0
Reproduction:
true
According to integration document already set
Build Settings
>Always Embed Swift Standard Libraries
toYES
.I found a solution by add
/usr/lib/swift
toBuild Settings
->Runpath Search Paths
.Please verify the crash and update the integration document if it is true.
The text was updated successfully, but these errors were encountered: