Developer Alert: .NET 8 Can’t Target API 35 — Google Play Deadline Approaches
Stuck at API Level 34? .NET 8 Developers Hit a Wall with Android 35 – Frustration, Fixes & Future
If you're a .NET MAUI or Xamarin developer working with .NET 8, chances are you’ve run into the dreaded wall of API Level 35. You’ve set everything up, upgraded your Android SDK, and yet your app just won’t target the latest Play Store requirement. You're not alone.
Join our exclusive WhatsApp group for Xamarin and .NET MAUI developers to connect with experts, share insights, and get help with your projects. Whether you're a beginner or an experienced developer, this group is the perfect place to enhance your skills and collaborate with the community.
Please, support my blog by clicking on our sponsors ad!
π¨ The Problem: .NET 8 Doesn't Support API Level 35
As per Google’s Play Store policy, all new apps and updates must target API level 35 by August 31, 2025. However, .NET 8 only supports Android API Level 34.
“.NET 8 is locked to net8.0-android34.0
. API Level 35 is only supported starting with .NET 9 sts version.”
— GitHub Issue #9992
π‘ Developer Frustration Is Real
Many developers feel blindsided. They expected .NET 8, being an LTS (Long Term Support) version, to cover all upcoming requirements. But now they face a decision:
- π Stay on .NET 8 and miss the Play Store deadline
- π§ Upgrade to .NET 9 STS with no LTS guarantee
- π Hack around it manually (not recommended)
Setting
AndroidTargetSdkVersion
to 35 in your project file doesn’t work because the MAUI and Xamarin workloads don’t include the necessary API 35 bindings in .NET 8.
π§ͺ Option 1: Upgrade to .NET 9 STS
Microsoft has added support for API 35 in the .NET 9 STS workloads. If you’re okay with potential instability, you can switch by:
- Install .NET 9 STS SDK from dotnet.microsoft.com
- Update your project’s
.csproj
file:<TargetFramework>net9.0-android</TargetFramework>
- Install updated Android workload:
dotnet workload install maui --skip-sign-check
✅ Result: You can now target Android 14 (API 35) and publish your app without Play Store rejection.
π Option 2: Apply for a Google Play Deadline Extension
Google allows developers to request an extension if they can’t meet the API level requirement in time. This buys time until Nov 1, 2025.
→ Apply for extension here (official Google link)
Table of Contents for .Net Maui
- What is .NET MAUI and why it’s important
- Applying the MVVM pattern for cleaner architecture
- Working with Renderers and Mappers
- Storing data locally using SQLite and Preferences
- Image Picker from gallery
- Sending push notifications using Firebase
- Publishing your app to Android and iOS stores
- π Explore More Topics
⚠️ Option 3: Manually Hack SDK Version (Advanced)
Some developers try to patch their project like this in manifest file:
<uses-sdk android:minSdkVersion="21" android:targetSdkVersion="35" />
π« Warning: This allows the app to pass the Play Store's target SDK check. However, you're still compiling against API 34, so API 35 features won't be available, and your app might experience some runtime behavior changes specific to Android 14.
π Helpful References
- GitHub: .NET Android API 35 Support
- GitHub: MAUI + API 35 Play Store Deadline
- Google Play API Level Policy
- Migrate Android Projects to .NET 9 (Microsoft Docs)
π¬ Final Thoughts
The .NET and Android ecosystem is evolving fast. For .NET 8 developers, this situation is frustrating — especially when you’ve built stable apps that now need major updates just to remain visible on the Play Store.
For now, your best path forward is:
- π Upgrade to .NET 9 STS
- π Request an extension if you need more time
- π¦ Keep track of GitHub issue updates
Stay calm, code on — and remember, even Microsoft is figuring this out. π
Comments
Post a Comment