#mokembo-android

1 messages · Page 1 of 1 (latest)

fringe fulcrum
rich kayak
#

Hi

fringe fulcrum
#

Hi there!

rich kayak
#

What's the solution for this cause they are continuously rejecting app

fringe fulcrum
rich kayak
#

they are keep saying this
we’ve identified that your app is using Stripe SDK or library, which facilitates the transmission and collection of users' installed application and phone number information without posting a privacy policy from within the Play distributed app itself.

#

we already mention this in App and in privacy policy link

fringe fulcrum
#

As we do not have any context on their reasons behind rejecting apps 🙇

#

Maybe you should ask their team directly what information they are looking for that is missing in your policy

rich kayak
#

The only one reason they are saying is this
regarding Stripe SDK

fringe fulcrum
#

Could you please ask them what is missing in your policy in order to use the Stripe SDK?

rich kayak
#

Hi Developers at xxxx,

Thanks for contacting the Google Play team.

Status: Latest app update not available on Google Play

I’ve reviewed your appeal request and found that your app, The Perfect Gentleman (com.xxx.xxx, App bundle:15, Track: Production) is not compliant with Google Play Policy. If you submitted an update to an existing app, the version published prior to the update is still available on Google Play. I’ve included details below about the specific issue with your app and what you can do to get your app on Google Play.

Step 1: Fix the policy issue with your app

During review, we found that your app doesn’t comply with the User Data and Mobile Unwanted Software policies. We don’t allow apps that are potentially harmful to the user experience. You can read through the User Data and Mobile Unwanted Software policy pages for more details and examples of common violations.

For example, we’ve identified that your app is using Stripe SDK or library, which facilitates the transmission and collection of users' installed application and phone number information without posting a privacy policy from within the Play distributed app itself.

We acknowledge that you have provided a valid privacy policy on the Play Console, however, please ensure to have it posted within the in-app as well.

#

They are saying only this nothing else

fringe fulcrum
#

I see, thank you for posting a privacy policy within the app, I think what Google wants is a message in your app (in-app) to let the customers know you will be collecting information from them when they make a payment via Stripe SDK.

rich kayak
#

Yes we also do that by opening dialog with "Disclosure" with this above text that we are using and sharing with stripe
and even we put the checkbox and accept button so he can not proceed without checkbox and agree button

fringe fulcrum
#

Sorry, just wanted to clarify, there is a checkbox and accept button for the customers to "sign" a Disclosure form?

rich kayak
#

yes

fringe fulcrum
#

Maybe you should take a video of this and send it to Google, it is possible they have missed this in the code, or if there are specific pages in your app they would also like to see this information. It would be the best to clarify with them.

rich kayak
#

When we submit for review we send them credentials and screenshots of privacy policy from link and from app also then also they reject update

#

See this again same message from them even they are not clearly mention what they want

unknown.png
fringe fulcrum
#

It does look like a potential verification mistake, I suggest you to chat to one of their support team agents to look into this

#

As they have full control over the app acceptance process, if you share with them these information in person, I am sure they will try their best to help 🙂

#

Please write into them and show them your screen shots and the rejection message, clearly indicate the specified information they have requested have been included in the app

rich kayak
#

We already contact them through this page and they replay same

turbid cedar
#

👋 stepping in since makoto is signing off for the day. Give me a few mins to catchup

rich kayak
turbid cedar
#

Could you verify which version you are using?

rich kayak
#

implementation "com.stripe:stripe-java:17.9.1"
implementation 'com.stripe:stripe-android:13.2.0'

turbid cedar
#

I believe that answer has some really good step-by-step actions

rich kayak
#

According to there comments i see he used version 17.9.1 and the guy on Github he said he got the issue in same version

#

can you suggest me which version should be good to use

turbid cedar
rich kayak
#

Let me try this one cause this one i am getting duplicate class error
Duplicate class androidx.lifecycle.DefaultLifecycleObserver found in modules lifecycle-common-2.4.1.jar

turbid cedar
#

That error message normally will have further part , like duplicate class in XXX and YYY

rich kayak
#

1 exception was raised by workers:
java.lang.RuntimeException: java.lang.RuntimeException: Duplicate class androidx.lifecycle.DefaultLifecycleObserver found in modules lifecycle-common-2.4.1.jar (androidx.lifecycle:lifecycle-common:2.4.1) and lifecycle-common-java8-2.3.0.jar (androidx.lifecycle:lifecycle-common-java8:2.3.0)

Go to the documentation to learn how to <a href="d.android.com/r/tools/classpath-sync-errors">Fix dependency resolution errors</a>.

turbid cedar
rich kayak
#

there is not lib like
lifecycle-common-java8-2.3.0 in main app gradle may be some other lib were using that
i applied this solution but it didn't resolve problem

now it shows
Execution failed for task ':app:processDebugManifest'.

Manifest merger failed with multiple errors, see logs