Admob's mediations are in conflict with the xcconfig settings

[hou...@gmail.com]

We are using Admob as our primary provider and mediate through AdMob two further ad providers (AdColony and IronSource). 

On iOS upon installation of the Podfile, admob shows problems when installing AdColony and IronSource.

The error message is:

[!] Can't merge user_target_xcconfig for pod targets: ["AdColony", "IronSourceSDK"]. Singular build setting EXCLUDED_ARCHS[sdk=iphonesimulator*] has different values.

If I remove AdColony and only leave Ironsource in there. The Error goes away.

If I add Adcolony back and remove Ironsource, the error still doesn't appear.

If I add them both back, the error reappears again.

Since this is driven through Admob, this is a problem on your side. The IronSource and Adcolony customer support can't help.

The installed versions are:

- Google-Mobile-Ads-SDK (7.67.1):

- GoogleMobileAdsMediationAdColony (4.4.1.0):

    - AdColony (= 4.4.1)

    - Google-Mobile-Ads-SDK (>= 7.66.0)

- GoogleMobileAdsMediationIronSource (7.0.3.0):

    - Google-Mobile-Ads-SDK (>= 7.66.0)

    - IronSourceSDK (= 7.0.3)

The Podfile looks like this:

def shared_pods

  pod 'SSZipArchive'

  pod 'KeychainAccess'

  pod 'SwiftyBeaver'

  pod 'OpenVPNAdapter', :git => 'https://github.com/ss-abramchuk/OpenVPNAdapter.git', :tag => '0.7.0'

end

target 'myApp' do

  # Comment the next line if you don't want to use dynamic frameworks

  platform :ios, '11.0'

  use_frameworks!

  shared_pods

  # Pods for myApp

  pod 'IQKeyboardManagerSwift'

  pod 'Firebase/Analytics'

  pod 'Firebase/Crashlytics'

  pod 'FacebookSDK/CoreKit'

  pod 'FacebookSDK/ShareKit'

  pod 'Google-Mobile-Ads-SDK'

  pod 'GoogleMobileAdsMediationAdColony'

  pod 'GoogleMobileAdsMediationIronSource'

# pod 'GoogleMobileAdsMediationTestSuite'

  target 'myAppTests' do

    inherit! :search_paths

    # Pods for testing

  end

  target 'myAppUITests' do

    # Pods for testing

  end

  target 'tunnel-ios' do

    pod 'OpenVPNAdapter', :git => 'https://github.com/ss-abramchuk/OpenVPNAdapter.git', :tag => '0.7.0'

  end

end

target 'MyApp VPN Proxy' do

  # Comment the next line if you don't want to use dynamic frameworks

  platform :macos, '10.12'

  use_frameworks!

  shared_pods

  # Pods for MyApp VPN

  pod 'AppCenter'

  target 'myApp-macTests' do

    inherit! :search_paths

    # Pods for testing

  end

  target 'myApp-macUITests' do

    # Pods for testing

  end

end

post_install do |installer|

        installer.pods_project.targets.each do |target|

                target.build_configurations.each do |config|

                        config.build_settings['APPLICATION_EXTENSION_API_ONLY'] = 'NO'

                        config.build_settings.delete 'IPHONEOS_DEPLOYMENT_TARGET'

                end

        end

end

What can I do?

Many Thanks,

Houman

[Mobile Ads SDK Forum Advisor Prod]

Hi there,

I replicated your issue and brought it with the rest of my team. We will get back to you as soon as possible.

Regards,

Aryeh Baker Mobile Ads SDK Team

ref:_00D1U1174p._5004Q276pFd:ref

[Houman]

Hello Aryeh,

Thank you for the confirmation.  Is there any update on this, please? This is really problematic.

Based on my research and the help from their support team, it seems that the issue can be resolved by using Adcolony 4.4.1.1. However Admob is still used the older 4.4.1 version:

- GoogleMobileAdsMediationAdColony (4.4.1.0):

    - AdColony (= 4.4.1)

    - Google-Mobile-Ads-SDK (>= 7.66.0)

May you please update your Pod?

Thank you,

Houman

[Mobile Ads SDK Forum Advisor Prod]

Hi Houman,

Thank you for responding back. I work along with Aryeh and as such will be helping you today. I have looked over the post and checked up with my team. At the moment their is no updates to pass along to you. But I have made sure to pass along to them your comment of having spoken to Adcolony.

Regards,

William Pescherine Mobile Ads SDK Team

ref:_00D1U1174p._5004Q276pFd:ref

[Houman]

Hello William,

This is blocking our next release. Can you confirm if we should ignore the error message and it will still mediate the ads correctly?

Otherwise what is your roadmap about upgrading Adcolony to the latest version 4.4.1.1 to fix the problem? When can we expect that, please?

Kind Regards,

Houman

[Mobile Ads SDK Forum Advisor Prod]

Hi Houman,

Thank you for your patience on this issue.

I'm afraid that we do not have any new insights (nor can we share any timelines) on this at the moment, since the team is still working on updating the AdColony adapter. Rest assured that we'll keep you updated.

Ziv Yves Sanchez Mobile Ads SDK Team

ref:_00D1U1174p._5004Q276pFd:ref

[Houman]

Hi AdMob Support team,

It has been 17 days since we reported this issue. Can you please provide at least a workaround?

What kind of technical support is this? :-) 

Many Thanks,

Houman