You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
source 'https://cdn.cocoapods.org/'
source 'https://github.com/CocoaPods/Specs'
platform :ios, '13.0'
target 'UnityFramework' do
pod 'AppLovinMediationAdColonyAdapter', '4.9.0.0.4'
pod 'AppLovinMediationBidMachineAdapter', '2.4.0.1.0'
pod 'AppLovinMediationByteDanceAdapter', '5.7.0.7.0'
pod 'AppLovinMediationChartboostAdapter', '9.6.0.0'
pod 'AppLovinMediationFacebookAdapter', '6.14.0.1'
pod 'AppLovinMediationFyberAdapter', '8.2.5.0'
pod 'AppLovinMediationGoogleAdapter', '10.14.0.1'
pod 'AppLovinMediationGoogleAdManagerAdapter', '10.14.0.0'
pod 'AppLovinMediationHyprMXAdapter', '6.3.0.0'
pod 'AppLovinMediationInMobiAdapter', '10.6.0.0'
pod 'AppLovinMediationIronSourceAdapter', '7.6.0.0.0'
pod 'AppLovinMediationMintegralAdapter', '7.5.3.0.0'
pod 'AppLovinMediationMobileFuseAdapter', '1.6.5.0'
pod 'AppLovinMediationUnityAdsAdapter', '4.9.2.1'
pod 'AppLovinMediationVerveAdapter', '2.20.0.0'
pod 'AppLovinMediationVungleAdapter', '7.2.0.0'
pod 'AppLovinSDK', '11.11.4'
pod 'AppsFlyerFramework', '6.5.4'
pod 'FBSDKCoreKit', '~> 11.1.0'
pod 'FBSDKCoreKit_Basics', '~> 11.1.0'
pod 'FBSDKGamingServicesKit', '~> 11.1.0'
pod 'FBSDKLoginKit', '~> 11.1.0'
pod 'FBSDKShareKit', '~> 11.1.0'
pod 'Firebase/Analytics', '10.11.0'
pod 'Firebase/Core', '10.11.0'
pod 'Firebase/Crashlytics', '10.11.0'
pod 'Firebase/Messaging', '10.11.0'
pod 'Firebase/RemoteConfig', '10.11.0'
pod 'Google-Mobile-Ads-SDK', '~> 10.9'
end
target 'Unity-iPhone' do
end
use_frameworks! :linkage => :static
use_frameworks!
Description
After running command pod install for the xcode project we receive the next log error:
After some investigation, we found out that this was caused by AppLovinMediationByteDanceAdapter, specifically by its dependency BURelyFoundation_Global.
What else we found?
This is not reproducible on Intel processors on Mac OS, only machines with M processors are affected
This is not caused by cocoapods type or version, tested on different versions of cocoapods with native support and under Rosseta
What else we did do to fix it?
Obvious move - we removed AppLovinMediationByteDanceAdapter from the build. Without ByteDance adapter everything works as expected, so this problem is directly linked to this adapter
Downgraded version of this adapter (to 3 different versions, even to 5.1.0.8.0), it doesn't help
Expected Behavior
Pod install command for resulted xcode project with AppLovinMediationByteDanceAdapter works as expected
How to Reproduce
Described in the expected behaviour section
Additional Info
No response
The text was updated successfully, but these errors were encountered:
AdColony is deprecated so you no longer need that adapter. The permission issue may be related to how you're running CocoaPods command, perhaps try sudo ...?
@thomasmso Cocoapods, by default, can't be run under sudo, this is a restriction of this tool, however there is a available arg --allow-root, but we can't use it because we are using https://github.com/googlesamples/unity-jar-resolver and we are unable to pass extra arguments to cocoapods. Thus, this is workaround for the issue, not a solution for it.
@Viabo looks like this is a regression in cocoapods 1.15.0 based on the issue here: CocoaPods/CocoaPods#12225
Downgrading to 1.14.3 should work while they fix it.
MAX SDK Version
Unity 5.11.5
Device/Platform Info
iOS
Current Behavior
Configuration
Cocoapods configuration:
Description
After running command pod install for the xcode project we receive the next log error:
After some investigation, we found out that this was caused by AppLovinMediationByteDanceAdapter, specifically by its dependency BURelyFoundation_Global.
What else we found?
What else we did do to fix it?
Expected Behavior
Pod install command for resulted xcode project with AppLovinMediationByteDanceAdapter works as expected
How to Reproduce
Described in the expected behaviour section
Additional Info
No response
The text was updated successfully, but these errors were encountered: