First I uploaded one app with one package and now client changed the package name, in my app I used FB login and push notifications with the old app, so I have to change any thing in the FB developer either I have to create new account or I can use the old fb developer account and app_ID, with changing of the Package name.I am so much confused what I have to do, when I change the package name,please suggest some solution.
You also have to change the folder names to match the name of the new package.
For example the package:
xxx.yyy.zzz
Should correspond to the directory:
xxx/yyy/zzz
First , In android code, you will need to change package names in manifest xml and gradle mainly. use refractor for that.
secondly,
you mentioned that you used fb login and push notifications,
so for these, you will need to make some changes .
in Facebook developer app settings page, simple add your new package name to existing package list,
and for GCM push notifications, do the same on developer console and create new configuration files and add them to your project and everything will work fine.
Related
I want to know that can I publish a new android app with existing app package name?
i.e I have a photo editor and its package name is com.myapps.photoeditor. now I want to make new version but i will publish VPN. so the new app will totally different.
VPN will be ok with existing package name com.myapps.photoeditor?
plz guide me
No, you cannot do this. Package name basically I unique ID for an app. When a package name is associated with an app and it is published over google play this is a unique ID for that app. You cannot publish new app with the same package name but you can update the app.
You can't publish two apps with same package name as google consider it as primary key but story doesn't end here. There are two things you can do:
you can update your app, here updates mean you can remove existing feature, you can add new feature, you can modify existing feature but you have to handle it properly.
But you want the new feature in a separate app then you should change clone your existing code and add new feature and change package name before publishing. (Not Recommended)
If you mean by package name as the applicationId in build.gradle, then the answer is NO. Your new VPN app will overwrite your existing Photo editor app.
If you mean by package name as the package name used by your source codes, then the answer is IT DEPENDS. YES you can use same package name in source code provided that you provide different name for applicationId. NO you cannot if you provide the same name for applicationId regardless of what you use as the package name used by your source codes.
Know the difference here: https://developer.android.com/studio/build/application-id
If you want to release a new app with applicationId (from app/build.gradle) same as any apps before, you can't do it.
If you want to update an existing app with complete new ideas or feature or name or type, having access to that app's signing keys and developer account, yes you can do it. Just release with version code greater than before
I have an Android app and its package name is com.domain.myapp. During the development, I have to change it to something else due to some reasons and I changed it to com.domain.myappandroid.
Now, I have to integrate Facebook SDK for Android and it asks me to add the package name and the class name of my Activity. My Activity is named GameActivity and it is in com.domain.myapp.activities, the package name didn't change to com.domain.myappandroid.activities after changing my app package name.
I know that the package name is com.domain.myappandroid but I am not sure if I should use com.domain.myapp.activities.GameActivity or com.domain.myappandroid.activities.GameActivity. I tried both and I don't know if it is working or not since the dashboard says 0 installs for Android.
Please help, thanks!
Note:
I am using using Facebook Android SDK v3.0.2 and I can't verify if it is reporting the app installs properly.
Write the package name of your app i.e. com.domain.appandroid. It will work fine.
actually you should use com.domain.myapp， the class name have nothing to do with the Facebook SDK function but callback to game site ， it means wether classname you used， the Facebook function will worked well， but if you use the com.domain.myappandroid， players click the message that send by their friends， the game will not launched。。。。 so ~ use com.domain.myapp~ i just have the same case~ and i worked very well by this way！
I am creating Oauth 2.0 client id for DrEdit gdrive sample application.
I am doing everything as explained in Readme file of the repo. providing my SH1 certificate and giving package "com.example.android.notepad" , but when i am clicking on "create client id" then it is saying that "This client ID is globally unique and is already in use."
Please tell me how to setup this app and create client id for it.
Thanx
(From comments, please give complete answers in the future)
com.example.android.notepad is already in use. Change the package name of you app.
Just to add a little more detail Ali's correct answer:
You must change the package name in your android manifest file for it to work. You do not need to change the package names in the java files themselves.
I try to update customers App in Google Play, this is my first time I do this.
I created a certificate, it seems to be fine. The app was packaged with appcelerator titanium.
When I upload the app in store I get this message:
The name ofupdated APK-Package (gdp.app) must be the same with the package I want to replace (de.gdp)
File Name I upload is: GdP.apk
What do I have to change?
You changed the package name. You have to use the same package name as the original .apk.
Change your package name back to de.gdp .
More information:
http://developer.android.com/guide/topics/manifest/manifest-element.html
"I wont to replace (de.gdp)"
well, you cannot rename your package. If you change your package name the store recognizes it as a different app.
so you cannot update it with different package name.
Renaming your package to gdp.app will solve the issue.
If the package name and signing certificate do not match those of the existing version, Market will consider it a new application, publish it as such, and will not offer it to existing users as an update.
So, you have to maintain the same package name of previous build.
See this link: http://lokeshatandroid.blogspot.in/2012/07/upload-apk-into-android-market.html
During the upgrade of my android application, I changed the package name. But Android market doesn't allow to upload the changed package name application as an upgrade. If I upload the application as a new application, will the user have two applications on his/her device? How can I make sure that the user doesn't have to download the application again from scratch without reverting the change of my package name?
two package = two different application in market place.
Once you upload one app, its package should be same. Also, the key should be same.
Android market is only concerned about the package name in your manifest, not the actual packages name in the source.
You could try to give the old package name in the manifest attribute, then for activities give the new package name instead of relative (ie .MainActivity)
Like this:
<manifest package="your.old.package" ...>
...
<application android:name="your.new.package.MainActivity" ...>
Could work..
I plan to serve two versions of my app (paid/free) this way and using same project and code.
If you change the package name, it's treated as a separate app - not just in the market, but apk's in general will only 'replace' the same package name (and only if they're both signed with the same key).
Although it's possible to phase over to a new key by signing an intermediate package with both keys, there's currently no easy way to phase over the package name.
The best that can be done is this:
New apk version is signed with the same key, but has a different package name.
When installed, the new apk arranges to use the shared_prefs with the old package name.
The data is copied across to the new package name.
The new version requests that the old version is removed, and the user sees the uninstall dialog.
Note app data is usually kept here:
/data/data/pac.kage.name/
I haven't tried this, so I can't give anymore details yet. You may also be interested in my request for a seamless way of transitioning the package name.