How should .NET MAUI handle Google’s new policy requirements?

Question

How should .NET MAUI handle Google’s new policy requirements?

Singha Nissaisuk 15

Hi, I received new warnings from Google Play Console about my .NET MAUI Android app. Google requires higher obfuscation percentage and proper edge‑to‑edge rendering for Android 15 (SDK 35).

1.Our app optimization is below the required threshold. Please improve the percentage in the following category:

Code Obfuscation (1%) Any category with a percentage lower than 25% may affect your app’s visibility and publishing eligibility on Google Play. https://developer.android.com/topic/performance/vitals/code-optimization

Please optimize your app within the required timeframe to avoid potential issues.

2.Some users may not see edge‑to‑edge rendering. Starting from Android 15, apps targeting SDK 35 will use edge‑to‑edge rendering by default. Apps targeting SDK 35 should properly handle window insets to ensure correct display on Android 15 and above. Please review this issue and take time to test edge‑to‑edge rendering and apply any necessary updates. Alternatively, call enableEdgeToEdge() for Kotlin or EdgeToEdge.enable() for Java to maintain backward compatibility. https://developer.android.com/about/versions/15/behavior-changes-15#edge-to-edge

0 comments

1 answer

Your answer

Answer 1

Thank you for your question, @Singha Nissaisuk

Based on the information provided, I suggest the following approaches to address these two Google Play warnings in a .NET MAUI Android application.

1. Code obfuscation

The reported percentage applies to the DEX code included in the Android App Bundle generated for the .NET MAUI application, rather than directly to its managed C# code. You may consider the following:

Ensure that the application is built and published in Release mode with the intended .NET MAUI Android optimization settings.
Check whether the affected DEX code comes from an Android dependency and review its optimization or keep-rule guidance.
If needed, inspect the generated .aab with Android tooling to identify unobfuscated DEX packages.
Test the Release build after any changes to ensure that the application and its dependencies continue to work correctly.

For details about how the percentage is calculated or how it may affect Google Play publishing eligibility, please refer to the relevant Google Play documentation or support channel.

2. Edge-to-edge rendering

For edge-to-edge rendering, verify that content remains correctly positioned on Android 15 with both gesture and three-button navigation. You may consider the following:

Run the Release build on an Android 15/API 35 device or emulator.
Open each page containing headers, bottom navigation, floating buttons, or controls near the screen edges, and check for overlap with the status bar, navigation bar, or display cutout.
Repeat the checks with both gesture and three-button navigation enabled in the device or emulator settings.
Where overlap occurs, adjust the affected .NET MAUI layout to account for the relevant system-bar insets rather than relying on fixed padding or margins.
Retest the affected pages after each layout change to confirm that content remains visible and controls remain accessible.
Use enableEdgeToEdge() only when equivalent edge-to-edge behavior is required on earlier Android versions; inset handling is still required where overlap occurs.

No additional changes are necessary if the existing layouts already handle the relevant insets correctly.

The suggestions above are intended as general guidance. If you are experiencing a specific publishing or layout issue, please feel free to provide the complete Play Console warning, a screenshot or minimal example, your development environment, the .NET MAUI and Android versions, relevant dependencies, and project configuration. I would be happy to provide more targeted guidance based on the additional details.

If you found my response helpful or informative, I would greatly appreciate it if you could follow this guide for your confirmation. Thank you.