[Question]: Incorrect foreground service type From Android 14 - Publishing overview - Play Store

[developerflutter]

Please check the following before submitting a new issue.

• I have searched the existing issues.
• I have carefully read the documentation.

Please select for which platform(s) you need help

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

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

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

Version

13.0.1

[Luis-Leonidas-Fernandez]

I have the same problem, I still don't know how to solve it.

[TimHoogstrate]

Dear @developerflutter,

When do you see this message? Is this message coming from the play store?

Kind regards,

[developerflutter]

Yes it's in Publishing overview.
Screenshots attached.

[TimHoogstrate]

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,

[developerflutter]

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

<service
        android:name="id.flutter.flutter_background_service.BackgroundService"
        android:foregroundServiceType="location"
 />

[mvanbeusekom]

Hi @developerflutter,

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:

1. Make sure to build an .apk of your application.
2. Open Android Studio and go to "Build" -> "Analyze APK" (no need to open a project first).
3. Next navigate to the .apk file that you just build and is should show the final AndroidManifest file for your application.

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.

[github-actions]

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.