Android Question Problem when setting targetSdkVersion=34 on background location app

[vikingivesterled]

App with background location run under foreground permission as recommended
now failes on startup and gives the following error:

java.lang.SecurityException: Starting FGS with type location callerApp=ProcessRecord{8fce9ec 12241:mobi.moonc.anchorwatch/u0a374} targetSDK=34 requires permissions: all of the permissions allOf=true [android.permission.FOREGROUND_SERVICE_LOCATION] any of the permissions allOf=false [android.permission.ACCESS_COARSE_LOCATION, android.permission.ACCESS_FINE_LOCATION] and the app must be in the eligible state/exemptions to access the foreground only permission


Works with targetSdkVersion=33

Posted as requested sample by Erel in thread 161928 post 11

We are getting close to the August 31 deadline now if one have many apps to update.

 

[vikingivesterled]

Complete error message:

servicetimer3_service_start (java line: 394)
java.lang.SecurityException: Starting FGS with type location callerApp=ProcessRecord{8fce9ec 12241:mobi.moonc.anchorwatch/u0a374} targetSDK=34 requires permissions: all of the permissions allOf=true [android.permission.FOREGROUND_SERVICE_LOCATION] any of the permissions allOf=false [android.permission.ACCESS_COARSE_LOCATION, android.permission.ACCESS_FINE_LOCATION] and the app must be in the eligible state/exemptions to access the foreground only permission
at android.os.Parcel.createExceptionOrNull(Parcel.java:3069)
at android.os.Parcel.createException(Parcel.java:3053)
at android.os.Parcel.readException(Parcel.java:3036)
at android.os.Parcel.readException(Parcel.java:2978)
at android.app.IActivityManager$Stub$Proxy.setServiceForeground(IActivityManager.java:7220)
at android.app.Service.startForeground(Service.java:775)
at anywheresoftware.b4a.objects.ServiceHelper.StartForeground(ServiceHelper.java:85)
at mobi.moonc.anchorwatch.servicetimer3._service_start(servicetimer3.java:394)
at java.lang.reflect.Method.invoke(Native Method)
at anywheresoftware.b4a.BA.raiseEvent2(BA.java:221)
at anywheresoftware.b4a.BA.raiseEvent(BA.java:201)
at mobi.moonc.anchorwatch.servicetimer3.handleStart(servicetimer3.java:103)
at mobi.moonc.anchorwatch.servicetimer3.access$000(servicetimer3.java:8)
at mobi.moonc.anchorwatch.servicetimer3$1.run(servicetimer3.java:74)
at anywheresoftware.b4a.objects.ServiceHelper$StarterHelper.onStartCommand(ServiceHelper.java:240)
at mobi.moonc.anchorwatch.servicetimer3.onStartCommand(servicetimer3.java:72)
at android.app.ActivityThread.handleServiceArgs(ActivityThread.java:5268)
at android.app.ActivityThread.-$$Nest$mhandleServiceArgs(Unknown Source:0)
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:2531)
at android.os.Handler.dispatchMessage(Handler.java:106)
at android.os.Looper.loopOnce(Looper.java:230)
at android.os.Looper.loop(Looper.java:319)
at android.app.ActivityThread.main(ActivityThread.java:8918)
at java.lang.reflect.Method.invoke(Native Method)
at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:608)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1103)
Caused by: android.os.RemoteException: Remote stack trace:
at com.android.server.am.ActiveServices.validateForegroundServiceType(ActiveServices.java:2741)
at com.android.server.am.ActiveServices.setServiceForegroundInnerLocked(ActiveServices.java:2452)
at com.android.server.am.ActiveServices.setServiceForegroundLocked(ActiveServices.java:1797)
at com.android.server.am.ActivityManagerService.setServiceForeground(ActivityManagerService.java:15880)
at android.app.IActivityManager$Stub.onTransact$setServiceForeground$(IActivityManager.java:11916)

 

[mangojack]

One of the issues is you are using a Foreground Service.

See Erel's statement regarding this Here ...


This recent Snippet by @Addo might help. It solves his issue with a Media Playback app, but you should be able to adapt it for your scenario.

https://www.b4x.com/android/forum/threads/targetsdkversion-34-foreground-service-for-mediaplayba

ps: Unsure if Location Permission's need addressing as well.

 

[Scantech]

App with background location run under foreground permission as recommended
now failes on startup and gives the following error:

java.lang.SecurityException: Starting FGS with type location callerApp=ProcessRecord{8fce9ec 12241:mobi.moonc.anchorwatch/u0a374} targetSDK=34 requires permissions: all of the permissions allOf=true [android.permission.FOREGROUND_SERVICE_LOCATION] any of the permissions allOf=false [android.permission.ACCESS_COARSE_LOCATION, android.permission.ACCESS_FINE_LOCATION] and the app must be in the eligible state/exemptions to access the foreground only permission


Works with targetSdkVersion=33

Posted as requested sample by Erel in thread 161928 post 11

We are getting close to the August 31 deadline now if one have many apps to update.

see if this helps. foregroundServiceType .

Also, might want to check this out. Check the manifest. New permissions are required.
Location example

 

[DonManfred]

Read https://www.b4x.com/android/forum/threads/background-location-tracking.99873/
The Example is updated to use 34.

Updates:

- Project updated with targetSdkVersion = 34.
This update required several changes:

1. New non-dangerous permission:
   B4X:
   
   AddPermission(android.permission.FOREGROUND_SERVICE_LOCATION)

• 
  With the above change the service can be started from the activity and run theoretically forever. However if we also want to start tracking after the device is booted then we need to follow several additional steps:
• We need to receive the ACCESS_BACKGROUND_LOCATION permission. This is a special permission and it is granted in the settings app. We can only help the user get into the settings app - see Activity_Resume code.
• The Tracker service can no longer be started after boot directly. This is related to the fact that we must make it a foreground service and it is impossible to do without the ACCESS_BACKGROUND_LOCATION permission. So the solution is to add a Receiver that starts after boot (see manifest editor), checks whether we have the permission and then starts the service with a call to StartForegroundService sub. Note that this sub doesn't actually moves the service to the foreground state. Instead it tells the system that the target service will be moved to the foreground. This is something that is required since Android 8 and in previous cases it was possible to manage it internally.

 

[Erel]

Add this line to the manifest editor:

AddPermission(android.permission.FOREGROUND_SERVICE_LOCATION)

 

[vikingivesterled]

Thanks for all help.
Adding android.permission.FOREGROUND_SERVICE_LOCATION solved the error problem.
Before I had just android.permission.FOREGROUND_SERVICE