I set uses-feature android:required=”false” but Google play keeps insisting on these features

I set uses-feature android:required=”false” but Google Play keeps insisting on these features

You’ve set the android:required="false" attribute in your uses-feature tags, but Google Play keeps insisting that your app requires those features. This is a common issue, and it can be frustrating when you’re trying to build a flexible app that can run on a wider range of devices.

Understanding the Problem

How Google Play Determines Compatibility

Google Play analyzes your app’s AndroidManifest.xml file to determine its compatibility with different devices. The uses-feature tag tells Google Play which features your app needs to function correctly.

The android:required Attribute

The android:required attribute within the uses-feature tag specifies whether the feature is strictly required for your app to work. Setting it to "false" indicates that your app will still function even if the device doesn’t have the feature.

The Issue

Despite setting android:required="false", Google Play might still believe your app needs the feature. This can occur due to several factors:

• Hardcoded Dependencies: Your app code might have hardcoded dependencies on the feature, even though it’s set as optional in the manifest. For example, directly using APIs that rely on the feature.
• Incorrect Feature Declarations: Your app might be incorrectly specifying the features it needs. Check the documentation for the correct names and values.
• Google Play Store Policies: Google Play might have specific requirements regarding the features your app needs to support, even if they’re not strictly required for its functionality.

Troubleshooting Steps

1. Inspect Your Code

Thoroughly examine your app’s code for any direct dependencies on the features you marked as optional.

// Example of hardcoded dependency:
// This code relies on the "android.hardware.camera.autofocus" feature
Camera camera = Camera.open();
camera.autoFocus(null);

If you find any such dependencies, you need to implement alternatives or conditional checks to ensure your app works on devices without the feature.

2. Verify Feature Declarations

Double-check that your uses-feature tags correctly specify the features you need. Use the Android documentation to verify the accurate feature names and values.

Ensure that the declared features are indeed the ones your app needs to function correctly. If your app does not need the feature, you should remove it.

3. Check Google Play Store Policies

Consult Google Play Store policies to see if there are any specific requirements related to the features in question.

• Camera API Requirements: Google Play may have requirements for camera-related features, even if your app does not actively use the camera.
• Location Services Requirements: Apps that utilize location services may need to support certain features, even if they’re marked as optional.

4. Test on Different Devices

Test your app on devices with and without the features in question. This will help you identify any issues related to your app’s functionality on devices lacking the features.

5. Request Feature Removal

If you’ve reviewed your code, checked feature declarations, and confirmed your app doesn’t require the feature, you can consider contacting Google Play Support to request the feature’s removal from your app’s requirements.

Table: Common Feature Issues

Conclusion

While setting android:required="false" in your uses-feature tags aims to make your app more flexible, Google Play’s compatibility checks can be strict. Understanding the factors influencing compatibility and applying the troubleshooting steps outlined above can help you address the issue and make your app accessible to a wider range of devices.