[SOLVED we think] AdMob support for iOS 14 AppTrackingTransparency

[khoabuidev]

Hi, Today I received this message on google Admob "Prepare your apps for iOS 14 Apple announced the new AppTrackingTransparency framework, which requires changes to your iOS apps. Implement the GMA SDK 7.64.0 (or later) and set up consent messaging to help prevent a significant loss in ad revenue." so what can I do now for it? many thanks!

Issue

Describe your issue here

---

Project Files

Javascript

Click To Expand

package.json:

# N/A

firebase.json for react-native-firebase v6:

# N/A

iOS

Click To Expand

ios/Podfile:

• I'm not using Pods
• I'm using Pods and my Podfile looks like:

# N/A

AppDelegate.m:

// N/A

---

Android

Click To Expand

Have you converted to AndroidX?

• my application is an AndroidX application?
• I am using android/gradle.settings jetifier=true for Android compatibility?
• I am using the NPM package jetifier for react-native compatibility?

android/build.gradle:

// N/A

android/app/build.gradle:

// N/A

android/settings.gradle:

// N/A

MainApplication.java:

// N/A

AndroidManifest.xml:

<!-- N/A -->

---

Environment

Click To Expand

react-native info output:

 OUTPUT GOES HERE

• Platform that you're experiencing the issue on:
  • iOS
  • Android
  • iOS but have not tested behavior on Android
  • Android but have not tested behavior on iOS
  • Both
• react-native-firebase version you're using that has this issue:
  • e.g. 5.4.3
• Firebase module(s) you're using that has the issue:
  • e.g. Instance ID
• Are you using TypeScript?
  • Y/N & VERSION

---

• 👉 Check out React Native Firebase and Invertase on Twitter for updates on the library.

[andersonaddo]

Hmmmm
so I had a look at this:
https://developers.google.com/admob/ios/ios14

Looks like there are two options: Stick with IDFA (which Apple is trying to effectively kill), or move on to SKAdNetwork.
And it seems that most of the work will still be developer side work for either option you choose - you just have to add some things to your info.plist.
Some native code checks are recommended but not needed. But I suppose patch-package can help with that.

I wonder if we should think about integrating this: https://developers.google.com/admob/ump/ios/quick-start

[khoabuidev]

Hmmmm
so I had a look at this:
https://developers.google.com/admob/ios/ios14

Looks like there are two options: Stick with IDFA (which Apple is trying to effectively kill), or move on to SKAdNetwork.
And it seems that most of the work will still be developer side work for either option you choose - you just have to add some things to your info.plist.
Some native code checks are recommended but not needed. But I suppose patch-package can help with that.

I wonder if we should think about integrating this: https://developers.google.com/admob/ump/ios/quick-start

Thank @andersonaddo very much, I will try to apply this.

[andersonaddo]

Just to note:
The docs note that Google Mobile Ads v7.64.0 will be needed, but I think we use a lower version. I'm not sure.
Having a look at our tests files (which contains a compiled app):

react-native-firebase/tests/ios/Podfile.lock

Line 14 in fcf2447

- Google-Mobile-Ads-SDK (~> 7.50)

react-native-firebase/tests/ios/Podfile.lock

Line 219 in fcf2447

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

[mikehardy]

Good spot @andersonaddo

They specify '~> 7.50' https://github.com/CocoaPods/Specs/blob/b513b219e9a15e2ab11b7ed93e69e0c7336a176a/Specs/0/3/5/Firebase/6.30.0/Firebase.podspec.json#L93

https://guides.cocoapods.org/using/the-podfile.html#specifying-pod-versions
`~> Major.Minor' (but not patch!) means that pod update should be allowed to bring in the 7.64 Google-Mobile-Ads-SDK

That's why the test Podfile.lock has 7.62 (must have been current the last time the lock file was updated) vs 7.50 which is specified

So it's achievable to test using current dependencies I think

[andersonaddo]

Great.
@khoabuidev please keep us updated about this. If it works, it might be worth mentioning it in our docs.

[khoabuidev]

I have updated all dependencies in my project, remove Podfile.lock and Pods folder and run "pod install" . I see that it installing Google-Mobile-Ads-SDK (7.64.0), detail as below:

1. npm i -g npm-check-updates
2. npx npm-check-updates -u
3. rm -r node_modules
4. yarn install
5. cd ios
6. pod install
   And there is the result

FYI: @andersonaddo

[mikehardy]

Of interest, react-native-permissions has a pull request that should work now, but it requires Xcode 12beta toolchain to compile zoontek/react-native-permissions#501

And adding the right stuff to your plist

<key>NSUserTrackingUsageDescription</key>
<string>This identifier will be used to deliver personalized ads to you.</string>

[mikehardy]

With the addition of that PR to react-native-permissions to handle the user consent, and the ability (proven) to use the latest version of the AdMobs SDK, I don't think there is anything more to do here. I'm going to close this but if I am wrong obviously we can reopen and discuss - not closing because it's not important just that I think it's resolved :-). Cheers

[khoabuidev]

Of interest, react-native-permissions has a pull request that should work now, but it requires Xcode 12beta toolchain to compile react-native-community/react-native-permissions#501

And adding the right stuff to your plist

<key>NSUserTrackingUsageDescription</key>
<string>This identifier will be used to deliver personalized ads to you.</string>

Thanks so much @mikehardy mikehardy