I will update target sdk to API 36 for react native and expo android apps
Software Engineer
About this Gig
Seeing "App must target Android 16 (API level 36) or higher" in Play Console? I update React Native and Expo apps to target SDK 36 so you can publish updates again.
Many SDK update services focus on native or Flutter apps. React Native is different: reaching API 36 often needs a React Native upgrade, 16KB page size support and native library updates. That's my specialty, with 4 years of hands-on React Native work.
What I do:
- Update targetSdk and compileSdk to 36, plus Gradle and AGP
- React Native upgrade or Expo SDK upgrade when needed
- Fix "Your app does not support 16 KB memory page sizes"
- Fix Android 16 edge-to-edge layout issues
- Update or replace outdated native libraries
- Signed AAB build, plus Google Play upload in Standard and Premium
Which package fits you?
Basic: RN 0.77+ or Expo SDK 53+
Standard: RN 0.72-0.76 or Expo SDK 50-52
Premium: older or heavily customized apps
You get full source code and a change log of every update.
Not included: new features, backend work, Play policy appeals, iOS changes (available as an extra).
Not sure which package fits? Message me your app's version and I'll recommend the right one.
My Portfolio
FAQ
Which package should I choose for my app?
Check the "react-native" or "expo" version in your package.json. RN 0.77+ or Expo SDK 53+: Basic. RN 0.72-0.76 or Expo SDK 50-52: Standard. Older apps or custom native code: Premium. Not sure? Message me before ordering.
Why can't you just change the target SDK number?
On older React Native versions, raising targetSdk alone can build but crash or break the UI. Android 16 forces edge-to-edge layouts, and Google Play requires 16KB page size support. React Native 0.77+ handles 16KB, and 0.81+ targets API 36 by default.
Can you update my Expo app to target API 36?
Yes. I work with both Expo managed and bare React Native apps. If your Expo SDK is outdated, I upgrade it (SDK 54+ targets API 36) and fix any broken libraries. Expo EAS build setup is available as an extra.
Can you fix the 16 KB memory page sizes error?
Yes. I upgrade React Native and any native libraries with old .so files, then check the final AAB for 16KB alignment before delivery, so Play Console accepts your update. The fix is included in Standard and Premium.
Will my app be removed if I miss the deadline?
No, your published app stays live. But you can't release updates until it targets API 36, and apps below API 35 stop showing to new users on newer Android devices. Updating early protects your installs.
What do you need from me to start?
Source code access (GitHub, GitLab or Bitbucket), your RN or Expo version, and a screenshot of the Play Console warning. For a signed build, your upload keystore and passwords. I work on a separate branch and never share your code.
I lost my keystore. Can you still update my app?
Usually yes, if your app uses Play App Signing. I create a new upload key and guide you through Google's upload key reset in Play Console. Google must approve the request from your account, which can take a few days.
Can you upload the update to Google Play for me?
Yes. Standard and Premium include uploading your signed AAB and releasing it. For Basic, add the Google Play upload extra. You just invite me as a user in Play Console with release access, no password sharing needed.
Will my iOS app still work after the upgrade?
This gig focuses on Android. A React Native upgrade also touches iOS files, so if you need iOS to build cleanly too, add the iOS build check extra and I'll make sure it compiles and runs.
Do you offer support after delivery?
Yes. If anything breaks because of my changes, I fix it free for 3 days (Basic), 7 days (Standard) or 14 days (Premium) after delivery. New features and Play review delays are not covered.

