Crash on older devices (Android 4.4.2)

[LostInDarkMath]

I have released 4.2.1 that should force Java 8 on the package and prevent this error. Let me know if it's okay for you :)

Hi @Lyokone Does the update break support to Android API level 18? I think this incompatible. On my Android 4.4.2 phone, location 4.1.1. works fine, but 4.2.3 crashes.

06-13 17:47:39.144 19280-19280/com.foo.foo W/AccessibilityBridge: can't invoke getChildId with reflection
06-13 17:47:39.434 19280-19280/com.foo.foo I/dalvikvm: Failed resolving Lcom/lyokone/location/-$$Lambda$FlutterLocation$f8XcZ8MqI0jurqryNosbwR0gzsU; interface 285 'Landroid/location/OnNmeaMessageListener;'
06-13 17:47:39.434 19280-19280/com.foo.foo W/dalvikvm: Link of class 'Lcom/lyokone/location/-$$Lambda$FlutterLocation$f8XcZ8MqI0jurqryNosbwR0gzsU;' failed
06-13 17:47:39.434 19280-19280/com.foo.foo E/dalvikvm: Could not find class 'com.lyokone.location.-$$Lambda$FlutterLocation$f8XcZ8MqI0jurqryNosbwR0gzsU', referenced from method com.lyokone.location.FlutterLocation.createLocationCallback
06-13 17:47:39.434 19280-19280/com.foo.foo W/dalvikvm: VFY: unable to resolve new-instance 6876 (Lcom/lyokone/location/-$$Lambda$FlutterLocation$f8XcZ8MqI0jurqryNosbwR0gzsU;) in Lcom/lyokone/location/FlutterLocation;
06-13 17:47:39.434 19280-19280/com.foo.foo I/dalvikvm: Could not find method android.location.LocationManager.isLocationEnabled, referenced from method com.lyokone.location.FlutterLocation.checkServiceEnabled
06-13 17:47:39.434 19280-19280/com.foo.foo W/dalvikvm: VFY: unable to resolve virtual method 1633: Landroid/location/LocationManager;.isLocationEnabled ()Z
06-13 17:47:39.434 19280-19280/com.foo.foo I/dalvikvm: Could not find method android.location.LocationManager.addNmeaListener, referenced from method com.lyokone.location.FlutterLocation.lambda$startRequestingLocation$2$FlutterLocation

Original comment: https://github.com/Lyokone/flutterlocation/issues/576#issuecomment-860232163

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[LostInDarkMath]

I do not think that it's a good idea to close issues without any maintainer response.

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[LostInDarkMath]

I do not think that it's a good idea to close issues without any maintainer response.

Let's remove the inactive label, because only the maintainer is inactive.

[bartekpacia]

Please create a new issue if this problem still occurs on the latest v5 versions.