[Bug]: 'Error loading' crash when app started to run

[muhammedrollic]

What happened?

I exported an iOS build with OneSignal SDK 3.0.5 from Unity. Builded the app without errors and I ran the app. During launching, app immediately closed with 'Library not loaded: '@rpath/OneSignalCore.framework/OneSignalCore' message.

I solved this issue by embeding OneSignal.xcframework to app target. In previous versions, I didn't need to embed framework manually.

Steps to reproduce?

1. Install OneSignal SDK 3.0.5 to Unity project
2. Set the SDK with OneSignal SDK Setup window
3. Export an iOS build
4. Build and run iOS project

What did you expect to happen?

I expected to build and run my iOS app without any additional configuration.

Unity version

2020.3.41f1
2021.3.13f1

OneSignal Unity SDK version

3.0.5

Platform

iOS

Relevant log output

2022-11-10 13:50:35.729029+0300 v2020[62145:2726679] Error loading /var/containers/Bundle/Application/46EB3F7D-CC1A-4E43-AF67-64A0C38B1449/v2020.app/Frameworks/UnityFramework.framework/UnityFramework:  dlopen(/var/containers/Bundle/Application/46EB3F7D-CC1A-4E43-AF67-64A0C38B1449/v2020.app/Frameworks/UnityFramework.framework/UnityFramework, 0x0109): Library not loaded: '@rpath/OneSignalCore.framework/OneSignalCore'
  Referenced from: '/private/var/containers/Bundle/Application/46EB3F7D-CC1A-4E43-AF67-64A0C38B1449/v2020.app/Frameworks/UnityFramework.framework/UnityFramework'
  Reason: tried: '/usr/lib/swift/OneSignalCore.framework/OneSignalCore' (no such file), '/private/var/containers/Bundle/Application/46EB3F7D-CC1A-4E43-AF67-64A0C38B1449/v2020.app/Frameworks/OneSignalCore.framework/OneSignalCore' (no such file), '/private/var/containers/Bundle/Application/46EB3F7D-CC1A-4E43-AF67-64A0C38B1449/v2020.app/Frameworks/UnityFramework.framework/Frameworks/OneSignalCore.framework/OneSignalCore' (no such file), '/usr/lib/swift/OneSignalCore.framework/OneSignalCore' (no such file), '/private/var/containers/Bundle/Application/46EB3F7D-CC1A-4E43-AF67-64A0C38B1449/v2020.app/Frameworks/OneSignalCore.framework/OneSignalCore' (no such file), '/private/var/containers/Bundle/Application/46EB3F7D-CC1A-4E43-AF67-64A0C38B1449/v2020.app/Frameworks/UnityFramework.framework/Frameworks/OneSignalCore.framework/OneSignalCore' (no such file), '/private/var/containers/Bundle/Application/46EB3F7D-CC1A-4E43-AF67-64A0C38B1449/v2020.app/Frameworks/OneSignalCore.framework/OneSignalCore' (no such file), '/private/var/containers/Bundle/Application/46EB3F7D-CC1A-4E43-AF67-64A0C38B1449/v2020.app/Frameworks/OneSignalCore.framework/OneSignalCore' (no such file), '/System/Library/Frameworks/OneSignalCore.framework/OneSignalCore' (no such file)
2022-11-10 13:50:35.730456+0300 v2020[62145:2726679] Error loading /var/containers/Bundle/Application/46EB3F7D-CC1A-4E43-AF67-64A0C38B1449/v2020.app/Frameworks/UnityFramework.framework/UnityFramework:  dlopen(/var/containers/Bundle/Application/46EB3F7D-CC1A-4E43-AF67-64A0C38B1449/v2020.app/Frameworks/UnityFramework.framework/UnityFramework, 0x0109): Library not loaded: '@rpath/OneSignalCore.framework/OneSignalCore'
  Referenced from: '/private/var/containers/Bundle/Application/46EB3F7D-CC1A-4E43-AF67-64A0C38B1449/v2020.app/Frameworks/UnityFramework.framework/UnityFramework'
  Reason: tried: '/usr/lib/swift/OneSignalCore.framework/OneSignalCore' (no such file), '/private/var/containers/Bundle/Application/46EB3F7D-CC1A-4E43-AF67-64A0C38B1449/v2020.app/Frameworks/OneSignalCore.framework/OneSignalCore' (no such file), '/private/var/containers/Bundle/Application/46EB3F7D-CC1A-4E43-AF67-64A0C38B1449/v2020.app/Frameworks/UnityFramework.framework/Frameworks/OneSignalCore.framework/OneSignalCore' (no such file), '/usr/lib/swift/OneSignalCore.framework/OneSignalCore' (no such file), '/private/var/containers/Bundle/Application/46EB3F7D-CC1A-4E43-AF67-64A0C38B1449/v2020.app/Frameworks/OneSignalCore.framework/OneSignalCore' (no such file), '/private/var/containers/Bundle/Application/46EB3F7D-CC1A-4E43-AF67-64A0C38B1449/v2020.app/Frameworks/UnityFramework.framework/Frameworks/OneSignalCore.framework/OneSignalCore' (no such file), '/private/var/containers/Bundle/Application/46EB3F7D-CC1A-4E43-AF67-64A0C38B1449/v2020.app/Frameworks/OneSignalCore.framework/OneSignalCore' (no such file), '/private/var/containers/Bundle/Application/46EB3F7D-CC1A-4E43-AF67-64A0C38B1449/v2020.app/Frameworks/OneSignalCore.framework/OneSignalCore' (no such file), '/System/Library/Frameworks/OneSignalCore.framework/OneSignalCore' (no such file)

Code of Conduct

• I agree to follow this project's Code of Conduct

[shepherd-l]

Hey, thanks for reporting. We are going to look into this

[Vladeng]

Hey, thanks for reporting. We are going to look into this

Same problem with OneSignal SDK 3.0.6.

[muhammedrollic]

Hey, thanks for reporting. We are going to look into this

Same problem with OneSignal SDK 3.0.6.

I think they did not add fix for this bug to v3.0.6. So, we have to wait for next versions.

[isInYourMind]

Same error. iOS is still crashing at startup with OneSignal 3.0.6

[vdaineko]

I have managed to fix it by switching to brew CocoaPods installation:

1. Uninstall CocoaPods https://superuser.com/a/686319
2. Install cocoapods with brew
   brew install cocoapods
3. Make pod symbolik link because EMDU checks only standard paths for pod (/usr/local/bin and /usr/bin)
   sudo ln -s /opt/homebrew/bin/pod /usr/local/bin/pod

I don't know what the difference is, same CocoaPods versions (1.11.3), no errors in both cases, but somehow this fixed the problem.

[shepherd-l]

Please make sure that you are using CocoaPods version 1.11.3. We’ve seen this issue appear when using versions lower than 1.11.3.

Try

rm Podfile.lock
pod cache clean --all
pod install --repo-update

[roointan]

We have this same problem.
CocoaPods version 1.11.3
Xcode version 14.1
Unity 2021.3.14f1

What @shepherd-l suggested didn't work.
I tried adding $(inherited) to OTHER_LDFLAGS and LIBRARY_SEARCH_PATHS in Unity-iPhone target, didn't work.

Next I added
OneSignal.xcframework
OneSignalCore.xcframework
OneSignalExtension.xcframework
OneSignalOutcomes.xcframework
to UnityFramework Framework and libraries. It works fine on the development device with no startup crash, but when trying to upload to app store, we get another error:

Asset validation failed
CFBundleIdentifier Collision. There is more than one bundle with the CFBundleIdentifier value 'com.onesignal.OneSignal-Dynamic' under the iOS application ......

also for CFBundleIdentifiers "com.onesignal.OneSignalExtension"

Also another error, "UnityFramework.framework contains disallowed nested bundles"

[shepherd-l]

Hey @roointan,

Could you check and make sure that your Ruby version is 2.7.5+ and that Cocoapods is 1.11.3 and try cleaning your pods again


We think the root cause of this issue is from updating to Xcode 14.1.

[roointan]

@shepherd-l

CocoaPods is 1.11.3

system ruby version ruby --version is:
ruby 2.6.10p210 (2022-04-12 revision 67958) [universal.x86_64-darwin22]

ruby version installed by brew /usr/local/opt/ruby/bin/ruby --version is:
ruby 3.1.2p20 (2022-04-12 revision 4491bb740a) [x86_64-darwin21]

also, I should note, macOS version is 13.0.1

we had to update Xcode to version 14.1, because we have Firebase in our project too. Firebase has removed bitcode support, and we had to disable bitcode for other targets too. But after doing that project was not building with the old Xcode version, and the only solution we found was upgrading to 14.1

I removed ~/.cocoapods and retried pod install, didn't help.

I'm going to try what vdaineko suggested next.

[shepherd-l]

@roointan

If that doesn’t work, you can try setting your system ruby to match your brew installed ruby so that your system ruby --version is 2.7.5+

And after that, clean with this again:

rm Podfile.lock
pod cache clean --all
pod install --repo-update

[roointan]

@shepherd-l

using this ruby:
ruby 3.1.2p20 (2022-04-12 revision 4491bb740a) [x86_64-darwin21]

didn't help.
still getting an error on game start, but the error just looks different.

warning: UnityFramework was compiled with optimization - stepping may behave oddly; variables may not be available.
(lldb)

Thread 1 Queue : com.apple.main-thread (serial)
#0 0x000000010ada4390 in GetPreallocatedMemory [inlined] at /Users/bokken/build/output/unity/unity/Runtime/Allocator/MemoryManager.cpp:385
#1 0x000000010ada4390 in ::InitializeMemory() at /Users/bokken/build/output/unity/unity/Runtime/Allocator/MemoryManager.cpp:589
.
.
#22 0x000000010ada3618 in ::operator new() at /Users/bokken/build/output/unity/unity/Runtime/Allocator/MemoryManager.cpp:273
#23 0x000000019d0c3d74 in ___lldb_unnamed_symbol25507 ()

[roointan]

I went a long way,
Uninstalled Pod (that was installed with brew) and reinstalled it with gem (With 3.1.2p20 as the system ruby)
ran rm -rf ~/cocoapods
exported the project from Unity again, disabled bitcode on OneSignalNotificationServiceExtension target, and built again.
all to get back to
dyld[2239]: Library not loaded: @rpath/OneSignalCore.framework/OneSignalCore
error on game start.

[roointan]

I can build and run on device successfully by adding the following 4 to Framework and libraries of UnityFramework target
OneSignal.xcframework
OneSignalCore.xcframework
OneSignalExtension.xcframework
OneSignalOutcomes.xcframework

But can't upload to app store, because of the following errors:

Asset validation failed
CFBundleIdentifier Collision. There is more than one bundle with the CFBundleIdentifier value 'com.onesignal.OneSignal-Dynamic' under the iOS application ......

also for CFBundleIdentifiers "com.onesignal.OneSignalExtension"

Also another error, "UnityFramework.framework contains disallowed nested bundles"

@shepherd-l Do you have a solution for that?

[roointan]

Is there any plan to solve this issue in short-term?
or even long term?
Or do we have to find a solution ourselves?

[emawby]

@roointan Do you have an example project with the issue that we can use to try to reproduce? We have not been able to reproduce this issue when using Cocoapods 1.11.3 and Ruby 2.7.5+. We have received example projects in other platforms (iOS native, flutter, and react native) that have the issue and it is always resolved when pod install is run on a machine using the versions I listed above (also running pod cache clean --all pod install --repo-update and removing derived data). We have not yet been able to pin down exactly what changed in our distributed binaries/folks build environments to cause this