I am trying to publish an upgrade to my app in Android Market. I am using the same key and alias as before (I have only one key and a single alias). But I get the error "The apk must be signed with the same certificates as the previous version.". This is not the first time I am uploading upgrades. Never had problems before.
The only difference I have this time is I added a new sub-package to the project. My base package is "in.vasanth.android.droidsave". I added a package "in.vasanth.android.droidsave.db". Does adding a package affect the upgrade? Or did I some how mess up my key?
Make sure that you are uploading an exported .apk file, not the one that is normally built in the project's bin directory. Adding a sub-package won't affect anything as long as you haven't changed the package name for the overall application in the manifest file.
Related
When I upload my apk on the playStore(release in alpha), I am getting this error:
Upload failed
You need to use a different package name because
[name of package] is used by a pre-installed
application. To upload a pre-installed application, please contact
Google Play Developer Support. Learn more.
However, it is my first release and no one is using this package name.
Last thing, the version code is 1531. Maybe is it due to that? FOr the first release, I have to set it to 1?
There exists other application with the same package name for sure.
You can refactor-rename your package name, and make it sure that changes reflect in a manifest file, Proguard configuration etc.
Copy your Package name in the Manifest file
<package="com.example.myapplication"> Press ctrl+shift+R enter your old package name and replace with a new one.
Your application is having the same named package, which is already used by some other app on play store.
The solution is to change the package name using refactoring. It will change your package name.
Cannot upload app to Google Play because of wrong package name (I included the keyword 'android' in the package name). I tried changing the package name everywhere but this conflicts with the google-services.json file (I am using Firebase in this app). I tried creating a new app within my Firebase Console with a different package name and then I downloaded and placed the new google-services.json file in the right place. The app still doesn't work (Users cannot authenticate in my app). Any suggestions?
I know that almost identical question was asked here, but accepted answer doesn't work for me.
Make apk with Capitalized package name in android studio
Let me explain.
Our Android app was developed in Xamarin.Android, we did a mistake with package naming - Visual Studio and Xamarin configured our's app manifest with uppercased package name (this was a mistake which now I pay with my sanity). It worked for Xamarin version, but we decided to rewrite that app in Android Studio after some releases. Now the problem begins...
We are not able to directly deploy/install apk on devices older than Android 8.0, we get following error: INSTALL_PARSE_FAILED_MANIFEST_MALFORMED
It's funny that issue does not exists on devices with newest API.
It's clearly issue with our package name which is something like:
YES_We_Failed_On_It.We_Failed_Very_Badly
If I change it to lowercased everything works, but the case is we can't release another application with different package name.
Is there any possibility to fix this?
It will be self answer question.
If anyone else will be at my position, fix is quite simple.
As mentioned in docs: https://developer.android.com/studio/build/application-id.html
When you create a new project in Android Studio, the applicationId exactly matches the Java-style package name you chose during setup. However, the application ID and package name are independent of each other beyond this point. You can change your code's package name (your code namespace) and it will not affect the application ID, and vice versa (though, again, you should not change your application ID once you publish your app).
Application ID and Java package name are not the same.
So to fix this I renamed my package to be lowercased and stayed with uppercased Application ID. Problem disappeared.
At the end of build, build tools copy our Application ID into final APK's manifest, that's why it's still the same package I think.
Also from docs:
One more thing to know: Although you may have a different name for the manifest package and the Gradle applicationId, the build tools copy the application ID into your APK's final manifest file at the end of the build.
Is it possible to create two Firebase projects with the same SHA-1? because I have an android project created already and the installed application are targeting that project, now for some reasons I need to use another project for the newer versions of the same applications so the existence of both firebase projects is necessary.
But I wonder how would I do it with the same SHA-1 because it gives me error and I am not able to find a way?
The error message says:
An OAuth2 client already exists for this package name and SHA-1 in another project
Read the error message carefully. It says it's using both the package name of the app and the SHA-1. This means you can have the same SHA-1 in two projects, but the package names of the app (also called "application id") must be different. Likewise, you can have two projects that have the same package name, but they can not have any of the same SHA-1 added to them.
The combination of package name and SHA-1 must be unique.
Create a copy of your project and change the project package name everywhere, and keep the Sha1 It should work.Create another project in firebase and add it.
When I attempt to upload my apk then everytime I get the following error:
"Upload error
UPLOAD NEW APK TO PRODUCTION
Upload failed
You need to use a different package name because "com.google" is restricted."
When I rename or refactor based on the multiple different steps suggested on this site to change "com.google.samples.apps.myapp" it breaks the program in a manner which then prevents it from a successful "build"
I have read and reread: "com.example restricted" Google Play error; even when changing the package name AND also
Android Studio Rename Package
I suspect that the refactor does not correct the links I need to the R file? Any help would be appreciated.
If you're using Android Studio / Gradle you don't need to change your package name (as it impacts your resources) but only the "applicationId" which is whats used for publishing.
Details here: http://tools.android.com/tech-docs/new-build-system/applicationid-vs-packagename