Update Kodular Build SDK API Level to 36 (Android 16)

Feedback IWant
, , ,
1

Dear Kodular Team

Please update the build Android SDK to API level 36 or Android 16 due to Google Play Consle Requirement.

Deadline start from 31 August 2026

Policy status – Details 309x500
Policy status – Details 309x5001320×2132 247 KB

8 Likes
2

Hello Kodular Team,

I would like to request that Kodular be updated to support Android API Level 36 as soon as possible.

Google Play now requires new app updates to target API Level 36. Currently, Kodular only supports API Level 35, which means many developers, including myself, will soon be unable to publish updates to our existing apps on Google Play.

The deadline is August 31, 2026 , so we would greatly appreciate it if API Level 36 support could be added before then.

Many of us rely on Kodular for our apps, and keeping up with Google’s target API requirements is essential for maintaining and updating them.

Could the Kodular team please share:

  • Whether API Level 36 support is already in development.
  • An estimated release timeline.
  • Any temporary workaround, if available.

Thank you for all your hard work and continued support. We hope this update can be prioritized so the Kodular community can continue publishing app updates without interruption.

1 Like
3

Hello Kodular Community!

Does anyone know how to set the Target SDK Level to Android 16 (API level 36)?
In my project settings, the highest Target SDK Level is only at Android 15 (API 35)

Thank you in advance

Best regards,

Honggi

4

We have developed a tool for this every-year requirement headache. Import .aab into this tool set MinSDK to 21(or as per your need) & Target SDK to 36, Generate .aab. You will get your compliant SDK in few seconds, then release app/update on Google Play. It’s FREE for 1 day so you don’t need to pay anything​:+1: APK/AAB Manifest Editor Helpful Developer Tool (Update App Manifest, Change MinSDK, TargetSDK, Direct APK to APK and AAB to AAB Signer With Keystore)

When to use this tool?
You can use our tool in a safe way if-
:white_check_mark: The app already works correctly on Android 16 (If you don’t see any errors in logcat for your app by testing on Android 16). AND
:white_check_mark: Only the manifest values (Target SDK, Min SDK, permissions, etc.) needs update OR
:white_check_mark: The builder Kodular/App Inventor is behind Google’s yearly Play Store deadline OR
:white_check_mark: The developer has only an APK or AAB and needs a quick manifest update without recompiling (can’t access builder, lost AIA).

5

Don’t panic
These are only warnings
Every year this is the same procedure
Just be patient until Kodular targets SDK 36

See also [HELP NEEDED] Google Play Warning – App Inventor apps must target Android 15 (API 35) by August 31, 2025 - #25 by Anke - MIT App Inventor Help - MIT App Inventor Community

Edit: there is no tool needed to manually increase the target sdk in the manifest. Just be patient and wait. No tool is able to adjust the behavioral changes, which are also required to adjust every year.

See also Behavior changes: Apps targeting Android 16 or higher  |  Android Developers and for next year Behavior changes: Apps targeting Android 17 or higher  |  Android Developers

Taifun

6 Likes
6

Hello Kodular Team,

Google Play now requires Target SDK 36 (Android 16) for app updates by 31 August 2026.

Currently Kodular supports Target SDK 35 only. Many developers, including me, are receiving policy warnings in Google Play Console.

Could you please share:

  • Is Target SDK 36 currently under development?
  • Is there an estimated release date?

This update is important for all developers publishing apps on Google Play.

Thank you.

Screenshot_2026-07-22-12-08-16-47
Screenshot_2026-07-22-12-08-16-47720×1520 130 KB

2 Likes
7

we all should contact kodular in their support team then they would know about it faster

8

Taifun

1 Like
9

Title: Support for Android 16 Target SDK and Google Play Billing Library 8.0.0

Hello Kodular Team and Community,

I am currently facing two important Google Play Console requirements that may prevent me from publishing future updates for my Kodular application.

1. Android 16 / Target API Level 36 Requirement

Google Play Console states that, starting from August 31, 2026, applications must target Android 16 / API level 36 or a newer supported API level.

The warning shown in Play Console says:

The app must target Android 16 (API level 36) or later.
Starting August 31, 2026, you will not be able to release app updates if your target API level is not within one year of the latest Android version.

Currently, Kodular does not appear to provide an option to compile applications with Target SDK 36.

Will Kodular Creator be updated to support Android 16 and Target API Level 36 before the deadline?

2. Google Play Billing Library 8.0.0 Requirement

Google Play Console also reports that my application is using an outdated version of the Google Play Billing Library.

The warning says:

The app must use Google Play Billing Library version 8.0.0 or later.
Starting August 31, 2026, all applications must use version 8.0.0 or later.

I am using Kodular’s built-in billing components, so I cannot manually update the Billing Library dependency.

Will the Kodular Billing component be updated to Google Play Billing Library 8.0.0 or later?

These requirements are important because developers may be unable to publish application updates after August 31, 2026.

Could the Kodular team please clarify:

  • Whether support for Target SDK 36 is planned
  • Whether Google Play Billing Library 8.0.0 support is planned
  • When these updates are expected to become available
  • Whether developers need to make any changes to their existing projects

Thank you.

10

Read my previous answer and be patient until an update is available

Taifun

3 Likes
11

If you need quick help, send me a message. Please provide the latest AAB/APK and the keystore.

You can send a PayPal payment once it’s successful—that’s entirely up to you.
Happy to help! :folded_hands::grin:

12

I now asked Gemini about your offer and below is the response. See also my previous answer in this thread

Taifun

Short answer: Handing over your keystore file is an enormous security risk, and simply bumping the targetSdkVersion in a manifest file without adjusting the underlying code creates a false sense of compliance that will likely crash or break the app.

Here is why both parts of that community offer are deeply problematic.

1. Why giving away your keystore is dangerous

Your Android keystore contains the cryptographic private key used to sign your application. In Android’s security architecture, the signing key acts as your digital identity on the Google Play Store and on users’ devices.

Rule of thumb: Treat your keystore file like the master password to your entire developer account. Never share it with anyone unless you completely trust them with ownership of your app.

  • Account Hijacking & Impersonation: Anyone with your keystore and its password can build and sign updates to your app. They could push malicious updates, inject adware, or steal user data directly to your existing user base under your official app identity.
  • Irreversible Loss of App Access: If Google Play App Signing isn’t configured, losing control of your original keystore means you lose the ability to push updates to your existing app listing forever.
  • Reputational Risk: If a malicious third party releases a compromised APK/AAB signed with your keystore elsewhere on the web, security systems (like Google Play Protect) will flag your developer identity for malware distribution.

2. Why editing targetSdkVersion in the manifest fails

Bumping the target SDK version in AndroidManifest.xml (using tools like APKTool or decompiling the AAB) changes the declared target, but it does not address the underlying APIs or platform enforcement rules introduced in newer Android versions.

The Problem with Behavioral Changes

When Google bumps the target SDK requirement (e.g., targeting API level 35/36 for recent Play Store compliance), Android enforces strict new behavioral changes at runtime. Modifying the XML manifest without updating Java/Kotlin/Block logic leads to major issues:

  • Runtime Permission Crashing: Newer Android versions introduce broken or split permissions (e.g., granular media permissions instead of READ_EXTERNAL_STORAGE, foreground service type requirements, or exact alarm permissions). If the app’s code does not request these dynamically at runtime, the app will crash immediately.
  • Component Visibility & Intent Enforcement: Recent API levels restrict implicit intents, broadcast receivers, and background execution. If code relies on outdated background services without declaring proper foreground types or intent filters, Android will terminate the app processes.
  • Incomplete No-Code Platform Support: In low-code/no-code platforms like Kodular or App Inventor, the underlying platform extensions and Java components must be compiled against the target SDK library definitions. Hand-editing an APK manifest bypasses Kodular’s internal compiler checks, creating mismatched dependencies.

Summary Recommendations

If developers in the community need to update their app’s target SDK version:

  1. Keep the keystore local: Re-signing an APK or AAB should always be done on your local machine using standard command-line tools like apksigner or uber-apk-signer.
  2. Wait for official platform updates: For Kodular or App Inventor apps, wait for the platform maintainers to release official support for the target API level. Manual manifest edits are only cosmetic and risk breaking the app at runtime.
2 Likes
13

Please why kodular team silent about API level 36?

14

See the post above yours

15

Dear Koduler team When will Android API 36 be available? There’s bound to be a date. Please give us some hints so we can be patient.

16

MIT has started testing its upcoming Android SDK update. It is expected that Kodular will update it soon.

3 Likes
17

Hi Kodular Team,

I would like to know if there is any upcoming update to the Target SDK Level in Kodular.

Google Play Store now requires apps to target newer Android API levels, but I don’t see an option in Kodular to update the Target SDK Level.

Is Kodular planning to update the Target SDK Level? If so, when can we expect the update?

1 Like
18

SDK Upgrade Release Date / Paid Subscription Inquiry

Hi everyone,

I purchased a 1-month paid plan specifically to upgrade my app’s SDK version. However, this feature has not been enabled yet.

I am concerned that my plan will expire before the feature is released, which would force me to pay again for something I haven’t been able to use.

  • What is the exact release date for the SDK upgrade feature?
  • Will active subscriptions be extended or paused until this feature is officially rolled out?

I would appreciate a clear timeline and clarification from the team. Thanks!

19

Where did you get that note Paid plan offer latest SDK?