[Bug]: Latest SDK crashing on iPhone 8 Plus "DYLD 1 Library missing" Library not loaded: /System/Library/Frameworks/ActivityKit.framework/ActivityKit on Live or Simulator device

[DevelopmentDan]

What happened?

The latest version of the SDK crashes on iOS Model: iMac21,1, BootROM 10151.121.1, proc 8:4:4 processors, 16 GB, SMC "DYLD 1 Library missing" (iPhone 8 Plus) - It crashes on a live device and the simulator.

Steps to reproduce?

1. Install the latest version of the SDK into a OneSignal enabled app.
2. Build and deploy to an iPhone 8 Plus (simulator or live device)
3. The app will crash while trying to load libraries during start-up

What did you expect to happen?

For the app to work just as it did with the previous version of the SDK

Relevant log output

Exception Type: EXC_CRASH (SIGABRT)
Exception Codes: 0x0000000000000000, 0x0000000000000000
Termination Reason: DYLD 1 Library missing
Library not loaded: /System/Library/Frameworks/ActivityKit.framework/ActivityKit
Referenced from: /Users/USER/Library/Developer/CoreSimulator/Devices/F2542D4D-8A2E-4FBA-9425-ED8D1E3782C8/data/Containers/Bundle/Application/9D8CA19F-087C-46C7-A274-01AFA340C3AE/REDACTED.app/REDACTED
Reason: tried: '/Library/Developer/CoreSimulator/Profiles/Runtimes/iOS 15.0.simruntime/Contents/Resources/RuntimeRoot/System/Library/Frameworks/ActivityKit.framework/ActivityKit' (no such file), '/System/Library/Frameworks/ActivityKit.framework/ActivityKit' (no such file), '/Library/Developer/CoreSimulator/Profiles/Runtimes/iOS 15.0.simruntime/Contents/Resources/RuntimeRoot/System/Library/Frameworks/ActivityKit.framework/ActivityKit' (no such file)
(terminated at launch; ignore backtrace)

Code of Conduct

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

[emawby]

Thank you for reporting we are investigating. ActivityKit is only available in iOS 16+ and it looks like it is building for iOS 15 so that library needs to be excluded from the build. We are working on a fix.

Just to double check is your application attempting to use any of OneSignal's live activities methods on an iOS 15 device?

[DevelopmentDan]

@emawby. Thank you for the reply. I don't use live activities at all.

[alexsmi-noveo]

The same for me: MAUI 8.0.71. Crashes on iOS 15 with OneSignal 5.2.0.
On iOS 16 and 17 everything works ok.
Rollback to OneSignal 5.1.3 recovers MAUI functionality on iOS 15

Exception Type: EXC_CRASH (SIGABRT)
Exception Codes: 0x0000000000000000, 0x0000000000000000
Termination Reason: DYLD 1 Library missing
Library not loaded: /System/Library/Frameworks/ActivityKit.framework/ActivityKit
Referenced from: /Users/USER/Library/Developer/CoreSimulator/Devices/94B60F18-B865-4DB1-A051-F7E9BC35DA68/data/Containers/Bundle/Application/89FA099E-C3D9-4E48-B969-520CE13AF569/XXXX/XXXX
Reason: tried: '/Library/Developer/CoreSimulator/Profiles/Runtimes/iOS 15.5.simruntime/Contents/Resources/RuntimeRoot/System/Library/Frameworks/ActivityKit.framework/ActivityKit' (no such file), '/System/Library/Frameworks/ActivityKit.framework/ActivityKit' (no such file), '/Library/Developer/CoreSimulator/Profiles/Runtimes/iOS 15.5.simruntime/Contents/Resources/RuntimeRoot/System/Library/Frameworks/ActivityKit.framework/ActivityKit' (no such file)
(terminated at launch; ignore backtrace)

[DevelopmentDan]

Is there any news on this issue being fixed? I installed the latest SDK - and am still having problems. Keep having to roll this NuGet package back to get the app to work on iOS and then go to the latest version for Android

[IainS1986]

I'm not sure this is iOS 15 specific.

When I upgrade my .net-ios project to use 5.2.1 I get an instant crash during the splashscreen, before the debugger connects even so no Idea on the crash specifics, but also its before any calls to OneSignal itself.

This is on a device running iOS 17.6.1

Rolling back to 5.1.3 restores the app.

[fadi-george]

Hello,
The current SDK version (6.1.0) bundles native iOS frameworks that weak-link ActivityKit, so this crash should no longer occur on older iOS versions. If you're still hitting this, please update to the latest SDK version. The SDK now targets .NET 10 as well.

Closing this out, but feel free to reopen if you can reproduce on the latest version.