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

Offen
  • Stimmt etwas nicht?
#526 6 Kommentare 0 Reaktionen 2 zugewiesene Personen Auf GitHub ansehen

Maintainer antworten meist innerhalb von 5 Tagen

@illuminati1911 arbeitet bereits daran.

Seit 17.3.2026.

Bewertung

Dieses Issue wurde noch nicht bewertet.

Beschreibung

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

Vorherrschende Sprache
TypeScript
Sterne
226
Forks
39
Ø Merge
1 T. 20 Std.
Gemergte PRs (30 T.)
7

Entwicklungsumgebung

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus googlemaps/react-native-navigation-sdk

Alle Issues in googlemaps/react-native-navigation-sdk

Ähnliche Issues

Weitere Issues zu TypeScript

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.