I have commercial projects that no longer run on Android 14.
What do I tell my clients? Can they call Kodular?
@KodularCreator could fix the native component incompatibilities one by one, and release constant, incremental improvements instead of crashing every project in the world to release a single, gigantic, problematic update?
I pay for premium to have a better service, but I have the feeling that after it became paid, everything got worse. It seems like someone took the money and went to the beach.
Hi everyone, I personally recommend the method Jewel posted to solve the problem. I personally already did it and the update was published in the Play Store, no problem.
It looks like you forgot to read a few answers in this thread… and as you tagged me, I will give you again personally my advice, whis is:
Be wise and ask Google for an extension until Nov 1st and do your updates and whatever you have to do now while still using target sdk 33.
As soon as we get the sdk 34 release you have to expect new bugs anyway… and it will be real panic then when something does not work… then you are really out of other options…
Later (next year?) when some bugs will get fixed and others most probably not as always, then you might be able to finally use the sdk 34 release…
@Taifun the problem is not the publication, that has been overcome, I have already done that myself.
The problem is the native components, such as Image Picker and others, which simply stopped working in Android 14.
A native component that does not work is a disregard. Even worse if you are being pay for it.
And this could be solved incrementally, one by one, with constant daily updates.
To get around this I have to swaped native components for third-party components, change the project and test everything again.
What do you suggest in this case?
Did you target sdk 33?
What exactly does not work with the image picker? Did you search the community?
Start a new thread for this
Also what exactly are “others”?
Everything is wrong here, if you implement updated extensions for api34, when compiling the kodular libraries they become obsolete and generate new problems. I already went through that entire process and my best option was to migrate my projects
i’m very regretful to say this, i can’t wait for kodular update anymore, it’s very frustrating being a user of kodular, please anyone let me if there any other platform with api level 34 where i can transfer my kodular projects… i would be very thankful
It’s very simple, just edit the APK target to 34 with APK Editor, and compile the AAB with the APK to AAB Converter mobile app and your Keystore downloaded from Kodular. There is a tutorial in the community.
The ImagePicker component does not work.
Make a project and click to see that nothing happens.
I have also read about problems in the Download and Network components, reported by Kodular moderators.
New apps and app updates must target Android 14 (API level 34) to be submitted to Google Play (except for Wear OS and Android TV apps, which must target Android 13 or higher).
Existing apps must target Android 13 (API level 33) or higher to remain available to new users on devices running Android OS higher than your app’s target API level. Apps that target Android 12 (API level 31) or lower ( Android 10 or lower for Wear OS and Android 11 or lower for TV OS), will only be available on devices running Android OS that are the same or lower than your apps’ target API level.
You will be able to request an extension to November 1, 2024 if you need more time to update your app. You’ll be able to access your app’s extension forms in Play Console later this year.
