Open Luis-Leonidas-Fernandez opened 4 weeks ago
Hi @Luis-Leonidas-Fernandez ,
The geolocator
plugin should automatically add the correct <service ../>
element to the applications manifest file when the application is compiled into an appbundle or apk file.
Easiest way to validate this is by analyzing the .apk using Android Studio:
In my tests the application contains the following service declaration (note that there was no need for me to add this myself to the AndroidManifest.xml
file):
<service
android:name="com.baseflow.geolocator.GeolocatorLocationService"
android:enabled="true"
android:exported="false"
android:foregroundServiceType="0x8" />
The value 0x8
translates to the location
enum value as documented here: https://developer.android.com/reference/android/R.attr#foregroundServiceType
Can you verify if this is also the case for your application. If you add your own <service ... />
declaration please try to remove it. Or if the declaration in missing in your final AndroidManifest.xml
file please try adding it manually in the android/app/src/main/AndroidManifest.xml
by copy/ pasting the above XML.
Please let me know if this helped.
Please check the following before submitting a new issue.
Please select for which platform(s) you need help
Your question
Incorrect foreground service type From Android 14, developers must specify service types when foreground services are found in their app's manifest. Starting services with different types may cause your app to crash.
Your app's manifest declares com.baseflow.geolocator.GeolocatorLocationService, which starts in the foreground in the following place:
com.baseflow.geolocator.GeolocatorLocationService.com.baseflow.geolocator.GeolocatorLocationService.f Make sure that service types passed to startForeground() match what is specified in your app's manifest.
geolocator: ^13.0.1
Version
13.0.1