Thread 1: EXC_BREAKPOINT (code=EXC_I386_BPT, subcode=0x0)
Hi Alexey,
Thank you for bringing this to our attention. Could you please share with us the sample project file that you are using? This will help our team to check and to confirm if the crash is pointing to the GADMobileAds.sharedInstance().start() method. Also, kindly share the complete stack trace of the crash for our reference.
Kindly share the above information privately to our testing alias: mobileads...@gmail.com
Regards,
|
||||||
|
||||||
--
---
You received this message because you are subscribed to the Google Groups "Google Mobile Ads SDK Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-admob-ads...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-admob-ads-sdk/fAEp4000000000000000000000000000000000000000000000QPNPEI008TwsbT2jSCKI05J8O1ebOA%40sfdc.net.
Hi Alexy,
In SDK version 8.0.0, we removed support for i386 simulators (see https://developers.google.com/admob/ios/rel-notes). Since i386 is in your error code, I'm guessing your iOS 13 simulator is somehow running i386. Any chance you can try SDK version 7.69 and see if you still get the issue? If you don't have a test app, you can try one from https://github.com/googleads/googleads-mobile-ios-examples/releases/tag/7.22 which is built against 7.x.
In the meantime, I'll check with our SDK team to better understand if there's an actual use case here to bring that back, or if there's a more appropriate workaround. My understanding is 32-bit simulators are a thing of the past (and certainly your M1 Mac is 64-bit as it's running arm64). So I'm not sure why your iOS 13 simulator wants i386 instructions.
Thanks,
Eric, Mobile Ads SDK Team