Durank

Hello... any response about this?

This what I don't to avoid your hard code dialog in the Location Api. Your read very well this issue?

The developers are tied Hands with your Hard code dialog. From Target 29 this error are occuring. I avoid this dialog with my native Request permission Implemented, but with this...

this issue is occurring from android api 29,30. Google separate the way that you use the Location in foreground and background https://developer.android.com/training/location/permissions?hl=fr Now google decline our release App by this...

I have check your source code and I found that you have and option to avoid request background location.  I think that you must annunciate any change to your...

Please provide other solution to this hard code dialog. Create and interface or callback in the Codenameone side to notify permission required and the developer can create its own dialog....

> Notice that option is "false" by default. Meaning that it does NOT request background permissions in this block unless you explicitly set that display property. > > This option...

your are hard coding in your generated build server code the background location. this the main cause why this impact my app. Google now decline all app that don't justify...

Not I'm not using. I just use LocationManager api.

no I just call this method in the iphone side when goes to background. I just call this method in android side to delete this location by error when I...