AdMob cocoapods with XCode 15 + phantom runner async_load (runner bug)

[MHG-Works]

Hi,

I'm still testing AdMob issues on iOS, and it seems the Google Admob extension, and specifically the Yoyo example project on the marketplace, shows a massive list of warnings in XCode, and also throws an error. I have attached a logfile containing all those warnings, as well as a snapshot of the error. IDE and Runtime are both the LATEST, XCode and macOS updates also applied already. Note that I have un-installed cocoapods and re-installed it also. Cocoapods is enabled and minimum target build setting is 16.1. For the DerivedData warnings, I tried clearing the DerivedData folder inside the Libraries > Developer > XCode folder, but the warnings persist anyway.

Would kindly ask the admob extension, using Yoyo's own example project even, be tested for these issues. Again, please see attached warnings log (file is called "Build Google_AdMob_2023-09-24T11-02-19.txt"), and error snapshot, which were produced by Yoyo's example project from the marketplace.

Thanks.

Build Google_AdMob_2023-09-24T11-02-19.txt

[DiasFranciscoA]

Hello,

Thank you for your report and patience.

After reviewing the details you provided, this ticket will be closed as it does not pertain to a bug with the extension itself. The issues you have described seem to be associated with:

The most recent release of XCode, version 15, especially affecting projects dependent on cocoapods. We are aware of this issue, and an internal fix has already been implemented. This fix will be included in the upcoming hotfix/release.

The demo experiences crashes due to an invalid ds_map error, a known issue with the runner that occasionally triggers “phantom” asynchronous events with invalid maps at random execution points, predominantly when the app is minimized and then restored. A fix for this has also been developed internally and will be available in the next hotfix|release.

~NOTE: We have noted the increased number of warnings the AdMob extension triggers during compilation. We plan to address this at a later stage as they do not impact the functionality of the extension. However, if you are comfortable and would like to contribute to our source code to resolve these issues, we welcome you to do so with a Pull Request. We have open-sourced the extensions specifically to encourage community involvement in the development process.~

After a thorough analysis of the included log file, it has been determined that the increased number of warnings experienced are not related to the extension but are rather a result of the building process of the runner. Unfortunately, this cannot be addressed or solved within the extension.

Please Note: This issue tracker is intended for addressing problems specific to the extension only. We recommend addressing concerns related to the runner's building process in the appropriate channels or forums designated for those types of issues. Since this is not a problem with AdMob but rather a problem that will be traversal to all extensions with similar setups.

We understand the inconvenience caused and appreciate your understanding. Please watch for the upcoming releases, and do check back with us if the issues persist post-update.

Best Regards, Francisco Dias

[MHG-Works]

@DiasFranciscoA Thanks for the in-depth reply. This is hopeful.

One small thing though:

Please Note: This issue tracker is intended for addressing problems specific to the extension only. We recommend addressing concerns related to the runner's building process in the appropriate channels or forums designated for those types of issues. Since this is not a problem with AdMob but rather a problem that will be traversal to all extensions with similar setups.

I'm aware of this, but please note that I was directed to using this tracker by Yoyo support. Posting technical issues on the forum yields poor results frequently. All the issues I've been experiencing with the AdMob extension are clearly down to the issues you've described above. However, importantly, the issues came up specifically due to needing to use AdMob, and I would not have known that the issues are being caused by xcode / the runner's building process (and not something on my end) without your explanation above, in this github space.

The point I'm emphasizing here is that you may expect issues being posted here (from me at least) regardless of the cause, because I obviously would not know the cause since I didn't develop the extension and can only report on what I'm seeing.

Thanks again.