GoogleUserMessagingPlatform 1.3.0 ios build issue

[lionel...@iscool-e.com]

Hi,

Xcode 12, I have this issue on build

ld: framework not found UserMessagingPlatform.xcframework

Have to going back to 1.2.0

[ash...@scirra.com]

We have this problem too. I don't think we changed anything, but now all our AdMob builds fail with that error message.

The framework is there under Pods\GoogleUserMessagingPlatform\Frameworks\Release, but it seems Xcode can't find it now.

I tried building with both Xcode 12 and Xcode 12.1, neither could compile.

[Mobile Ads SDK Forum Advisor Prod]

Hi everyone,

Thank you for bringing this to our attention. My UMP project just built following our guide with with SDK 1.3.0 works - there's just minor minor changes such as: changing UMPFormStatusAvailable to UMPFormStatus.available, UMPConsentStatusRequired to UMPConsentStatus.required, UMPConsentStatusObtained to UMPConsentStatus.obtained, UMPDebugGeographyEEA to UMPDebugGeography.EEA. This points to an issue occurring when upgrading. 

To help us investigate, could you give me the steps to take to reliably reproduce this issue while following as close as possible to our Consent guide?

Regards,

Aryeh Baker Mobile Ads SDK Team

ref:_00D1U1174p._5004Q275INW:ref

[Mobile Ads SDK Forum Advisor Prod]

Hi everyone,

You may monitor our Consent guide for documentation updates and fixes.

[ash...@scirra.com]

It's not clear from that guide what we ought to change, if anything. We already had everything set up according to that - it used to build, now it doesn't.

Here's a test Xcode project exhibiting the problem: https://www.dropbox.com/s/y1ly2c3yi45rop6/TestBuild.ios.project.zip?dl=0

Would you be able to identify from that what the problem is?

Ashley

[Mobile Ads SDK Forum Advisor Prod]

Hi Ashley,

Thank you for responding to our messages, as stated in a previous thread. I work along with Aryeh, and will be assisting you today with this issue. Are you able to give us a description of the steps that you are doing when updating the UMP SDK so that we can replicate it on our end. Also if you can send over a simple app that uses the UMP SDK with 1.3 included so that we can see what is happening.

Regards,

William Pescherine Mobile Ads SDK Team

ref:_00D1U1174p._5004Q275INW:ref

[ash...@scirra.com]

We didn't do any upgrade ourselves. This compile error seems to have come out of the blue.

I already provided a link to a sample Xcode project in my previous post.

[Mobile Ads SDK Forum Advisor Prod]

Hi Ashley,

Thank you for the additional information, I was able to download the code that you sent. The one question that I would have for you is that it appears that you are importing Cordova files to run your app? Was the app buiklt cross platform and thus converted to Xcode? If this is the case we are unable to offer any support for Cordova, and would suggest that you contact them as it would appear to be an issue with something they may have done.

[ash...@scirra.com]

Yes, we're using Cordova. But I am sure the Cordova team would tell us to talk to you instead!

It used to work. We haven't changed anything at all about our Cordova configuration. As far as I know Cordova runs the same configuration as you advise. And it used to work as of fairly recently (I checked this a few weeks ago and it was working).

I have no idea why this has stopped working or what to do about it. Can you please try to look at what might be wrong with the Xcode project and advise what could be done?

Ashley

[Mobile Ads SDK Forum Advisor Prod]

Hi Ashley,

Thank you for the response back, I would definitely suggest to contact Cordova. As they are the ones really supporting this . We are only supporting Android Studio, Xcode and Unity. What I am guessing has happoened is that a few weeks ago a new patch came out 1.3 as you tlaked about. Chances are there have been changes to UMP which Cordova has not yet caught up with. Thus you would get the compiling issue. As our internal working are looking for something and Cordova has not yet implemented them into their SDK.

Here are our Release notes regarding UMP SDK. I think it has to do with the 10/21 xcframework update that is causing the issue. Which as stated they probably have not yet caught up with in Cordova is my guess.

[lionel...@iscool-e.com]

We don't use UMP directly, we're using admob.

target 'Unity-iPhone' do

  platform :ios, '10.0'

  pod 'Firebase/Core', '6.33.0'

  pod 'Firebase/Messaging', '6.33.0'

  pod 'Firebase/RemoteConfig', '6.33.0'

  pod 'Firebase/Analytics', '6.33.0'

  pod 'Firebase/Crashlytics', '6.33.0'

  pod 'FBSDKCoreKit', '~> 8.0'

  pod 'FBSDKLoginKit', '~> 8.0'

  pod 'FBSDKShareKit', '~> 8.0'

  pod 'FBSDKGamingServicesKit', '~> 8.0'

  pod 'mopub-ios-sdk/Core', '5.14.1' 

  # AdColony

  pod 'MoPub-AdColony-Adapters', '4.4.1.1.1'

  # AppLovin

  pod 'MoPub-Applovin-Adapters', '6.14.5.0'

  # Chartboost

  pod 'MoPub-Chartboost-Adapters', '8.3.1.1'

  # Facebook Audience Network

  pod 'MoPub-FacebookAudienceNetwork-Adapters', '6.0.0.1'

  # Google (AdMob & Ad Manager)

  pod 'MoPub-AdMob-Adapters', '7.66.0.0'

  # Unity Ads

  pod 'MoPub-UnityAds-Adapters', '3.5.0.0'

  # ironSource

  pod 'MoPub-IronSource-Adapters', '7.0.2.0.0'

  # Tapjoy

  pod 'MoPub-TapJoy-Adapters', '12.7.0.1'

  target 'Unity-iPhone Tests' do

    inherit! :search_paths

  end

[Mobile Ads SDK Forum Advisor Prod]

Hi Ash,

I work along with Aryeh and William. Allow me to assist you in this.

I've tried your sample app on iPhone 8 iOS 14 simulator, and I wasn't able to reproduce the build issue. Instead, the app successfully build on my end (please see attached file). With that said, could you please confirm what device are you using when the issue occurs?

@Lionel,

Would it be possible for you to provide a sample project as well, so we could further assist your? You may upload it on your Google Drive, then provide to us the shareable link via Reply privately to author option.

Regards,

Teejay Wennie Pimentel Mobile Ads SDK Team

ref:_00D1U1174p._5004Q275INW:ref

[Brodie Sellar]

Hello,

I'm also facing the same issue. I have created a pod which is using the Google-Mobile-Ads-SDK as a dependency. 

I'm using cocoapods version 1.10. Since the update of UserMessagingPlatform to version 1.3.0, I can't publish my podspec anymore. 

pod publish is failing with an error ld: framework not found UserMessagingPlatform.

I noticed pod publish is building the app towards the simulator in release mode. I try to reproduce in an empty project. 

Building for simulator in debug mode is working but release mode is failing.

How to reproduce: 

1. Create a new project
2. pod init
3. add Google-Mobile-Ads-SDK to the pod file
4. pod install
5. run the following command: 

xcodebuild clean build -workspace PROJECT_NAME.xcworkspace -scheme TARGET_NAME -configuration Release -sdk iphonesimulator

Best regards,

Brodie

[Mobile Ads SDK Forum Advisor Prod]

Hi Brodie,

Thank you for your detailed instructions to fail a simulator release build with UMP! I received an error, but after following this stackoverflow article to navigate to Build Settings of your project and add Any iOS Simulator SDK with value arm64 inside Excluded Architecture I was able to build successfully. As described in that article there will soon be macs that run on iOS style architecture which means that simulators that run on that mac will also run on arm64 architecture. Let me bring this request up with my team. You may monitor the SDK Release Notes and UMP Release Notes for updates.

Regards,

Aryeh Baker Mobile Ads SDK Team

ref:_00D1U1174p._5004Q275INW:ref

[Brodie Sellar]

Hi Aryek,

Thanks for the link to article, I was able to build the project successful. I added EXCLUDED_ARCHS to my project build settings. And I used the following post_install hook to add EXCLUDED_ARCHS only to the UMP pod target. 

However, this solution doesn't seem to be applicable to the cocoaPods publish command. This command is running some validation on my podspec before publishing it. It'll create an empty project and install my pod into it then build it for release toward the simulator. In this case, I can't add the post_install hook inside the pod file as it's generated automatically by the publish script.

Is there another way to add EXCLUDED_ARCHS to the UMP target build settings ? 

Why do I need the EXCLUDED_ARCHS only for the UMP libraries and not others ? 

Since you are also using cocoapods, did you used the publish command  for the UMP podspec ? Was it successful for you ?

Instead of letting us add the EXCLUDED_ARCHS manually, could you add it tho the UMP podspec directly ?

Also like you said, we'll have a simulator running on arm64 so this solution looks only temporary. 

Best regards,

Brodie

[Mobile Ads SDK Forum Advisor Prod]

Hi Brodie,

Let me raise your additional comments to the rest of my team. You may monitor our release notes for updates. You may want to also check this article out.

[ash...@scirra.com]

I've tried the workarounds mentioned in this thread and none of them seem to work for me.

Building for a real device fails. Building for the iOS simulator also fails.

I've tried adding the build settings mentioned and trying different build options. Nothing seems to work. We make middleware and we have other customers asking for a solution, and I'm at a loss as to what to do.

It seems pretty clear from this thread others are affected and it is nothing to do with Cordova, which is just some other library we happen to use; we're really just using an Xcode project like everyone else here. Can anyone advise a workaround that can work for the Xcode project I provided earlier? Link: https://www.dropbox.com/s/y1ly2c3yi45rop6/TestBuild.ios.project.zip?dl=0

Ashley

[Mobile Ads SDK Forum Advisor Prod]

Hi Ashley,

Thank you for your response back. Please allow me to bringing this to my team to look at. Once we have some feedback  we will be certain to let you know.

Regards,

William Pescherine Mobile Ads SDK Team

ref:_00D1U1174p._5004Q275INW:ref

[Karim Lahbach]

i have the same problem like Ashley 

any tips to fix this problem i need to update my game in appstore

Thanks