Warning in Google Play Console

Oct 13, 2025 by sorusgentrification.com 122 views

Introduction

As Android continues to evolve, it's essential for developers to stay up-to-date with the latest requirements and best practices. One such requirement is the removal of resizability and orientation restrictions for large-screen devices, such as foldables and tablets. Starting from Android 16, the operating system ignores these restrictions for devices with larger screens. However, the Qonversion SDK includes a restriction in AndroidManifest.xml that causes a warning in the Google Play Console. In this article, we'll explore the issue, its implications, and the necessary steps to resolve it.

Understanding the Issue

The Qonversion SDK includes the following restriction in AndroidManifest.xml:

<activity 
    android:name="com.qonversion.android.sdk.automations.mvp.ScreenActivity"
    android:screenOrientation="PORTRAIT" />

This restriction causes a warning in the Google Play Console:

"Remove resizability and orientation restrictions in your app to support large screen devices."

The warning is a result of the new Android requirements, which will enforce resizable activities on large-screen devices starting from Android 16. This means that apps with orientation restrictions will not be compatible with foldables and tablets.

Why is this a Problem?

The restriction in AndroidManifest.xml is a problem for several reasons:

Incompatibility with large-screen devices: As mentioned earlier, Android 16 will enforce resizable activities on large-screen devices. This means that apps with orientation restrictions will not be compatible with foldables and tablets.
Warning in Google Play Console: The warning in the Google Play Console is a sign that the app is not compliant with the latest Android requirements. This can lead to issues with app distribution and user experience.
Impact on user experience: The restriction can also impact the user experience, as users may not be able to use the app in the orientation they prefer.

Steps to Reproduce the Issue

To reproduce the issue, follow these steps:

Integrate Qonversion SDK in an Android app: Integrate the Qonversion SDK in an Android app.
Upload the app to Google Play Console: Upload the app to the Google Play Console.
Google Play Console warns about resizability and orientation restrictions: The Google Play Console will warn about resizability and orientation restrictions.

Expected Behavior

The expected behavior is that the ScreenActivity should support all screen orientations or allow developers to override this setting. This will ensure that the app is compatible with large-screen devices and does not cause any issues with user experience.

Additional Context

Android 16 will enforce resizable activities on large-screen devices: Android 16 will enforce resizable activities on large-screen devices, which means that apps with orientation restrictions will not be compatible.
Removing orientation restrictions will help improve compatibility with foldables and tablets: Removing orientation restrictions will help improve compatibility with foldables and tablets, which is essential for a seamless user experience.

Resolving the Issue

To resolve the issue, you can either remove the android:screenOrientation="PORTRAIT" restriction from ScreenActivity in the SDK or make it configurable, so developers can override it in their apps. Here are the steps to resolve the issue:

Option 1: Remove the Restriction

To remove the restriction, you can simply remove the android:screenOrientation="PORTRAIT" line from the AndroidManifest.xml file:

<activity 
    android:name="com.qonversion.android.sdk.automations.mvp.ScreenActivity" />

Option 2: Make it Configurable

Alternatively, you can make the restriction configurable, so developers can override it in their apps. To do this, you can add a new attribute to the ScreenActivity in the AndroidManifest.xml file:

<activity 
    android:name="com.qonversion.android.sdk.automations.mvp.ScreenActivity"
    android:screenOrientation="@string/screen_orientation" />

Then, you can add a new string resource to the strings.xml file:

<string name="screen_orientation">portrait</string>

Developers can then override the screen_orientation string resource in their app's strings.xml file to change the screen orientation.

Conclusion

In conclusion, the restriction in AndroidManifest.xml is a problem that needs to be addressed to ensure compatibility with large-screen devices and a seamless user experience. By removing the restriction or making it configurable, developers can resolve the issue and ensure that their apps are compliant with the latest Android requirements.

Recommendations

Based on the analysis, here are some recommendations:

Remove the restriction: Remove the android:screenOrientation="PORTRAIT" restriction from ScreenActivity in the SDK.
Make it configurable: Make the restriction configurable, so developers can override it in their apps.
Update the documentation: Update the documentation to reflect the changes and provide guidance to developers on how to override the restriction.

Introduction

In our previous article, we discussed the issue of the android:screenOrientation="PORTRAIT" restriction in the Qonversion SDK and its implications for large-screen devices. We also provided steps to resolve the issue by removing the restriction or making it configurable. In this article, we'll answer some frequently asked questions (FAQs) related to this topic.

Q: Why is the `android:screenOrientation="PORTRAIT"` restriction a problem?

A: The android:screenOrientation="PORTRAIT" restriction is a problem because it causes a warning in the Google Play Console, which indicates that the app is not compliant with the latest Android requirements. This can lead to issues with app distribution and user experience.

Q: What are the implications of not removing the restriction?

A: If the restriction is not removed, the app will not be compatible with large-screen devices, such as foldables and tablets. This can lead to a poor user experience and may result in negative reviews.

Q: How can I remove the restriction?

A: To remove the restriction, you can simply remove the android:screenOrientation="PORTRAIT" line from the AndroidManifest.xml file. Alternatively, you can make the restriction configurable, so developers can override it in their apps.

Q: What are the benefits of making the restriction configurable?

A: Making the restriction configurable allows developers to override the restriction in their apps, which provides more flexibility and control over the app's behavior. This can be particularly useful for apps that require specific screen orientations.

Q: How can I make the restriction configurable?

A: To make the restriction configurable, you can add a new attribute to the ScreenActivity in the AndroidManifest.xml file, such as android:screenOrientation="@string/screen_orientation". Then, you can add a new string resource to the strings.xml file, such as <string name="screen_orientation">portrait</string>. Developers can then override the screen_orientation string resource in their app's strings.xml file to change the screen orientation.

Q: What are the best practices for handling screen orientation?

A: The best practices for handling screen orientation include:

Removing unnecessary restrictions: Remove any unnecessary restrictions on screen orientation to ensure that the app is compatible with large-screen devices.
Making the restriction configurable: Make the restriction configurable, so developers can override it in their apps.
Providing guidance to developers: Provide guidance to developers on how to override the restriction and handle screen orientation in their apps.

Q: What are the next steps after removing the restriction?

A: After removing the restriction, you should:

Test the app: Test the app to ensure that it is working as expected and is compatible with large-screen devices.
Update the documentation: Update the documentation to reflect the changes and provide guidance to developers on how to override the restriction.
Submit the app for review: Submit the app for review to ensure that it meets the latest Android requirements.

Conclusion

In conclusion, removing the android:screenOrientation="PORTRAIT" restriction from ScreenActivity is an essential step in ensuring that apps are compatible with large-screen devices and provide a seamless user experience. By following the steps outlined in this article, developers can resolve the issue and ensure that their apps are compliant with the latest Android requirements.

Recommendations

Based on the analysis, here are some recommendations:

Remove the restriction: Remove the android:screenOrientation="PORTRAIT" restriction from ScreenActivity in the SDK.
Make it configurable: Make the restriction configurable, so developers can override it in their apps.
Update the documentation: Update the documentation to reflect the changes and provide guidance to developers on how to override the restriction.

By following these recommendations, developers can ensure that their apps are compatible with large-screen devices and provide a seamless user experience.