App being rejected due to not meeting compliance [Health - Other]

[perotem7]

Your Environment

• Plugin version: 4.17.6
• Platform: Android
• OS version: NA
• Device manufacturer / model: NA
• React Native version (react-native -v): 0.75.2
• Plugin config

{
    // Geolocation Config
    desiredAccuracy: BackgroundGeolocation.DESIRED_ACCURACY_HIGH,
    distanceFilter: 10,
    stopTimeout: 5,
    debug: false, 
    logLevel: BackgroundGeolocation.LOG_LEVEL_WARNING,
    stopOnTerminate: false,  
    startOnBoot: false,      
}

Expected Behavior

App approved by google and released on the store.

Actual Behavior

The app gets rejected for not meeting compliance requirements.

I reviewed the issues section of this repo and read 2031 and 1953 as well as your blog post, but it seams that the issue we're facing is a bit different.

Upon installation we display a very descriptive dialog explaining why we require the FOREGROUND permissions.

We've tried your recommendations for the blog post, adding several versions of declaration text and video, with no help.

Google are complaining for 3 reasons:

1. Issue found: Service interruption or deferment of functionality does not have material user impact
   We found that one or more of the declared use cases is not compliant with how foreground service permission is allowed to be used. Specifically, the declared use case(s) can be interrupted or deferred by the system without creating a negative user experience. Your app is using foreground service to Health - Other when it is not required to do so.

2. Issue found: Permission use is either not declared or incorrectly declared
   We found that one or more of the use cases utilizing the foreground service permission in your app has either been incorrectly submitted or is missing from your Console declaration.
   Your app is utilizing foreground service to Health - Other, but you have not disclosed this in your declaration or it is not required.

3. Issue found: Functionality is not initiated by or perceptible to the user
   We found that one or more of the declared use cases is not compliant with how foreground service permission is allowed to be used. Specifically, the user is not made aware of functionality requiring permission when active. Use of FGS is not perceptible to the user when performing Health - Other functionality.

If you or anyone have any guidance that may help us go past this hurdle it would be highly appreciated.

[ReiDx]

Same issue, any update?

[christocracy]

Follow my blog linked above. It’s what I used to publish the demo app.

It’s completely between you and the Play Store,

[perotem7]

We got the app approved 😀🎉

In case anyone else encounters this issue, this is what we did:

• We filed an appeal through play console. This resulted with a mail thread which enabled asking questions and getting clarifications.
• We then realized that the main complaint by Google was that they couldn't understand why our specific use case required foreground services (see complain no. 1 above).
• We then explained in details (over mail) why we do require foreground services.
• At this point google approved the app, requesting that we remove "Health - other" from our declarations.
• App got approved.

[christocracy]

At this point google approved the app, requesting that we remove "Health - other" from our declarations.

Can you explain more about how exactly you “removed Health (Other)”?

[perotem7]

At this point google approved the app, requesting that we remove "Health - other" from our declarations.

Can you explain more about how exactly you “removed Health (Other)”?

"Health - other" as in one of the declarations on google play console. When you submit an app, there's a section called "Policy and programs" on the left pane. When you expand it you'll find an item labeled "App content", select it and you'll see 2 tabs, one of which labeled "Actioned".

In the Actioned tab you'll see all sorts of items google identified in your app that are related to policies. There you can provide explanations related to your app.

In our case, under "Foreground service permissions" we checked "Health - other" section, which was a mistake.

Hope this clears up things.

[christocracy]

Thanks, I’ll investigate that in my Play Console.

[ademirtemur]

this works, add these lines.

<uses-permission android:name="android.permission.ACTIVITY_RECOGNITION" tools:node="remove" />
<uses-permission android:name="android.permission.FOREGROUND_SERVICE_HEALTH" tools:node="remove" />