Thank you for your response. Regarding your question, “Where did you get that note Paid plan offer latest SDK?”, I would like to clarify my point. My concern is not that the premium plan explicitly guarantees immediate SDK updates, but rather how the platform’s architectural limits affect active subscribers during mandatory Google Play transitions.
As you know, in the Kodular builder, users cannot manually select or change the Target SDK Level; the system forces a predefined SDK. Google Play has set a strict deadline of August 31st for the new Target SDK requirement.
My current premium subscription expires on August 24th. Because Kodular has not yet provided a clear timeline or release date for the SDK update, I am put in a position where I will be forced to purchase another month of subscription just to export my updated AAB/APK file when the update finally arrives. It is unfair that I have to pay an extra fee due to a delay that is entirely out of my control.
I am requesting a fair resolution to this problem. At the very least, on the day the new SDK is released, Kodular should allow users to export their AAB/APK files for free (without any file size limits), just as it was done last year. This would be a reasonable and customer-friendly solution for users whose subscriptions expire while waiting for a platform-side update.
I look forward to your understanding and a positive resolution.
Google Play uses a two-tier timeline system for its Target API Level Policy:
1-Year Rule for Submissions: New apps and app updates must target an API level within 1 year of the latest major Android release (e.g., Target SDK 36 for phone app submissions starting August 31).
2-Year Rule for Visibility (The “App Floor”): Existing apps on Google Play that are not updated only need to target an API level within 2 years of the latest Android release to stay discoverable.
If your app currently targets SDK 35 (Android 15), you do not need to update it immediately to SDK 36 to keep it visible. It will remain visible to new users on newer Android versions for another year. It won’t lose discoverability until the API 37 policy cycle begins the following year.
I need to build an AAB file targeting Android API level 36, as required by Google Play Store. How can I set the target SDK version to API 36 in Kodular? If API 36 is not currently supported, when will the Kodular update for Android API 36 (Target SDK 36) be released?
Please read the previous answers in this rhread. There is no need to rush. You have 1 year after the deadline of August 31 to publish a version targeting sdk 36.
Thank you for the clarification. I understand that these are only warnings and that Kodular needs to properly implement the required behavioral changes for Target SDK 36.
However, I urgently need Target SDK 36 support because of Google Play requirements. Could you please let me know when Kodular is expected to support SDK 36? Even an approximate date would be very helpful.
Read the Taifun reply