distriqt / ANE-IronSource

IronSource ANE updated to latest SDK
5 stars 0 forks source link

iOS app crashes on launch when including the Admob mediator #70

Open jdtapslots opened 2 weeks ago

jdtapslots commented 2 weeks ago

Problem Description

iOS app crashes on launch. 100% reproducible. Android works fine. AIR SDK 51.1.1.5 Windows

Steps to Reproduce

Include the Ironsource ANE and the Admob mediator as per Distriqt docs.

<extensionID>com.distriqt.IronSource</extensionID>
<extensionID>com.distriqt.ironsource.AdMob</extensionID>

Known Workarounds

None.

marchbold commented 2 weeks ago

Did you add your admob app id to the info additions?

This is the most common cause of a crash on launch with admob.

Check the docs for more info: https://docs.airnativeextensions.com/docs/ironsource/mediation/admob

jdtapslots commented 2 weeks ago

Hi @marchbold , thanks for your prompt response. Yes all of those settings are present https://docs.airnativeextensions.com/docs/ironsource/mediation/admob/#ios We've been using Ironsource and the Admob mediator for several years, and this issue is new to us after updating the ANEs to the latest available.

marchbold commented 2 weeks ago

Okay, Could you provide the logs from the device? Hopefully I can spot the issue there.

https://docs.airnativeextensions.com/docs/tutorials/device-logs/

jdtapslots commented 2 weeks ago
error   20:42:31.919401+0800    SpringBoard Scene FBSceneManager/sceneID:com.[redacted]-default update failed: <NSError: 0x3077942a0; domain: FBSceneErrorDomain; code: 1 ("operation-failed"); "Scene update failed."> {
    NSUnderlyingError = <NSError: 0x307705e60; domain: BSServiceConnectionErrorDomain; code: 3 ("OperationFailed"); "XPC error received on message reply handler">;
}
marchbold commented 2 weeks ago

Are you using the platform sdk option?

We have found that some versions of AIR seem to fail if you don't supply a version of the iOS SDK. You can do this via the adt platformsdk command line option:

https://docs.airnativeextensions.com/docs/adverts/troubleshooting#ios-sdk-issue

jdtapslots commented 2 weeks ago

We were not, so tried that and get compiler errors:

     [java] [Adt]ld64: error: E:\\iPhoneOS18.0.sdk/usr/lib\libc++.tbd: unhandled file type
     [java] [Adt]ld64: error: E:\\iPhoneOS18.0.sdk/usr/lib\libz.tbd: unhandled file type
     [java] [Adt]ld64: error: E:\\iPhoneOS18.0.sdk/usr/lib\libobjc.tbd: unhandled file type
     [java] [Adt]ld64: error: library not found for -lswiftFoundation
     [java] [Adt]ld64: error: E:\\iPhoneOS18.0.sdk/usr/lib\libobjc.tbd: unhandled file type
     [java] [Adt]ld64: error: E:\\iPhoneOS18.0.sdk/usr/lib\libobjc.tbd: unhandled file type
     [java] [Adt]ld64: error: E:\\iPhoneOS18.0.sdk/usr/lib\libobjc.tbd: unhandled file type
     [java] [Adt]ld64: error: E:\\iPhoneOS18.0.sdk/usr/lib\libobjc.tbd: unhandled file type
     [java] [Adt]ld64: error: E:\\iPhoneOS18.0.sdk/usr/lib\libobjc.tbd: unhandled file type
     [java] [Adt]ld64: error: E:\\iPhoneOS18.0.sdk/usr/lib\libobjc.tbd: unhandled file type
     [java] [Adt]ld64: error: E:\\iPhoneOS18.0.sdk/usr/lib\libobjc.tbd: unhandled file type
     [java] [Adt]ld64: error: E:\\iPhoneOS18.0.sdk/usr/lib\libobjc.tbd: unhandled file type
     [java] [Adt]ld64: error: E:\\iPhoneOS18.0.sdk/usr/lib\libobjc.tbd: unhandled file type
     [java] [Adt]ld64: error: E:\\iPhoneOS18.0.sdk/usr/lib\libobjc.tbd: unhandled file type
     [java] [Adt]ld64: error: E:\\iPhoneOS18.0.sdk/usr/lib\libobjc.tbd: unhandled file type
     [java] [Adt]ld64: error: E:\\iPhoneOS18.0.sdk/usr/lib\libobjc.tbd: unhandled file type
     [java] [Adt]ld64: error: E:\\iPhoneOS18.0.sdk/usr/lib\libobjc.tbd: unhandled file type
     [java] [Adt]ld64: error: E:\\iPhoneOS18.0.sdk/usr/lib\libobjc.tbd: unhandled file type
     [java] [Adt]ld64: error: E:\\iPhoneOS18.0.sdk/usr/lib\libobjc.tbd: unhandled file type
     [java] [Adt]ld64: error: E:\\iPhoneOS18.0.sdk/usr/lib\libobjc.tbd: unhandled file type
     [java] [Adt]ld64: error: too many errors emitted, stopping now (use --error-limit=0 to see all errors)
     [java] [Adt]
     [java] [AdtE]Compilation failed while executing : ld64
     [java] Exit: 12
     [java] Package Failed
marchbold commented 2 weeks ago

Did you try 17.5, not sure if 18.0 has been tested thoroughly yet.

jdtapslots commented 2 weeks ago

Same with 17.5

     [java] [Adt]ld64: error: could not load TAPI file at E:\\iPhoneOS17.5.sdk/System/Library/Frameworks\CoreFoundation.framework\CoreFoundation.tbd: unsupported file type
     [java] [Adt]ld64: error: could not load TAPI file at E:\\iPhoneOS17.5.sdk/System/Library/Frameworks\CoreFoundation.framework\CoreFoundation.tbd: unsupported file type
     [java] [Adt]ld64: error: could not load TAPI file at E:\\iPhoneOS17.5.sdk/System/Library/Frameworks\CoreFoundation.framework\CoreFoundation.tbd: unsupported file type
     [java] [Adt]ld64: error: could not load TAPI file at E:\\iPhoneOS17.5.sdk/System/Library/Frameworks\CoreFoundation.framework\CoreFoundation.tbd: unsupported file type
     [java] [Adt]ld64: error: E:\\iPhoneOS17.5.sdk/usr/lib\libc++.tbd: unhandled file type
     [java] [Adt]ld64: error: could not load TAPI file at E:\\iPhoneOS17.5.sdk/usr/lib\libSystem.B.tbd: unsupported file type
     [java] [Adt]ld64: error: E:\\iPhoneOS17.5.sdk/usr/lib\libz.tbd: unhandled file type
     [java] [Adt]ld64: error: E:\\iPhoneOS17.5.sdk/usr/lib\libobjc.tbd: unhandled file type
     [java] [Adt]ld64: error: library not found for -lswiftFoundation
     [java] [Adt]ld64: error: could not load TAPI file at E:\\iPhoneOS17.5.sdk/System/Library/Frameworks\AVFAudio.framework\AVFAudio.tbd: unsupported file type
     [java] [Adt]ld64: error: could not load TAPI file at E:\\iPhoneOS17.5.sdk/System/Library/Frameworks\AVFoundation.framework\AVFoundation.tbd: unsupported file type
     [java] [Adt]ld64: error: could not load TAPI file at E:\\iPhoneOS17.5.sdk/System/Library/Frameworks\AudioToolbox.framework\AudioToolbox.tbd: unsupported file type
     [java] [Adt]ld64: error: could not load TAPI file at E:\\iPhoneOS17.5.sdk/System/Library/Frameworks\CFNetwork.framework\CFNetwork.tbd: unsupported file type
     [java] [Adt]ld64: error: could not load TAPI file at E:\\iPhoneOS17.5.sdk/System/Library/Frameworks\CoreAudio.framework\CoreAudio.tbd: unsupported file type
     [java] [Adt]ld64: error: could not load TAPI file at E:\\iPhoneOS17.5.sdk/System/Library/Frameworks\CoreFoundation.framework\CoreFoundation.tbd: unsupported file type
     [java] [Adt]ld64: error: could not load TAPI file at E:\\iPhoneOS17.5.sdk/System/Library/Frameworks\CoreGraphics.framework\CoreGraphics.tbd: unsupported file type
     [java] [Adt]ld64: error: could not load TAPI file at E:\\iPhoneOS17.5.sdk/System/Library/Frameworks\CoreImage.framework\CoreImage.tbd: unsupported file type
     [java] [Adt]ld64: error: could not load TAPI file at E:\\iPhoneOS17.5.sdk/System/Library/Frameworks\CoreMIDI.framework\CoreMIDI.tbd: unsupported file type
     [java] [Adt]ld64: error: could not load TAPI file at E:\\iPhoneOS17.5.sdk/System/Library/Frameworks\CoreMedia.framework\CoreMedia.tbd: unsupported file type
     [java] [Adt]ld64: error: could not load TAPI file at E:\\iPhoneOS17.5.sdk/System/Library/Frameworks\CoreText.framework\CoreText.tbd: unsupported file type
     [java] [AdtE]Compilation failed while executing : ld64
     [java] [Adt]ld64: error: too many errors emitted, stopping now (use --error-limit=0 to see all errors)
     [java] [Adt]
     [java] Exit: 12
     [java] Package Failed
marchbold commented 2 weeks ago

Is this on macOS or Windows? I'm not sure the iOS SDK works with the linker on Windows. If you are building on Windows you'll need to use the previous release of AdMob or wait updates for the AIR SDK.

mrfrasier commented 1 week ago

Had the same issue on Windows today. Was going to switch over to trying to build on Mac again, but tried downgrading AdMob to 2.2.0 and that fixed the crashing.

Does always seem to be that adapter causing issues haha

marchbold commented 1 week ago

Yeah agreed, Google are probably more active in integrating the latest SDK functionality and it can cause issues if you aren't linking against the latest iOS SDK. In our experience so far using the platformsdk option has resolved all these issues however.