As of today my patience was used and abused and now I’m pissed off.
I am still stuck on this error i cant even publish my app…
Hi Thunkable Community,
We understand your frustration about this, and we really appreciate your patience with us thus far.
Without further ado, our engineering team has released a fix for this publishing issue today.
To publish your Android app, click the “Publish Android” button in the top right of the builder. You’ll see a box pop up with the option to select “Target build for Android 12 (API level 31).” If you select this box, you will be able to publish your new apps to the GooglePlay Store.
We hear your feedback and are diagnosing internally to ensure that this does not take the amount of time it did for us to deploy in the years to come.
If you have any further questions about this, please feel free to direct message me here or email me directly at cassandra@thunkable.com. I’m happy to chat with you further about this.
Thank you all for your support of Thunkable thus far, and we can’t wait to see all those new apps on the Google Play Store.
Best,
Cassandra
1 Like
Hello Cassandra
for me, my application still does not work
would you be so kind to tell me if this is going to be fixed in this week? as you mention with the new update.
thanks
1 Like
Hi @ingraulbarbosa70a - thanks for reaching out. I’ve you’ve been having issues opening your project both before and after this update then the cause is possibly not the API update. Since this topic has gotten quite noisy, can I ask that you create a new question in #thunkable. if you haven’t done so already, specifically about this.
Thanks
2 Likes
Hi!
This is the link for the issue:
1 Like
Still having issues with this.
Downloading APK with the new API won’t install due to an error. I can only install an APK downloaded with the old API.
Publishing to play store with new API entirely broke BLE in my app. I get the error “BleError: Cannot start scanning operation”. BLE works in both the APK using the old API and the live test in the thunkable app.
2 Likes
Appreciate you flagging this. I’ll reach out over email to get more details from you so we can investigate.
Best,
Cassandra
1 Like
@jon.fawcett8aghe Please build your APK with the Android API 31 again. We just released a new fix and expected it to work again.
Thanks,
Wei
2 Likes
@jon.fawcett8aghe - just checking in to see if the fix we released is working ok for you?
Thanks,
Domhnall
It solved the play console upload issue. But I’m having BLE errors for users on android 11 when it’s compiled with API 31. My workaround is to provide an APK compiled without the new checkbox.
@wei do we have to program the apps again in thunkable and then upload
Excellent - that’s the main thing.
Do you have a separate thread open for this already? (mainly wondering which errors you’re seeing!)
You mean, you’re still targeting API 30? Or something different?
Thankfully not @purpletutor! you just need to download your app again, just make sure you are targeting Android 12 with your build.
I don’t have a separate thread. The error when running the app on Android 11 when compiled with API 31 is this:
So my quick workaround was to make 2 different APK’s for people to manually install for the time being. Obviously this needs solved for play store
- Compiling with API 30 solves this error and works for Android 11.
- Compiling with API 31 works for Android 12.
1 Like
This has previously happened and was due to some entries that has to exist in the manifest file.
This is a task for the developers and we, users, does not have access to it.
1 Like
@cassandra Any solutions for this? It’s not a good workaround to require Android 11 and older users manually install an APK while Android 12 users install from the Play Store.
1 Like
Hello,
Since the latest update, Bluetooth scan no longer works.
It no longer times out and continues to scan endlessly. Please fix the error as soon as possible.
I tested on Android 10,11,12.
2 Likes