Open eli1stark opened 5 days ago
@eli1stark, thank you for raising this issue. The AppLovin SDK should not be manually added to your Podfile
, as our Flutter package already specifies the certified SDK version. Our documentation has incorrect information about this, which is currently being revised here. So, remove this from your Podfile.
pod 'AppLovinSDK'
Additionally, the NSUserTrackingUsageDescription
key is missing from your Info.plist
, and this is required to enable tracking of user activity within the app. Please add it as specified in the documentation.
@alhiwatan Thank you so much for providing this information. Does removing pod 'AppLovinSDK'
on iOS and implementation 'com.example.adapter:version'
on Android apply only to v4.0.0
, or to any version of AppLovin including v3.11.1
?
@eli1stark, it applies to all the plugin versions, including v3.11.1.
@alhiwatan Thank you. It's still not building with the recommended changes, but I think this is due to a hard Google Ads version requirement set by AppLovin. The Google Ads plugin is not supporting it yet which causes fetching of the older version via pods.
MAX Plugin Version
4.0.0
Flutter Version
3.24.3
Device/Platform Info
iOS 17.6.1
Current Behavior
When we updated AppLovin Flutter SDK to v4.0.0, the iOS app stopped building due to the error mentioned in this comment.
We can't reproduce this issue on v3.11.1.
Expected Behavior
The app should build without issues. Currently, when
AppLovinMAX.initialize(apiKey)
is called, the app build hangs indefinitely.How to Reproduce
The correct way to manage AppLovin mediation adapter versions is to:
Our Podfile looks like this (scroll to CocoaPods section) as advised in official docs:
For some reason, the AppLovin SDK is not fetching the latest version of the Google Adapter when we are running
pod update
. Instead ofv11.10.0
, it's fetchingv11.2.0.1
.We are also using the package
google_mobile_ads: 5.1.0
, which is required to enable the Google UMP flow. Could these packages conflict with each other? If so, there should be backward compatibility because there's no way to implement the UMP flow without it.Reproducible in the demo app?
Yes
We followed instructions provided here but for some reason we are getting a different error from Google adapter:
However we are providing correct app id that we use in our main project.
Here's our complete
Podfile
andInfo.plist
for demo app (app-key is stripped):Podfile
``` # Uncomment this line to define a global platform for your project platform :ios, '13.0' # CocoaPods analytics sends network stats synchronously affecting flutter build latency. ENV['COCOAPODS_DISABLE_STATS'] = 'true' project 'Runner', { 'Debug' => :debug, 'Profile' => :release, 'Release' => :release, } def flutter_root generated_xcode_build_settings_path = File.expand_path(File.join('..', 'Flutter', 'Generated.xcconfig'), __FILE__) unless File.exist?(generated_xcode_build_settings_path) raise "#{generated_xcode_build_settings_path} must exist. If you're running pod install manually, make sure flutter pub get is executed first" end File.foreach(generated_xcode_build_settings_path) do |line| matches = line.match(/FLUTTER_ROOT\=(.*)/) return matches[1].strip if matches end raise "FLUTTER_ROOT not found in #{generated_xcode_build_settings_path}. Try deleting Generated.xcconfig, then run flutter pub get" end require File.expand_path(File.join('packages', 'flutter_tools', 'bin', 'podhelper'), flutter_root) flutter_ios_podfile_setup target 'Runner' do use_frameworks! use_modular_headers! pod 'AppLovinMediationByteDanceAdapter' pod 'AppLovinMediationFacebookAdapter' pod 'AppLovinMediationGoogleAdapter' pod 'AppLovinMediationVungleAdapter' pod 'AppLovinMediationInMobiAdapter' pod 'AppLovinSDK' flutter_install_all_ios_pods File.dirname(File.realpath(__FILE__)) end post_install do |installer| installer.pods_project.targets.each do |target| flutter_additional_ios_build_settings(target) end end ```Info.plist
```Additional Info
Relevant links: