[Bug]: Fatal Exception: android.app.ForegroundServiceDidNotStartInTimeException

Ouverte
#526 6 commentaires 0 réactions 2 personnes assignées Voir sur GitHub

Les mainteneurs répondent en général sous 5 jours

@illuminati1911 y travaille déjà.

Depuis le 17/3/2026.

Évaluation

Cette issue n'a pas encore été évaluée.

Description

priority: p0 type: bug
Is there an existing issue for this?
  • I have searched the existing issues
Description of the bug

We get those crashes time to time:

Fatal Exception: android.app.ForegroundServiceDidNotStartInTimeException: Context.startForegroundService() did not then call Service.startForeground(): ServiceRecord{808d146 u0 com.apolloscooters/com.google.android.libraries.geo.navcore.service.base.NavigationService}
       at android.app.ActivityThread.throwRemoteServiceException(ActivityThread.java:2078)
       at android.app.ActivityThread.access$2800(ActivityThread.java:259)
       at android.app.ActivityThread$H.handleMessage(ActivityThread.java:2303)
       at android.os.Handler.dispatchMessage(Handler.java:106)
       at android.os.Looper.loopOnce(Looper.java:233)
       at android.os.Looper.loop(Looper.java:344)
       at android.app.ActivityThread.main(ActivityThread.java:8249)
       at java.lang.reflect.Method.invoke(Method.java)
       at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:589)
       at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1071)

also:

          Fatal Exception: android.app.RemoteServiceException$ForegroundServiceDidNotStartInTimeException: Context.startForegroundService() did not then call Service.startForeground(): ServiceRecord{883ead4 u0 com.apolloscooters/com.google.android.libraries.geo.navcore.service.base.NavigationService c:com.apolloscooters}
       at android.app.ActivityThread.generateForegroundServiceDidNotStartInTimeException(ActivityThread.java:2675)
       at android.app.ActivityThread.throwRemoteServiceException(ActivityThread.java:2643)
       at android.app.ActivityThread.-$$Nest$mthrowRemoteServiceException()
       at android.app.ActivityThread$H.handleMessage(ActivityThread.java:3068)
       at android.os.Handler.dispatchMessage(Handler.java:110)
       at android.os.Looper.loopOnce(Looper.java:273)
       at android.os.Looper.loop(Looper.java:363)
       at android.app.ActivityThread.main(ActivityThread.java:10060)
       at java.lang.reflect.Method.invoke(Method.java)
       at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:632)
       at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:975)
React Native version

0.81.5

React version

19.1.0

Package version

0.12.1

Native SDK versions
  • I haven't changed the version of the native SDKs
React Native Doctor Output

✓ Node.js - Required to execute JavaScript code
✓ yarn - Required to install NPM dependencies
✓ Watchman - Used for watching changes in the filesystem when in development mode
✓ Metro - Required for bundling the JavaScript code

Android
✓ Adb - Required to verify if the android device is attached correctly
✓ JDK - Required to compile Java code
✓ Android Studio - Required for building and installing your app on Android
✓ ANDROID_HOME - Environment variable that points to your Android SDK installation
✓ Gradlew - Build tool required for Android builds
✖ Android SDK - Required for building and installing your app on Android

  • Versions found: N/A
  • Version supported: 36.0.0

iOS
✓ Xcode - Required for building and installing your app on iOS
✓ Ruby - Required for installing iOS dependencies
✓ CocoaPods - Required for installing iOS dependencies
✓ .xcode.env - File to customize Xcode environment

Errors: 1
Warnings: 0

Steps to reproduce

I didn't manage to reproduce yet, but it might be related to the fact that we cleanup the navigation controller when the app goes in background.

Expected vs Actual Behavior

No crash...

Code Sample
// Example code here
Additional Context

No response

Langage dominant
TypeScript
Étoiles
226
Forks
39
Merge moyen
1 j 20 h
PR mergées (30 j)
7

Préparer son environnement

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Autres issues de googlemaps/react-native-navigation-sdk

Toutes les issues de googlemaps/react-native-navigation-sdk

Issues similaires

Plus d'issues TypeScript

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.