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

Singha Nissaisuk 15 Reputation points
2026-09-17T07:16:18.2366667+00:00

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

Developer technologies | .NET | .NET Multi-platform App UI
0 comments

1 answer

Sort by: Oldest
Most helpful Newest Oldest
  1. Nguyen Dam (WICLOUD CORPORATION) 685 Reputation points Microsoft External Staff Moderator
    2026-09-17T09:27:36.3+00:00

    Thank you for your question, @Singha Nissaisuk

    For the DEX obfuscation warning, enable R8 for the Release build in your project's .csproj file:

    <PropertyGroup Condition="'$(Configuration)' == 'Release'">

    <AndroidLinkTool>r8</AndroidLinkTool>

    <AndroidR8ObfuscationMode>private-members</AndroidR8ObfuscationMode>

    <AndroidCreateProguardMappingFile>true</AndroidCreateProguardMappingFile>

</PropertyGroup>

    This enables code obfuscation but may ultimately fail to satisfy Google's new policy requirements, due to a known issue here.

    For the edge-to-edge warning, use SafeAreaEdges="Container" on the ContentPage or affected root layout of your MAUI page, for example:

    <ContentPage ... 
	SafeAreaEdges="Container">
    ...
</ContentPage>

    Then test the pages on an API 35 device or emulator and verify that content is not covered by the status bar, navigation bar, or display cutout.

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

    Was this answer helpful?

    1 person found this answer helpful.

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.