[Bug]: App crashes when calling getCurrentPosition()

[muhammad67uzair]

Please check the following before submitting a new issue.

• I have searched the existing issues.
• I have carefully read the documentation and verified I have added the required platform specific configuration.

Please select affected platform(s)

• Android
• iOS
• Linux
• macOS
• Web
• Windows

Steps to reproduce

1. add the geolocator plugin
2. add the access.coarse.location permission in androidmanifest.xml
3. call geolocator.getCurrentPosition();

Expected results

the coarse location/position of the user should be returned.

Actual results

App crashes when calling geolocator.getCurrentPosition();
i have added the android.permission.ACCESS_COARSE_LOCATION in my AndroidManifest.xml file, but when the app requests the user's current position the app crashes with the following exception:

D/AndroidRuntime(11738): Shutting down VM
E/AndroidRuntime(11738): FATAL EXCEPTION: main
E/AndroidRuntime(11738): java.lang.SecurityException: Neither user 10373 nor current process has android.permission.ACCESS_FINE_LOCATION.

although im not even requesting user's fine location.

I even tried specifying a specific geolocator version like 11.0.0 and previous ones but to no avail.

complete error log:

E/AndroidRuntime(11738): java.lang.SecurityException: Neither user 10373 nor current process has android.permission.ACCESS_FINE_LOCATION.
E/AndroidRuntime(11738): at android.os.Parcel.createExceptionOrNull(Parcel.java:3057)
E/AndroidRuntime(11738): at android.os.Parcel.createException(Parcel.java:3041)
E/AndroidRuntime(11738): at android.os.Parcel.readException(Parcel.java:3024)
E/AndroidRuntime(11738): at android.os.Parcel.readException(Parcel.java:2966)
E/AndroidRuntime(11738): at android.location.ILocationManager$Stub$Proxy.registerGnssNmeaCallback(ILocationManager.java:1625)
E/AndroidRuntime(11738): at android.location.LocationManager$GnssNmeaTransportManager.registerTransport(LocationManager.java:3127)
E/AndroidRuntime(11738): at android.location.LocationManager$GnssNmeaTransportManager.registerTransport(LocationManager.java:3117)
E/AndroidRuntime(11738): at com.android.internal.listeners.ListenerTransportManager.addListener(ListenerTransportManager.java:70)
E/AndroidRuntime(11738): at android.location.LocationManager.addNmeaListener(LocationManager.java:2629)
E/AndroidRuntime(11738): at android.location.LocationManager.addNmeaListener(LocationManager.java:2610)
E/AndroidRuntime(11738): at com.baseflow.geolocator.location.NmeaClient.start(NmeaClient.java:76)
E/AndroidRuntime(11738): at com.baseflow.geolocator.location.FusedLocationClient.requestPositionUpdates(FusedLocationClient.java:157)
E/AndroidRuntime(11738): at com.baseflow.geolocator.location.FusedLocationClient.lambda$startPositionUpdates$2$com-baseflow-geolocator-location-FusedLocationClient(FusedLocationClient.java:240)
E/AndroidRuntime(11738): at com.baseflow.geolocator.location.FusedLocationClient$$ExternalSyntheticLambda3.onSuccess(Unknown Source:4)
E/AndroidRuntime(11738): at com.google.android.gms.tasks.zzm.run(com.google.android.gms:play-services-tasks@@18.1.0:1)
E/AndroidRuntime(11738): at android.os.Handler.handleCallback(Handler.java:958)
E/AndroidRuntime(11738): at android.os.Handler.dispatchMessage(Handler.java:99)
E/AndroidRuntime(11738): at android.os.Looper.loopOnce(Looper.java:224)
E/AndroidRuntime(11738): at android.os.Looper.loop(Looper.java:318)
E/AndroidRuntime(11738): at android.app.ActivityThread.main(ActivityThread.java:8720)
E/AndroidRuntime(11738): at java.lang.reflect.Method.invoke(Native Method)
E/AndroidRuntime(11738): at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:561)
E/AndroidRuntime(11738): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1013)
E/AndroidRuntime(11738): Caused by: android.os.RemoteException: Remote stack trace:
E/AndroidRuntime(11738): at android.app.ContextImpl.enforce(ContextImpl.java:2343)
E/AndroidRuntime(11738): at android.app.ContextImpl.enforceCallingOrSelfPermission(ContextImpl.java:2371)
E/AndroidRuntime(11738): at com.android.server.location.gnss.GnssManagerService.registerGnssNmeaCallback(GnssManagerService.java:206)
E/AndroidRuntime(11738): at com.android.server.location.LocationManagerService.registerGnssNmeaCallback(LocationManagerService.java:1151)
E/AndroidRuntime(11738): at android.location.ILocationManager$Stub.onTransact(ILocationManager.java:809)
E/AndroidRuntime(11738):
2
W/VideoCapabilities(11738): Unsupported mime image/vnd.android.heic
W/ScoutUtils(11738): Failed to mkdir /data/miuilog/stability/memleak/heapdump/
I/Process (11738): Process is going to kill itself!
I/Process (11738): java.lang.Exception
I/Process (11738): at android.os.Process.killProcess(Process.java:1356)
I/Process (11738): at com.android.internal.os.RuntimeInit$KillApplicationHandler.uncaughtException(RuntimeInit.java:174)
I/Process (11738): at org.chromium.base.JavaExceptionReporter.uncaughtException(chromium-TrichromeWebViewGoogle6432.aab-stable-636712333:27)
I/Process (11738): at com.datadog.android.error.internal.DatadogExceptionHandler.uncaughtException(DatadogExceptionHandler.kt:98)
I/Process (11738): at java.lang.ThreadGroup.uncaughtException(ThreadGroup.java:1071)
I/Process (11738): at java.lang.ThreadGroup.uncaughtException(ThreadGroup.java:1066)
I/Process (11738): at java.lang.Thread.dispatchUncaughtException(Thread.java:2306)
Lost connection to device.

Code sample

Code sample

  Future<void> _updateUserLocation() async {
    LocationPermission permission = await Geolocator.checkPermission();
    if (<LocationPermission>[LocationPermission.denied, LocationPermission.deniedForever]
        .contains(permission)) {
      permission = await Geolocator.requestPermission();
      if (<LocationPermission>[
        LocationPermission.denied,
        LocationPermission.deniedForever,
      ].contains(permission)) {
        throw Exception(
          'Location permissions are permanently denied, we cannot request permissions.',
        );
      }
    }
    permission = await Geolocator.checkPermission();
    if (<LocationPermission>[LocationPermission.whileInUse, LocationPermission.always]
        .contains(permission)) {
      final Position position = await Geolocator.getCurrentPosition(
        desiredAccuracy: LocationAccuracy.high,
      );
  }

Screenshots or video

Screenshots or video demonstration

[Upload media here]

Version

12.0.0

Flutter Doctor output

Doctor output

Doctor summary (to see all details, run flutter doctor -v):
[✓] Flutter (Channel stable, 3.16.9, on macOS 14.4.1 23E224 darwin-arm64, locale
    en-AU)
[✓] Android toolchain - develop for Android devices (Android SDK version 34.0.0)
[✓] Xcode - develop for iOS and macOS (Xcode 15.3)
[✓] Chrome - develop for the web
[✓] Android Studio (version 2023.1)
[✓] VS Code (version 1.89.1)
[✓] Connected device (3 available)
    ! Error: Browsing on the local area network for Avialdo’s iPhone Xr. Ensure
      the device is unlocked and attached with a cable or associated with the
      same local area network as this Mac.
      The device must be opted into Developer Mode to connect wirelessly. (code
      -27)
    ! Error: Browsing on the local area network for Avialdo Solutions’s iPhone
      12 mini. Ensure the device is unlocked and attached with a cable or
      associated with the same local area network as this Mac.
      The device must be opted into Developer Mode to connect wirelessly. (code
      -27)
[✓] Network resources

• No issues found!

[RokuIL]

+1

[mvanbeusekom]

Try specifying a lower accuracy.

Acquiring a location with accuracy of high and up require the fine permission.

[RokuIL]

Try specifying a lower accuracy.

Acquiring a location with accuracy of high and up require the fine permission.

This is with low accuracy:
Position position = await Geolocator.getCurrentPosition(desiredAccuracy: LocationAccuracy.low);

It worked fine with version 11.0.0, but not with 12.0.0

[RokuIL]

@muhammad67uzair

After upgrading from 11.0.0 (worked) to 12.0.0 (crashed), reverting back to 11.0.0 wasn't enough. I needed to restore the values in my pubspec.lock to:

geolocator:
dependency: "direct main"
description:
name: geolocator
sha256: "694ec58afe97787b5b72b8a0ab78c1a9244811c3c10e72c4362ef3c0ceb005cd"
url: "https://pub.dev"
source: hosted
version: "11.0.0"
geolocator_android:
dependency: transitive
description:
name: geolocator_android
sha256: f15d1536cd01b1399578f1da1eb5d566e7a718db6a3648f2c24d2e2f859f0692
url: "https://pub.dev"
source: hosted
version: "4.5.4"
geolocator_apple:
dependency: transitive
description:
name: geolocator_apple
sha256: bc2aca02423ad429cb0556121f56e60360a2b7d694c8570301d06ea0c00732fd
url: "https://pub.dev"
source: hosted
version: "2.3.7"
geolocator_platform_interface:
dependency: transitive
description:
name: geolocator_platform_interface
sha256: "009a21c4bc2761e58dccf07c24f219adaebe0ff707abdfd40b0a763d4003fab9"
url: "https://pub.dev"
source: hosted
version: "4.2.2"
geolocator_web:
dependency: transitive
description:
name: geolocator_web
sha256: "49d8f846ebeb5e2b6641fe477a7e97e5dd73f03cbfef3fd5c42177b7300fb0ed"
url: "https://pub.dev"
source: hosted
version: "3.0.0"
geolocator_windows:
dependency: transitive
description:
name: geolocator_windows
sha256: "53da08937d07c24b0d9952eb57a3b474e29aae2abf9dd717f7e1230995f13f0e"
url: "https://pub.dev"
source: hosted
version: "0.2.3"

[muhammad67uzair]

Try specifying a lower accuracy.

Acquiring a location with accuracy of high and up require the fine permission.

@mvanbeusekom i tried specifying the low accuracy but it still didn't work, i even added the ACCESS_FINE_LOCATION permission in my manifest file, with both low and high accuracies but still got the same error.

also it used to work before with high accuracy without the need to add the ACCESS_FINE_LOCATION permission, this happened after the version 12.0.0 and like @RokuIL said, reverting back to version 11.0.0 or even a previous version doesn't help.

[muhammad67uzair]

@muhammad67uzair

After upgrading from 11.0.0 (worked) to 12.0.0 (crashed), reverting back to 11.0.0 wasn't enough. I needed to restore the values in my pubspec.lock to:

geolocator: dependency: "direct main" description: name: geolocator sha256: "694ec58afe97787b5b72b8a0ab78c1a9244811c3c10e72c4362ef3c0ceb005cd" url: "https://pub.dev" source: hosted version: "11.0.0" geolocator_android: dependency: transitive description: name: geolocator_android sha256: f15d1536cd01b1399578f1da1eb5d566e7a718db6a3648f2c24d2e2f859f0692 url: "https://pub.dev" source: hosted version: "4.5.4" geolocator_apple: dependency: transitive description: name: geolocator_apple sha256: bc2aca02423ad429cb0556121f56e60360a2b7d694c8570301d06ea0c00732fd url: "https://pub.dev" source: hosted version: "2.3.7" geolocator_platform_interface: dependency: transitive description: name: geolocator_platform_interface sha256: "009a21c4bc2761e58dccf07c24f219adaebe0ff707abdfd40b0a763d4003fab9" url: "https://pub.dev" source: hosted version: "4.2.2" geolocator_web: dependency: transitive description: name: geolocator_web sha256: "49d8f846ebeb5e2b6641fe477a7e97e5dd73f03cbfef3fd5c42177b7300fb0ed" url: "https://pub.dev" source: hosted version: "3.0.0" geolocator_windows: dependency: transitive description: name: geolocator_windows sha256: "53da08937d07c24b0d9952eb57a3b474e29aae2abf9dd717f7e1230995f13f0e" url: "https://pub.dev" source: hosted version: "0.2.3"

@RokuIL thanks, that worked!

[corepuncher]

Both .medium and .high have always worked for me using:

  <uses-permission android:name="android.permission.ACCESS_FINE_LOCATION" />
  <uses-permission android:name="android.permission.ACCESS_COARSE_LOCATION" />

However, geolocator no longer works for my Windows app. It puts my location in southern Virginia. And it's not my computer, because I built the app and sent it to someone in another state, and they too show Virginia as the location. Any thoughts on this would be appreciated. Am I the only one with this issue so far?

[muhammad67uzair]

based on @RokuIL's comment, it seems to be an issue in the platform specific geolocator packages that geolocator itself depends upon.

The issue seems to be in the geolocator_android package.

instead of manually modifying the pubspec.lock file, we could just directly specify the versions of the packages that geolocator itself depends upon in our pubspec.yaml file like this:

dependencies:
geolocator: 11.0.0
geolocator_android: 4.5.4

or like

dependencies:
geolocator: 11.0.0

dependency_overrides:
geolocator_android: 4.5.4

this fixes it for me.

[rminkler1]

I'm seeing this as well. Coarse location does not seem to be used in the latest geolocator_android 4.6.0, regardless of desiredAccuracy setting. FINE permissions are required. These workarounds helped me get COARSE location working without crashes.

I just tested these dependencies in pubspec.yaml:

dependencies:
  geolocator: ^12.0.0
  geolocator_android: 4.5.5

It works fine. Clearly it is an issue with the newer geolocator_android release.
There were some major changes in 4.6.0 according to the changelog

I've been following a tutorial as I learn Flutter, updated Flutter. Could not figure out why this app kept crashing. Saw it is a location FINE permissions issue. I'm glad it's not just me doing something stupid.

[cedvdb]

Same even with fine location enabled:

  <uses-permission android:name="android.permission.ACCESS_FINE_LOCATION" />
  <uses-permission android:name="android.permission.ACCESS_COARSE_LOCATION" />

Adding the override fixes the issue

# Fix for https://github.com/Baseflow/flutter-geolocator/issues/1515
dependency_overrides:
  geolocator_android: 4.5.4

[KirillArtemenko]

I confirm that geolocator 12.0.0 works well with geolocator_android 4.5.5.
I'll probably stay with this configuration.

Interestingly, on Pixel running the latest Android 4.6.0 everything works fine, but on Xiaomi it crashes at 50% rate.

Obviously, this commit make this issue: 6b34beb

[agboolaidris]

This work for me