Your app uses deprecated APIs or parameters for edge-to-edge.

[gmck]

Android framework version

net9.0-android

Affected platform version

VS2022 17.14.7 Prev 1.0

Description

Every time I upload a new version of my app to Google Play Console, it states Your app uses deprecated APIs or parameters for edge-to-edge. The app has been accepted and published; therefore, for the moment, it is okay. However, I believe that all Android 15 apps must be edge-to-edge compliant by September 1st.

It states that I’m using SetStatusBarColor and SetNavigationBarColor. Both those methods were removed from my app when I first went edge-to-edge months ago. Neither method appears in my app when I search for either of them using VS’s Find in File (Solution).

EdgeToEdge.Enable(this) is the very first line of the OnCreate of my BaseActivity.cs

Google Play Console states that it starts in the following
• com.google.android.material.internal.EdgeToEdgeUtils.applyEdgeToEdge
• com.google.android.material.bottomsheet.BottomSheetDialog.onCreate

https://play.google.com/console/u/0/developers/4890293474557724868/app/4972948681272339281/tracks/production#:~:text=com.google.android,internal.EdgeToEdgeUtils.applyEdgeToEdge
https://play.google.com/console/u/0/developers/4890293474557724868/app/4972948681272339281/tracks/production#:~:text=com.google.android.material.bottomsheet.BottomSheetDialog.onCreate
If you check those two files, you will find references to both methods, and I suppose that is how they end up in my app.

The EdgeToEdge file name refers to internal, which I assume is not something we can change. I also thought that upgrading all the NuGet packages of my project would eventually fix the problem. However, the latest build is using the packages dated July 15th.

The app now looks to be edge-to-edge compliant. For example, RecyclerViews are visible through the bottom Navigation Bar. When you rotate the device, the padding of the views on the left and right is correct. BottomSheet dialogs display scrolling content through the bottom Navigation Bar. Both light and dark themes respect edge-to-edge.

I’ve asked Google Play Console support how they determine that an app is not compliant, but they were not at all helpful.

Would you guys have any knowledge of what can be done to make the app compliant?

Steps to Reproduce

N/A

Did you find any workaround?

No

Relevant log output

N/A

[jonathanpeppers]

You have to do what Google is asking, did you opt your app into supporting "edge to edge"?

• https://developer.android.com/develop/ui/views/layout/edge-to-edge

I'm not sure what we need to do here, except maybe do this for the .NET 10 project templates?

If you have the latest .NET 9 Android workload, you can also target API 36 with TargetFramework=net9.0-android36.

[gmck]

@jonathanpeppers

Thanks for your reply.

I’m familiar with Android’s documentation. I started with Edge-To-Edge back in November last year. The Google documentation and many community posts (including those referenced in your previous reply (See Additional Resources - Blogs) are outdated or misleading, often recommending approaches (e.g., SetDecorFitsSystemWindows – which will then also appear in the Google Play Console deprecated list) that do not address the root issue when deprecated calls are made internally by libraries.
In my case, the warnings originate from internal calls in Google’s Material library, notably EdgeToEdgeUtils.applyEdgeToEdge and BottomSheetDialog.onCreate.

The latest Xamarin binding (1.12.0.4) lags behind the Material library, which itself has not resolved the deprecated API usage as of 1.14.0-alpha, see material-components/material-components-android#4507

I’m surprised it hasn’t been mentioned here previously, as anyone publishing a net9.0-android35 app on Google Play would have received various warnings related to the above. Maui developers should also be aware of the September 1st deadline; however, they were initially advised to opt out of Edge-To-Edge using the following.

<application ... >
    <meta-data
        android:name="android.edgeToEdgeOptOut"
        android:value="true" />
</application>

If Google enforces a hard block (Sept 1st) on deprecated API usage, any app using the current Material library (and thus Xamarin.Google.Android.Material) will be rejected, regardless of the developer’s own code.

There is currently no workaround for Xamarin developers except to wait for Google to update the Material library and for Xamarin to update the bindings.

The only way to verify the issue is to publish to Google Play and receive the warning, making it difficult to test or demonstrate compliance proactively.

Previously, when pre-launch reports were available on Google Play Console, those types of warnings would appear there. Pre-launch reports now seem to be a thing of the past. The last one I received was for build 298, Feb 5th. My latest build is 330.

Request:

Could you please escalate this issue with Google and prioritise updating the Xamarin bindings as soon as a fix is available upstream?

Consider providing guidance or a roadmap for developers who face this compliance risk, including any potential mitigations or opt-out strategies.

If possible, collaborate with Google to ensure that the Material library is updated before enforcement begins, and communicate any progress to the community.

For reference, I have a public repo demonstrating edge-to-edge implementation in .NET 9:
https://github.com/gmck/NavigationGraph9Net9. I have now updated the NuGet packages to the July 15, 2025 versions.

However, since the warning only appears after publishing to Google Play, local testing is insufficient.

PS I tried updating my published app to Android 36. Build and deployment were successful. My app ran as normal. However, the build generated 1391 errors, five warnings and 74 messages. Could you please advise what you’d like back regarding those errors, etc. For now, I’ve gone back to 35.

[jonathanpeppers]

We don't have a way to contact Google any different than you would. We have to either file issues on GitHub or via their issue tracker.

What we could help with:

• A change needs to be made to the default project templates.
• There is some API missing that makes you unable to comply.
• There is a new Material package ready, and you need a matching C# NuGet package.
• If you want to file an issue about the net9.0-android36 warnings we could look into that separately.

Maybe you can share screenshots or text from Google Play with what you are seeing?

Do you get the same messages from a .NET 10 MAUI project template?

[gmck]

@jonathanpeppers

We don't have a way to contact Google any different than you would. We have to either file issues on GitHub or via their issue tracker.

Ok, I didn’t realise that.

I apologise for not sharing a screenshot. I wrongly assumed that you would be aware of the problem, as I’ve been getting these warnings from Google Play Console since I first released my Android 15 app to production. Initially, there were many more instances of non-compliance, but they have gradually reduced to just SetStatusBarColor and SetNavigationBarColor.

If you follow the link I supplied, you’ll see it was first reported on January 3rd and was assigned to Hunterstich. May 3rd, he claims it was fixed in 1.14.0-alpha01. Then, on Jun 3rd, it was reverted, and he reopened the issue on June 12th. From there, nothing much has happened, except that this thread was added to it overnight. I’ve got no idea how that happened. I suppose they scan GitHub regularly.

Do you get the same messages from a .NET 10 MAUI project template?

I don’t use Maui, so I can’t comment. However, I doubt that anyone would publish a standard template. You must publish an app to Production before you will receive these warnings. All uploads to closed or internal testing are now automatically accepted after a brief check and are immediately available.

Attaching the screenshot of what I received. The material-components thread has many more examples. I can’t provide previous examples, because I can only view my latest production warnings.

If you want to file an issue about the net9.0-android36 warnings we could look into that separately.

I’m not sure what I did last night, but when I tried again this morning with Android 36, it built without any warnings or errors. The app runs normally on any of my devices, including one using the most recent beta of Android 16 (BP2A.250705.008). Currently, I’m not considering moving to Android 16, as I first need to upgrade libraries like BillingClient due to another Google Play Console deadline. Once that's done, I’ll move on to 16.