Android App Publish Rejected From Play-store.

by ADMIN 46 views

Introduction

Publishing an Android app on the Google Play Store can be a daunting task, especially when it comes to dealing with app rejection. In this article, we will guide you through the process of resolving the issue of Android app publish rejected from the Play Store due to permission use not directly related to the app's core purpose.

Describe the Bug

When submitting an Android app to the Google Play Store, it's not uncommon to encounter issues related to permission use. In this case, the issue is that the READ_MEDIA_IMAGES/READ_MEDIA_VIDEO permissions are not being used directly in the app's core purpose. This can be a confusing issue, especially when you're not using any camera access, image, or video access from storage in your entire application.

To Reproduce

To reproduce this issue, follow these steps:

  1. Create a .aab file of your Android app.
  2. Upload the file to the Google Play Console.
  3. Wait for a server-hour review.
  4. Once the review is complete, check the app's status in the Google Play Console.

Expected Behavior

As per the documentation, the expected behavior is to add the necessary permissions in the AndroidManifest.xml file. However, in this case, the issue is that the READ_MEDIA_IMAGES/READ_MEDIA_VIDEO permissions are not being used directly in the app's core purpose.

Screenshots

To help explain the problem, add screenshots of the app's code and the error message received from the Google Play Console.

Stripe Terminal React Native SDK Version

The version of the Stripe Terminal React Native SDK being used is @stripe/stripe-terminal-react-native: ^0.0.1-beta.18, and the version of React Native is 0.73.6.

Smartphone Information

Provide information about the smartphone being used, including the model, operating system, and any other relevant details.

Additional Context

The additional context provided is that the user is seeking help from @nazli-stripe.

Resolving the Issue

To resolve this issue, follow these steps:

Step 1: Review the App's Code

Review the app's code to ensure that the READ_MEDIA_IMAGES/READ_MEDIA_VIDEO permissions are not being used directly in the app's core purpose.

Step 2: Remove Unnecessary Permissions

Remove any unnecessary permissions from the AndroidManifest.xml file.

Step 3: Update the App's Manifest File

Update the app's manifest file to reflect the changes made in the previous step.

Step 4: Rebuild and Resubmit the App

Rebuild the app and resubmit it to the Google Play Console.

Conclusion

Resolving the issue of Android app publish rejected from the Play Store due to permission use not directly related to the app's core purpose requires a thorough review of the app's code and manifest file. By following the steps outlined in this article, you can resolve this issue and successfully publish your Android app on the Google Play Store.

Troubleshooting Tips

  • Ensure that the READ_MEDIA_IMAGES/READ_MEDIA_VIDEO permissions are not being used directly in the app's core purpose.
  • Review the app's code and manifest file to ensure that all necessary permissions are declared.
  • Remove any unnecessary permissions from the AndroidManifest.xml file.
  • Update the app's manifest file to reflect the changes made in the previous step.
  • Rebuild the app and resubmit it to the Google Play Console.

Common Issues

  • Permission Use Not Directly Related to App's Core Purpose: This is the most common issue related to permission use in Android apps.
  • Unnecessary Permissions: Declaring unnecessary permissions in the AndroidManifest.xml file can lead to app rejection.
  • Manifest File Issues: Issues with the manifest file can cause app rejection.

Best Practices

  • Review the App's Code: Regularly review the app's code to ensure that all necessary permissions are declared.
  • Use Necessary Permissions: Only declare necessary permissions in the AndroidManifest.xml file.
  • Update the Manifest File: Regularly update the manifest file to reflect changes made to the app's code.

Conclusion

Introduction

In our previous article, we discussed the issue of Android app publish rejected from the Play Store due to permission use not directly related to the app's core purpose. In this article, we will provide a Q&A guide to help you resolve this issue and successfully publish your Android app on the Google Play Store.

Q: What are the common reasons for Android app publish rejection due to permission use?

A: The common reasons for Android app publish rejection due to permission use are:

  • Permission use not directly related to the app's core purpose
  • Unnecessary permissions declared in the AndroidManifest.xml file
  • Manifest file issues

Q: How can I resolve the issue of permission use not directly related to the app's core purpose?

A: To resolve this issue, follow these steps:

  1. Review the app's code to ensure that all necessary permissions are declared.
  2. Remove any unnecessary permissions from the AndroidManifest.xml file.
  3. Update the app's manifest file to reflect the changes made in the previous step.
  4. Rebuild the app and resubmit it to the Google Play Console.

Q: What are the necessary permissions that I need to declare in the AndroidManifest.xml file?

A: The necessary permissions that you need to declare in the AndroidManifest.xml file depend on the features and functionality of your app. Some common permissions include:

  • android.permission.BLUETOOTH_CONNECT
  • android.permission.BLUETOOTH_SCAN
  • android.permission.ACCESS_FINE_LOCATION
  • android.permission.ACCESS_COARSE_LOCATION

Q: How can I ensure that I am declaring the correct permissions in the AndroidManifest.xml file?

A: To ensure that you are declaring the correct permissions in the AndroidManifest.xml file, follow these steps:

  1. Review the app's code to determine which permissions are required.
  2. Declare the necessary permissions in the AndroidManifest.xml file.
  3. Remove any unnecessary permissions from the AndroidManifest.xml file.
  4. Update the app's manifest file to reflect the changes made in the previous step.

Q: What are the consequences of declaring unnecessary permissions in the AndroidManifest.xml file?

A: Declaring unnecessary permissions in the AndroidManifest.xml file can lead to app rejection. This is because the Google Play Store requires that apps only declare the necessary permissions to function.

Q: How can I troubleshoot issues related to permission use in my Android app?

A: To troubleshoot issues related to permission use in your Android app, follow these steps:

  1. Review the app's code to determine which permissions are required.
  2. Declare the necessary permissions in the AndroidManifest.xml file.
  3. Remove any unnecessary permissions from the AndroidManifest.xml file.
  4. Update the app's manifest file to reflect the changes made in the previous step.
  5. Rebuild the app and resubmit it to the Google Play Console.

Q: What are the best practices for declaring permissions in the AndroidManifest.xml file?

A: The best practices for declaring permissions in the AndroidManifest.xml file are:

  • Declare only the necessary permissions to function.
  • Review the app's code to determine which permissions are required.
  • Remove any unnecessary permissions from the AndroidManifest.xml file.
  • Update the app's manifest file to reflect the changes made in the previous step.

Conclusion

In conclusion, resolving the issue of Android app publish rejected from the Play Store due to permission use not directly related to the app's core purpose requires a thorough review of the app's code and manifest file. By following the steps outlined in this article and adhering to best practices, you can successfully publish your Android app on the Google Play Store.