Upgrading to SDK 35: What, Why, and How — A Friendly Guide for React Native Developers

SDK 35 Upgrade

Recently, Google made a big announcement: All Play Store apps must now target SDK 35—or risk being removed from production listings. This isn’t one of those “maybe later” things. If you don’t comply, your app stops getting updates, and new users won’t be able to install it.

I just went through this migration myself, upgrading a React Native app from 0.70.6 with Gradle 7.5.1 and AGP 7.2.2. Turns out, it’s not as simple as changing targetSdkVersion from 34 to 35. This post will share what I learned—so you can skip some headaches.

1. Why You Need to Upgrade Target SDK

  • Play Store policy: Without SDK 35, your app can’t be updated or installed.
  • Security: Newer SDKs fix vulnerabilities and enforce better privacy practices.
  • Performance & UX: Latest SDKs bring optimizations and keep your UI consistent with new devices.
  • Compliance: Google regularly bumps requirements to modernize the ecosystem.

2. Considerations & Challenges

  • Version interconnection: React Native, Gradle, AGP, and Java versions must be compatible. Upgrading one often forces upgrades in others.
  • Edge-to-edge enforcement: SDK 35 runs content behind system bars by default. Without adjustments, your UI can look “squished” under the status or navigation bars.
  • Dependency breakage: Third-party libraries (gesture handler, navigation, Firebase, etc.) may need updates—or code changes—to work after the upgrade.
  • Testing load: Visuals, navigation, and permissions might behave differently. You’ll need thorough QA.

3. Migration Guide – Step by Step

Step 1: Check Your Current Setup

Note down your React Native, Gradle, and AGP versions. In my case: RN 0.70.6, Gradle 7.5.1, AGP 7.2.2.

Step 2: Find Compatibility Requirements

Check what minimum RN version supports SDK 35. Then match compatible Gradle and AGP versions. Official docs will save you from guesswork:
React Native Docs
AGP Release Notes

Step 3: Use React Native Upgrade Helper

Visit Upgrade Helper, choose your current and target RN versions, and follow the diff it generates. Apply changes exactly—it’s your best upgrade roadmap.

Step 4: Update Dependencies

After upgrading RN core, fix other libraries:

  • react-native-gesture-handler
  • react-native-reanimated
  • @react-navigation/*
  • Any project-specific libs like Firebase, analytics, device APIs
Read changelogs to catch breaking changes early.

Step 5: Upgrade Gradle & AGP

Don’t manually edit build.gradle. Use Android Studio’s Upgrade Assistant to avoid version mismatch issues.
Recommended for SDK 35:

  • Android Studio: Koala (2024.1.2) or newer
  • Gradle: 8.0+
  • AGP: 8.6.1+
Also, download Android 15 (API 35) in SDK Manager.

Step 6: Change Target SDK

In android/app/build.gradle, set:
targetSdkVersion 35
compileSdkVersion 35
Then rebuild and fix errors as they appear.

Step 7: Handle Broken Builds

Errors are normal—resolve them one at a time. For Firebase users: check for compatibility updates before assuming the problem is in your code.

Step 8: Edge-to-Edge UI Adjustments

With SDK 35, content renders behind system bars by default. Use react-native-safe-area-context and test on gesture-nav devices to ensure headers and buttons aren’t hidden.

4. Bonus: Upcoming 16KB Alignment Rule

From August 2025, Play Store updates must have 16KB APK/Bundle alignment. Update your build tools or CI/CD scripts to meet this—don’t wait until submission day.

More info: Google Developer Blog

Wrapping Up

Upgrading to SDK 35 isn’t just about compliance—it’s about keeping your app secure, modern, and ready for the future. Do it step-by-step, follow the right resources, and you’ll get through without losing your weekend.

Have your own upgrade story? Share it in the comments—I’d love to hear how it went for you.

Home
Location: India

Comments

Post a Comment

Reader's Choice

No better way to understand GIt flow than this...

Image
Git Good with Guns: A Humorous, Hands-On Approach to Learning Version Control When it comes to Git, many developers feel like they're entering a battlefield. So, why not embrace that feeling and compare Git commands to handling a gun? Don't worry—no actual guns involved, just a bit of tech fun. Let’s break down some key Git commands as if you were preparing for a mission.  These are the basic commands you'll find yourself using day in and day out, so let’s make sure you’re ready for action! 1. git add . Think of this command as loading bullets into your magazine . When you run git add . , you're adding all your changes (the bullets) to the staging area (the magazine). You're getting everything ready for the next step. Make sure your magazine is fully loaded with all the necessary changes! 2. git commit -m '<message>' Now that y...
Read more

Vercel vs Render | Choosing the Best Free Hosting Platform for Your Projects

Image
  When it comes to FREE HOSTING, both Vercel and Render offer enticing options, each with its own set of strengths and trade-offs. Vercel and Render both offer free cloud hosting for your projects, providing a great opportunity to practice and learn with real-world tools. While these free plans come with limited resources and features, they're perfect for getting started or testing smaller projects. However, if you're considering using these platforms for production, it's worth noting that a dedicated plan would be more suitable. But let's set aside the paid plans for now and focus on what you can do with the free versions. Many of you may have noticed the constraints that come with free hosting, such as limited resources and restricted monthly uptime. Here, I'll give you a brief overview of what the free plans actually offer, along wi...
Read more

Implementing OTP Auto-Retrieval in React Native Using react-native-otp-verify

Image
OTP Auto-Retrieval in React Native Using react-native-otp-verify One-Time Passwords (OTPs) are a common method for verifying user identities in mobile applications. Manually entering OTPs can be cumbersome for users. Android's SMS Retriever API enables automatic OTP retrieval, enhancing both user experience and security. Understanding OTP Auto-Retrieval The SMS Retriever API enables your app to automatically retrieve verification codes without requiring SMS read permissions. The general flow is as follows: User initiates OTP verification. Your app starts the SMS Retriever API listener. The server sends an SMS with OTP and app hash. Google Play services detects and delivers the SMS to your app. Importance of the App Hash The app hash is an 11-character unique identifier that links the SMS to ...
Read more