if you provide set username in thunkable when we sign up than it will more helpful…may be i am wrong but its just a suggestion …by the way thanks for the new update 
seriously we need this
1 Like
Unfortunately it deletes an app from me before I know the changes and when I opened the backup this change must have been made, I can no longer update my application in the Play Store, I am really very sad about this news. If anyone can help me, please. 
Guys i think this is one of the best news so far in 2018. been able to use custom package names. if you have a company name PuzzleGames LTD and you are using same as your developer name at Playstore, i think you should probably have a gmail account to that name as well like puzzlegames@gmail.com. when you publish your app, that will automatically be the username of your app signifying your company name.
1 Like
Why would a programmer dedicate his time for that ??? this New Update is cool and very good and if any one can do that in thunkable, such a person can also do that in Android Studio or even AppyBuilder which also allows customising package name. Lets embrace this change/feature and look at the positives it brings
This is a Pro Feature been offered by Thunkable for Free and We are Grateful to Team @thunkable .
1 Like
Unfortunately it deletes an app from me before I know the changes and when I opened the backup this change must have been made, I can no longer update my application in the Play Store, I am really very sad about this news. If anyone can help me, please.
what happen ?
count it plus one! @albert
same to me here:
In the development of my app, I often make duplicates and because of that I do “Save app as”. Now it seems that this changes the apk name.
Now the update is not accepted in the german playstore:
I checked the corresponding aia file:
I really think, you can do what you think is best for thunkable, and I trust in the @thunkable developer team.
But I cannot understand, why you made this choice:
Publishing in the PlayStore is the most vulnerable part, when you have put months of work into the project. And I am sure you knew, that this problem would be coming for a lot of users!
cheers,
User81
EDIT 18.02.2018, 11:10 :
The easiest way for me was a new app in the app store. My steps:
- Create a gmail-acount with your companies name (this name will be in the apk-name)
- Create a new thunkable account by logging in with this gmail-account.
- Create Project or import your aia-Project
- Export keystore and keep it somewhere really save!
- Export aia and apk at the same time and keep them save in a archive folder
- publish in appstore
(I was able to keep the exact Name of the app(“MyApp”), because the apk-name has changed from “com.thunkable.MyCompany.MyApp” to “com.MyCompany.MyApp”)
! But I have to tell the users of my app to install this new app !
Hope this may help someone! Keep thunking
1 Like
We understand that we created some issues with our package name change. We are working on a change that will allow you to import old .aia files and keep their old package names. We expect that to be available soon.
Sorry for the trouble that this has caused.
-Mark
4 Likes
Thank you @Mark I’m really looking forward to it because I can’t update some apps until you fix this issue!
Hi,
I am also stuck to release a new update apk on play store, due to package name changed.
Sir, I have published an app on google play store now I want to update the app but it is show package name problem what should I do. and I have aia file of previous version app. need help please help me. when ever I upload my apk file it says that package name should be com.thunkable.android.worksaransh.RRR. I am really confused what should I do?
seriously, are you all unable to read?! It is LITERALLY 2 posts above…
To ask stuff right below the solution without even taking the slightest effort on reading is really ignorant behaviour… Sometimes I get the feeling people like spending more time in writing different forms of “help me/i need help/help please/do help me!!!” than spending a few minutes trying to find a solution themselves 
Because I feel like you still won’t be able to find it, here again:
1 Like
Thank you everybody @gurmeet @domhnallohanlon @albert @Mr_Blackd @Choofa @Avram I have sucessfully update my app on google play store. If I have annoyed you guys by questions than please forgive me . But thank you all again.
3 Likes
How to sovle bro
http://community.thunkable.com/t/your-apk-needs-to-have-the-package-name/20759
Plz check and help sir
I have just tried to update my app and Google bans you from uploading a APK as it does no longer have the com.thinkable prefix, this is a BIG PRO|BLEM caused by your LITTLE Change…
I have had to rename the app, as you cannot have the same app name on Google Play,
Gone through the entire creation process again, including all the certification and image loading, form filling etc.
By your little change you have removed the security of my original app and made it invalid!
“Existing app projects will maintain their same package names” This is not true in my case, my original project change when I compile the apk and have the new format com.{username}.{appname}, so i cant update my app in the store.
“uploading legacyapp project (.aia) from my computer” doesn’t work because my legacyapp was beta.thunkable. what can i do?
1 Like
This update broke my package name
I love using this old update
But when i import my aia using legacy option its not change my package name to ai format.So ı cant update my old apps on google play fix it guys @albert @wei @domhnallohanlon
Sir Albert: My App was uploaded in Play Store originally compiled from beta.thunkable, so it has the format: com.thunkable.android.myname.myappname, I need to launch an update, so I need to keep that same format, but when I export from beta.thunkable and then import from thunkable (with the Legacy option), this does not keep the old format. Can you do something to fix it?
Nor does it help me to import from AIA, since I need the format com.thunkable.android.myname.myappname
Do you get me?
Thanks in advance!