Hi i have a company app with few thousand downloads done by a developer who is not working with me anymore. I didn't knew much about these android package name stuff and he has used his name in my app package name with app name.
eg.. com.micheal.myapp
Now he is not giving me source code too.
So is there anyway to upload a new package like com.myapp.appname and keep all those downloads and reviews?
Unfortunately there is no way until you don't get previous application source code and application key store.
if you upload a new package then it'll be considered as a new application.
Related
I would like to rename an App which is already in playstore. Could i do something about, finding my app even when user's type in the old App name instead of new one?
Note : I am not changing the package name of the app.
you could follow the google's answer. Change your app description with your search keywords.
https://support.google.com/googleplay/android-developer/answer/4448378?hl=en
You can use the new name in your source, but in store listing, app name can be as follows:
New Name (formerly Old Name)
After installing the app, a user would only get new app name as defined in the source.
App Name length has been extended from 30 chars to 50 chars, so that should be enough.
This way your app would show up even when the users are searching using the old name.
Another thing is that the users would trust that they are using the same app but with just a different name.
I decided to change my app's package name and changed it using this tactic: https://stackoverflow.com/a/29092698/6144372 and then manually changed the package name defined in google-services.json file under this tag: "package_name": "com.xxx.xxx", but when I saw the package name in the Settings section of Firebase Console, it still shows the old one there.
So, I wanted to know that will it cause some bad effect on my app's performance in future or will it not do any harm? Please let me know
And if there is some way of changing the package name in Firebase Console settings too, let me know that too.
You should consider creating a new Firebase project. Just delete the old project and create a new one, with your new package name. I am not sure about the performance issues of just changing the old google-services.json file, but creating a new project is certainly more secure to prevent any future issues.
UPDATE: Thanks to TommieC.'s comment, a better way would be to add a new app to the project and just delete the old app. The new app will have your updated package name. Then download the google-services.json and replace it with the old file.
This method would be safer, in case your firebase project already has different integrations and deleting it is not really an option.
The problem arises when your firebase package name and application ID doesnot match. There is no any rename features in firebase project. You should create the new firebase project that matches the application Id and delete the old project. Then just import respective firebase project json to your code project. That should do the trick
What are the package names like "com.example.etc." in Android Studio representing? Does it actually have any association with the domain and website? Many tutorials I have read state to use a domain name you own. Why is this?
When releasing your application on the market, your application needs an unique package name. This will correspond to the ID on the market.
So choose a package name like your own domain, or your name... in order to have something unique.
Your package is is your Id when U upload in play store , It will recognize only by Id which is package name ,
Please give as com.companyname.appname.
Hi I am new to android and trying to publish on Google play first time.
I am getting error when uploading apk file saying file name should be in format com.example.myapp.apk
my package name is androidapplication1.androidapplication1.apk
there is no com in it!
is this the source of issue?
androidapplication1.androidapplication1.apk sounds like the file name of your application, not its package name. An apk file name shouldn't have more than one dot in it I believe.
The package name on the other hand should have multiple dots. The package name can be found in your manifest xml file. What does it say for that one?
Have a look here.Taken from the developer site:
A full Java-language-style package name for the application. The name should be unique. The name may contain uppercase or lowercase letters ('A' through 'Z'), numbers, and underscores ('_'). However, individual package name parts may only start with letters.
To avoid conflicts with other developers, you should use Internet domain ownership as the basis for your package names (in reverse). For example, applications published by Google start with com.google. You should also never use the com.example namespace when publishing your applications.
The package name serves as a unique identifier for the application.
It's also the default name for the application process (see the
element's process process attribute) and the default
task affinity of an activity (see the element's
taskAffinity attribute).
Caution: Once you publish your application, you cannot change the
package name. The package name defines your application's identity, so
if you change it, then it is considered to be a differen
t application and users of the previous version cannot update to the new version.
I created a sample app in my own development server with your package name androidapplication1.androidapplication1.apk . I didnot receive any errors. So you can either ask google for this issue or ensure that this package is not used by anyone in the play store.
Any android developers had any success changing the package name of your application (in the manifest) of an application already being distributed in the Market?
During my upgrade progress, I decided to change the package name slightly, which means that android identifies it as a new application. So, I suppose saved preferences will be lost, but I'm really hoping there are no other "surprises" for upgrading users.
Cheers!
It's not that the saved preferences will be lost, it's just that Android will set it as a completely new and seperate program which cannot access the old application's preferences.
However, if you sign your applications with the same signature and and give them the same userId then they can share information and you could migrate the original application's information to the new one.