ionic-team / ionic-team/ion-android-geolocation

[Bug]: crash error report due to IllegalStateException - Already resumed

Open
#15 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
Kotlin
Stars
1
Forks
1
PR merge metrics
No merged PRs in 30d

Description

### Current Behavior

We received the following crash report from Crashlytics:
```
Fatal Exception: java.lang.IllegalStateException: Already resumed, but proposed with update Location[network 15******,121****** hAcc=312 et=+1d13h14m12s786ms vAcc=??? sAcc=??? bAcc=???]
at kotlinx.coroutines.CancellableContinuationImpl.alreadyResumedError(CancellableContinuationImpl.kt:556)
at kotlinx.coroutines.CancellableContinuationImpl.resumeImpl$kotlinx_coroutines_core(CancellableContinuationImpl.kt:521)
at kotlinx.coroutines.CancellableContinuationImpl.resumeImpl$kotlinx_coroutines_core$default(CancellableContinuationImpl.kt:493)
at kotlinx.coroutines.CancellableContinuationImpl.resumeWith(CancellableContinuationImpl.kt:359)
at io.ionic.libs.iongeolocationlib.controller.helper.IONGLOCFallbackHelper$getCurrentLocation$2$1$2.onLocationChanged(IONGLOCFallbackHelper.kt:52)
at android.location.LocationManager$ListenerTransport._handleMessage(LocationManager.java:518)
at android.location.LocationManager$ListenerTransport.access$000(LocationManager.java:304)
at android.location.LocationManager$ListenerTransport$2.handleMessage(LocationManager.java:333)
at android.os.Handler.dispatchMessage(Handler.java:112)
at android.os.Looper.loop(Looper.java:216)
at android.app.ActivityThread.main(ActivityThread.java:7625)
at java.lang.reflect.Method.invoke(Method.java)
at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:524)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:987)
```

This is on device with following properties:
```
Device
Brand: Huawei
Model: JKM-LX1
Orientation: Portrait
RAM free: 982.02 MiB
Disk free: 35.21 GiB
Operating System
Version:Android 9
Orientation: Portrait
Rooted: No
Crash
Date: Aug 16, 2026, 9:14:36 PM
App version: 4.0.2 (4000201)
```

It seems it may have occurred during some transition state from geo location being turned off to turning on.

### Expected Behavior

No crash

### Reproduction

https://console.firebase.google.com/

### Screenshots / Media

_No response_

### Environment Details

```Shell
reported from user
```

### Versions Affected

latest

### Platforms Affected

- [ ] iOS
- [x] Android
- [ ] Web

### Notes / Comments

_No response_

Contributor guide

No contributing guide indexed for this repository

Research direction

Start with IONGLOCFallbackHelper.kt at line 52, where the crash stack shows onLocationChanged resuming an already-resumed continuation. Trace how location updates behave during the reported transition from disabled to enabled, then verify that the Android location flow no longer produces the Already resumed crash.

Written by the indexing model from the issue text.

Assessment

Tech stack
android, kotlin
Domain
mobile-dev
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
55/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.