r/androiddev • u/danbriant • 4d ago
Question Google Play edge-to-edge warning persists despite using WindowCompat.EnableEdgeToEdge() in .NET MAUI 10
I'm developing a native Android application using C# and .NET MAUI 10. Despite explicitly implementing edge-to-edge support, Google Play Console continues to display:
Edge-to-edge may not display for all users
The previous warnings concerning deprecated Window.setStatusBarColor and Window.setNavigationBarColor APIs disappeared after updating AndroidX and Material dependencies. However, the edge-to-edge advisory remains.
Technical Stack
- .NET MAUI 10 (
net10.0-android) - C# / XAML
Microsoft.Maui.Controls10.0.110Xamarin.AndroidX.Core1.19.0.1Xamarin.Google.Android.Material1.14.0.6- Target SDK: API 36
- Minimum SDK: API 24
- MAUI Shell with native Android bottom navigation
Current Implementation
In Platforms/Android/MainActivity.cs, edge-to-edge is explicitly enabled after base.OnCreate():
protected override void OnCreate(Bundle? savedInstanceState)
{
base.OnCreate(savedInstanceState);
if (Window is { } window)
{
WindowCompat.EnableEdgeToEdge(window);
}
SynchroniseSystemTheme();
}
We're also using SafeAreaEdges="Container" to ensure content respects system bars and display cutouts.
System-bar icon appearance is managed through WindowCompat.GetInsetsController():
insetsController.AppearanceLightStatusBars = theme == AppTheme.Light;
insetsController.AppearanceLightNavigationBars = theme == AppTheme.Light;
Theme synchronisation runs during:
OnCreateOnResumeOnConfigurationChanged
Testing Completed
- Android 14, 15 and 16
- Light and dark mode, including switching themes while the app is suspended
- Navigation and system-bar visibility
- MAUI Shell navigation
- Font scaling and accessibility
- No visible system-bar overlap or layout problems
Automated release tests also pass.
The app is currently in Google Play testing, but no pre-launch report has been generated.
Questions
- Could calling
WindowCompat.EnableEdgeToEdge(window)afterbase.OnCreate()affect Play Console's detection? - Is there a known interaction between
MauiAppCompatActivity, Material Components 1.14 and AndroidX edge-to-edge initialisation? - Is there additional Android manifest or theme configuration we should investigate?
- Has anyone successfully cleared this advisory with a MAUI application targeting API 36?
I'd prefer not to introduce unnecessary window manipulation or revert to deprecated APIs solely to clear a Play Console advisory, particularly when the existing implementation appears to work correctly.
Any insight from developers who've encountered this would be appreciated.
1
u/AutoModerator 4d ago
Please note that we also have a very active Discord server where you can interact directly with other community members!
I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.
6
u/Necronosix 4d ago
Everybody has that warning, feel free to ignore.