-
-
Notifications
You must be signed in to change notification settings - Fork 653
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Question]: Incorrect foreground service type From Android 14 - Publishing overview - Play Store #1558
Comments
I have the same problem, I still don't know how to solve it. |
Dear @developerflutter, When do you see this message? Is this message coming from the play store? Kind regards, |
Dear @developerflutter, Can you paste the contents of your app manifest to this issue? It helps a lot investigating and resolving this issue. Kind regards, |
|
The 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 <service
android:name="com.baseflow.geolocator.GeolocatorLocationService"
android:enabled="true"
android:exported="false"
android:foregroundServiceType="0x8" /> The value Can you verify if this is also the case for your application. If you add your own Please let me know if this helped. |
Without additional information, we are unfortunately not able to resolve this issue. Therefore, we reluctantly closed this issue for now. If you run into this issue later, feel free to file a new issue with a reference to this issue. Add a description of detailed steps to reproduce, expected and current behaviour, logs and the output of 'flutter doctor -v'. Thanks for your contribution. |
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
The text was updated successfully, but these errors were encountered: