Developer Alert: .NET 8 Can’t Target API 35 — Google Play Deadline Approaches


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)
Why not just patch it?
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:

  1. Install .NET 9 STS SDK from dotnet.microsoft.com
  2. Update your project’s .csproj file:
    <TargetFramework>net9.0-android</TargetFramework>
  3. 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)



⚠️ 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

πŸ’¬ 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

Popular posts from this blog

Push Notifications in .NET MAUI: A Comprehensive Guide

Push Notification using Firebase in xamarin form (Android and IOS)

School UI Design using xamarin form