AppLovin / AppLovin-MAX-Unity-Plugin

110 stars 31 forks source link

iOS crashing after use ogury #332

Closed jedai7 closed 1 month ago

jedai7 commented 4 months ago

MAX Plugin Version

6.1.1

Unity Version

2021.3.24

Device/Platform Info

all ios devices

Current Behavior

This is our current mediation networks. telegram-cloud-photo-size-2-5274054715631588976-y After install ogury ios build crashing crashing with error Error loading /var/containers/Bundle/Application/B7D68A1F-F540-423E-AC38-E35F864CCCAE/CryptoTycoon.app/Frameworks/UnityFramework.framework/UnityFramework (139):

Expected Behavior

No response

How to Reproduce

Install ogury mediation adapter

Additional Info

No response

jedai7 commented 4 months ago

Error loading /var/containers/Bundle/Application/A4F9925C-A766-4D29-8A7B-E9E005AED2B8/CryptoTycoon.app/Frameworks/UnityFramework.framework/UnityFramework (139): dlopen(/var/containers/Bundle/Application/A4F9925C-A766-4D29-8A7B-E9E005AED2B8/CryptoTycoon.app/Frameworks/UnityFramework.framework/UnityFramework, 0x0109): Library not loaded: @rpath/OMSDK_Ogury.framework/OMSDK_Ogury Referenced from: /private/var/containers/Bundle/Application/A4F9925C-A766-4D29-8A7B-E9E005AED2B8/CryptoTycoon.app/Frameworks/UnityFramework.framework/UnityFramework Reason: tried: '/usr/lib/swift/OMSDK_Ogury.framework/OMSDK_Ogury' (errno=2, not in dyld cache), '/private/preboot/Cryptexes/OS/usr/lib/swift/OMSDK_Ogury.framework/OMSDK_Ogury' (errno=2), '/private/var/containers/Bundle/Application/A4F9925C-A766-4D29-8A7B-E9E005AED2B8/CryptoTycoon.app/Frameworks/OMSDK_Ogury.framework/OMSDK_Ogury' (errno=2), '/private/var/containers/Bundle/Application/A4F9925C-A766-4D29-8A7B-E9E005AED2B8/CryptoTyco<…>

pods `source 'https://cdn.cocoapods.org/' source 'https://github.com/CocoaPods/Specs'

platform :ios, '12.0'

target 'UnityFramework' do pod 'Amplitude', '~> 8.16.3' pod 'AppLovinMediationChartboostAdapter', '9.1.0.1' pod 'AppLovinMediationFacebookAdapter', '6.12.0.2' pod 'AppLovinMediationFyberAdapter', '8.1.9.0' pod 'AppLovinMediationGoogleAdapter', '10.13.0.0' pod 'AppLovinMediationGoogleAdManagerAdapter', '10.13.0.0' pod 'AppLovinMediationIronSourceAdapter', '7.2.7.0.1' pod 'AppLovinMediationMintegralAdapter', '7.3.1.0.0' pod 'AppLovinMediationOguryPresageAdapter', '4.2.2.0' pod 'AppLovinMediationUnityAdsAdapter', '4.6.0.0' pod 'AppLovinMediationVungleAdapter', '6.12.0.2' pod 'AppLovinSDK', '12.1.0' pod 'AppsFlyerFramework', '6.8.1' pod 'FBAudienceNetwork', '~> 6.12.0' pod 'Firebase/Analytics', '9.6.0' pod 'Firebase/Core', '9.6.0' pod 'Firebase/Crashlytics', '9.6.0' pod 'Firebase/Messaging', '9.6.0' pod 'Firebase/RemoteConfig', '9.6.0' pod 'Google-Mobile-Ads-SDK', '~> 10.13' end target 'Unity-iPhone' do end use_frameworks! :linkage => :static `

JonathanLiuApp commented 4 months ago

Hello, could you check whether you have the correct External Dependency Manager settings by following our integration docs: https://dash.applovin.com/documentation/mediation/unity/getting-started/integration#external-dependency-manager

jedai7 commented 4 months ago

@JonathanLiuApp i do it. And i have new errors iOS framework addition failed due to a CocoaPods installation failure. This will will likely result in an non-functional Xcode project.

After the failure, "pod repo update" was executed and succeeded. "pod install" was then attempted again, and still failed. This may be due to a broken CocoaPods installation. See: https://guides.cocoapods.org/using/troubleshooting.html for potential solutions. The Swift pod FirebaseCoreInternal depends upon GoogleUtilities, which does not define modules. To opt into those targets generating module maps (which is necessary to import them from Swift when building as static libraries), you may set use_modular_headers! globally in your Podfile, or specify :modular_headers => true for particular dependencies.

Error building Player: iOS framework addition failed due to a CocoaPods installation failure. This will will likely result in an non-functional Xcode project.

My previous settings image with this settings always was fine, before add ogury network

JonathanLiuApp commented 3 months ago

To fix the issue, you can manually embed OMSDK_Ogury.xcframework to your target. That should fix it, but please let me know if you see any additional errors.