ANR : ANR in com.google.android.datatransport.runtime.scheduling.jobscheduling.Uploader on Android 14 – Investigation Needed

[Axita Savani]

Hello Team, 

I am experiencing an ANR issue in my app after updating to Target SDK 34. The issue is happening only in the background and primarily on Android 14 devices.  

Project Details:

• Ad Services: Google AdMob
• Firebase Services:
  • Firebase Analytics
  • Firebase Cloud Messaging (FCM)
  • Firebase Remote Config
• Target SDK: 34
• Minimum SDK: 21

ANR Details:

• Stack Trace (Main Thread Blocked):

main (runnable): tid=1 systid=5891 at com.google.android.datatransport.runtime.scheduling.jobscheduling.Uploader.upload(Uploader.java:95) at com.google.android.datatransport.runtime.scheduling.jobscheduling.JobInfoSchedulerService.onStartJob(JobInfoSchedulerService.java:49) at android.app.job.JobService$1.onStartJob(JobService.java:106) at android.app.job.JobServiceEngine$JobHandler.handleMessage(JobServiceEngine.java:195) at android.os.Handler.dispatchMessage(Handler.java:106) at android.os.Looper.loopOnce(Looper.java:257) at android.os.Looper.loop(Looper.java:368) at android.app.ActivityThread.main(ActivityThread.java:8839) at java.lang.reflect.Method.invoke(Native method) at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:572) at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1049) 

• Occurrences: This issue has been occurring for a long time but has increased significantly after targeting SDK 34.
• Affected Devices:
  • 99% of cases are on Android 14
  • 48% OnePlus, 30% Oppo, 19% Oppo, 3% Vivo
• Device State: 100% background
  
  Observations & Findings:

• I have not directly added com.google.android.datatransport in my project. It seems to be included as a transitive dependency, likely from Google AdMob or Firebase Messaging.
• The issue is not reproducible manually, but it is affecting live users continuously.
• After checking my dependency tree, I found:
  makefile

  
  

  + com.google.firebase:firebase-messaging:24.1.0
     ├── com.google.android.datatransport:transport-runtime:3.3.0
  
  
  Suggesting the ANR is related to Firebase Messaging’s background job scheduling.

Request for Support:

Could you please investigate this issue and provide guidance on:

1. The root cause of this ANR in Firebase Messaging/Google AdMob.
2. Any workaround or fix available for apps targeting SDK 34.
3. Whether unnecessary background jobs and how to disable them.

This issue is affecting live users, and any assistance would be greatly appreciated.

Looking forward to your response.
Thank you!

[Mobile Ads SDK Forum Advisor]

Hi, 

Thank you for contacting the Mobile Ads SDK support team.

I ran the Google BannerExample with the target SDK v34, minimum SDK v21 and Android 14 device and the ANR issue is not replicating. Can you confirm if you are making use of initialization optimization flag? If you haven't yet tried it, we suggest to use it as it mentioned that starting from Google Mobile Ads (GMA) SDK version 21.0.0, you can enable optimized SDK initialization and ad loading to improve the overall responsiveness of ads and help prevent "Application Not Responding" (ANR) errors on your app. The best way to optimize initialization is to call MobileAds.initialize() on a background thread, as described in the Get Started guide. If you are already doing so, you don't need to enable the optimization flag. After enabling the above mentioned flags also if the ANR issue still persists then kindly provide the below information privately for further investigation: 

• The full stack trace
• Steps to reproduce
• Sample app reproducing the issue(with affected app ID, ad unit ID)

You can provide the following details via reply privately to the author option or directly provide it to this link. 

This message is in relation to case "ref:!00D1U01174p.!5004Q02vH1gq:ref" (ADR-00288193)

Thanks,
 

Mobile Ads SDK Team

Feedback
How was our support today?

               

[Axita Savani]

Hi, 

We have already used Google Admob version 23+ with call MobileAds.initialize() on a background thread, as described in the Get Started guide document. 

Still getting this ANR too much.

I can share the full stack privately with the author but I don't have the step to reproduce this ANR.

[Mobile Ads SDK Forum Advisor]

Hi Axita,

Thank you for contacting the Mobile Ads SDK support team.

Looks like this ANR is not coming from AdMob, Kindly recheck and reach out to us if you see any AdMob or ad related logs in stack trace.

Thanks,
 

Mobile Ads SDK Team

Feedback
How was our support today?

               

[2025-02-18 11:57:53Z GMT] This message is in relation to case "ref:!00D1U01174p.!5004Q02vH1gq:ref" (ADR-00288193)