I've an application which has two product flavors:
production
development
Current .apk version published inside play store is with version code 40 and it's production flavor, so the package looks something like this: "example.smth.app". I've released a new functionality in development environment and I want to fully test billing inside my android application. I cannot receive SKUs, because I run the code with development flavor and that's normal as I have to post development version to access SKUs list.
Well, I made an .apk for development environment. It has version code 36. I got an message that:
Your APK or Android App Bundle needs to have the package name "example.smth.app".
You need to use a different version code for your APK or Android App Bundle because you already have one with version code 40.
Well, I could just solve the second point by changing the version code of .apk from 37 to 40 and that would resolve this, I guess, but what to do with the first point?
For development apks we have package name like this: "example.smth.app.dev" - does this mean that it's not possible to post this .apk to beta channel?
No, it is not. The beta channel has the same package name as all other channels. The package name is fix for the app.
Related
I have seen a similar stack overflow question but none that was for AppCenter. You can see that I have completely different version number and version codes for each release. I downloaded release 332, then tried download release 333 and this error message happens. How do I fix this? Why does this not happen on iOS appcenters?
Are all of your builds signed with the same release signing config? If the builds are not signed with the same key then you will get this error because it treats them as two different applications instead of an upgrade to the existing application.
Your old app has the same package name that the new app has. Whatever the version number maybe, you cannot install another app with same package name. Assuming, the old package name is com.demoapp New app will not accept its package name as the same as above. It should be something like com.demoappCopy.
I have one android app (e.g MyApp) in the Google Play Store, and at the moment the package is from the RC build in our pipeline, but we also want to publish package from CI build for testers. Is it better to create a new app called MyAppTest in play store which receives the package from CI build? Or is it better to just upload the package from CI build to "MyApp" under internal testing track? In the package from RC build, the version is like 1.0.0-RC1, and the package from CI build the version is like 1.1.0.1.
What is the best practice for this problem?
You should keep all into a single project! And use the different levels of testing of google play (alpha, closed beta, open beta).
Usually there are some levels of testing:
Internal testing (Release Candidates)
Open Beta for selected users
You should try to scale the same version from internal, to open beta to production. Most versions will be transitory, and won't reach production at all.
But you should keep the semantic versions all the way, some devs like to add -RC or -beta after the version to name, to tag as "in testing" version.
I have a "normal" Android app, made in Eclipse/java, published in Play Store, already at version 3.x, all works fine.
Now I am thinking to move the project to Xamarin/c#, and make the 4.0 there.
My question, what should I take care/be aware, that this change should be a natural continuation of the 3.x from Google Play/Users perspective?
So that I could simple upload the APK made by Xamarin to Dev Console as a new version upgrade, and not as a new App.
Like:
Existing signing key should be reused in Xamarin?
Package name (java <> xamarin c#) must be the same?
???
Thanks
There is absolutely no difference for google what language you natively used to write an app. By the way Xamarin will be compiled to java before packaging into apk.
Also Xamarin uses the installed Android SDK and installed Java SDK you have used before to sign the apk and compile the app. It also is going to use same keys so sign the apk.
So no worries, keep same package name and you're good for the update.
I am new to kobotoolBox, I was required to add some changes to kobotoolBox project. I have successfully run the project in android studio and have applied changes and now need to publish that.
I want to ask that I have cloned this project from GitHub means it has the same package name with which already an APK is published on play-store. What should I do to publish APK that I have created. Should I need to change the package name or there is another alternative way aside from changing package name??
You may check this guide to help you started.
Publishing is the general process that makes your Android applications
available to users. When you publish an Android application you
perform two main tasks:
You prepare the application for release.
During the preparation step you build a release version of your
application, which users can download and install on their
Android-powered devices.
You release the application to users.
During the release step you publicize, sell, and distribute the
release version of your application to users.
Explore the page for you to get the proper steps when publishing an application.
Hope this helps.
Inside of the Android Developer Console I would like to have 2 applications, MyAppName and MyAppName-Staging. The only differences between these two apps would be:
The API environment they point (prod vs. staging)
One would be for external Play Store release while the other (MyAppName-Staging) would be intended only for internal users in my company.
Would I be allowed to use the same package/app ID for both of these or would I need to change the package ID for each one? My assumption is I would need to change it, if thats the case can I use the same code base but just change the app ID and rebuild the apk to achieve this?
For additional context I've built this app using Nativescript. So all packaging info is handled through a package.json file and code signing must be done through the CLI. I just want to make sure I can't code sign myself into a situation where I can't release my build to production (the MyAppName build) Thanks for any guidance.
From my experience, Google Play Store doesn't allow 2 apps having the same package name to be published. You would need to either:
Change your package name
or if you want to have the same package name regardless,
Upload your staging app (with the same package name) to the beta channel of your live app then select users to be invited to the beta.
The developer console has the concept of beta builds that you can distribute to list of members or open to play store. You could build with same package name but pointing at different environment and distribute through there.
Then point back to prod when you release your official build.
https://support.google.com/googleplay/android-developer/answer/3131213?hl=en