When an app is updated in the Google Play Console (only for development) does the app have to be manually...
We are developing an Android app and using the Google Play Store. The app has not yet been published - we are still testing.
Our developers tell us that we have to delete the app before updating. When we haven't done that the app is all messed up.
They say that this is an artifact of only being in development, and that once we go to the store users will not have to delete the app.
I want to confirm that this is the case and there is not a different reason why the update fails.
Are others having this issue?
android 
google-play-console asked Jan 2 at 17:03
Bryan SchmiedelerBryan Schmiedeler
1,20121338
add a comment |
We are developing an Android app and using the Google Play Store. The app has not yet been published - we are still testing.
Our developers tell us that we have to delete the app before updating. When we haven't done that the app is all messed up.
They say that this is an artifact of only being in development, and that once we go to the store users will not have to delete the app.
I want to confirm that this is the case and there is not a different reason why the update fails.
Are others having this issue?
android google-play-console asked Jan 2 at 17:03
Bryan SchmiedelerBryan Schmiedeler
1,20121338
2
you definitely don't need to delete the app to re upload a new one. i just release a new build after changing the versionCode as stated below.
– soldfor
Jan 2 at 17:33
No need to delete the app. If you described what you call "messed up", we may be able to help a little more understanding the source of the issue. Possibly, the developers are changing the database in a non-backwards compatible way during development.
– Pierre
Jan 2 at 17:49
Pierre, this is exactly what I was thinking. If you change the SQLite schema of data in the app then you must detect this and upgrade the schema and data. We should get a new build tomorrow so I will test this. I am a little worried that this is the case, and we will release a build in production sometime where deleting the app would be catastrophic.
– Bryan Schmiedeler
Jan 2 at 18:13
add a comment |
We are developing an Android app and using the Google Play Store. The app has not yet been published - we are still testing.
Our developers tell us that we have to delete the app before updating. When we haven't done that the app is all messed up.
They say that this is an artifact of only being in development, and that once we go to the store users will not have to delete the app.
I want to confirm that this is the case and there is not a different reason why the update fails.
Are others having this issue?
android google-play-console asked Jan 2 at 17:03
Bryan SchmiedelerBryan Schmiedeler
1,20121338
We are developing an Android app and using the Google Play Store. The app has not yet been published - we are still testing.
Our developers tell us that we have to delete the app before updating. When we haven't done that the app is all messed up.
They say that this is an artifact of only being in development, and that once we go to the store users will not have to delete the app.
I want to confirm that this is the case and there is not a different reason why the update fails.
Are others having this issue?
android google-play-console android google-play-console asked Jan 2 at 17:03
Bryan SchmiedelerBryan Schmiedeler
1,20121338
asked Jan 2 at 17:03
Bryan SchmiedelerBryan Schmiedeler
1,20121338
asked Jan 2 at 17:03
Bryan SchmiedelerBryan Schmiedeler
1,20121338
asked Jan 2 at 17:03
Bryan SchmiedelerBryan Schmiedeler
1,20121338
asked Jan 2 at 17:03
Bryan SchmiedelerBryan Schmiedeler
1,20121338
1,20121338
2
you definitely don't need to delete the app to re upload a new one. i just release a new build after changing the versionCode as stated below.
– soldfor
Jan 2 at 17:33
No need to delete the app. If you described what you call "messed up", we may be able to help a little more understanding the source of the issue. Possibly, the developers are changing the database in a non-backwards compatible way during development.
– Pierre
Jan 2 at 17:49
Pierre, this is exactly what I was thinking. If you change the SQLite schema of data in the app then you must detect this and upgrade the schema and data. We should get a new build tomorrow so I will test this. I am a little worried that this is the case, and we will release a build in production sometime where deleting the app would be catastrophic.
– Bryan Schmiedeler
Jan 2 at 18:13
add a comment |
2
you definitely don't need to delete the app to re upload a new one. i just release a new build after changing the versionCode as stated below.
– soldfor
Jan 2 at 17:33
No need to delete the app. If you described what you call "messed up", we may be able to help a little more understanding the source of the issue. Possibly, the developers are changing the database in a non-backwards compatible way during development.
– Pierre
Jan 2 at 17:49
Pierre, this is exactly what I was thinking. If you change the SQLite schema of data in the app then you must detect this and upgrade the schema and data. We should get a new build tomorrow so I will test this. I am a little worried that this is the case, and we will release a build in production sometime where deleting the app would be catastrophic.
– Bryan Schmiedeler
Jan 2 at 18:13
2
2
you definitely don't need to delete the app to re upload a new one. i just release a new build after changing the versionCode as stated below.
– soldfor
Jan 2 at 17:33
you definitely don't need to delete the app to re upload a new one. i just release a new build after changing the versionCode as stated below.
– soldfor
Jan 2 at 17:33
No need to delete the app. If you described what you call "messed up", we may be able to help a little more understanding the source of the issue. Possibly, the developers are changing the database in a non-backwards compatible way during development.
– Pierre
Jan 2 at 17:49
No need to delete the app. If you described what you call "messed up", we may be able to help a little more understanding the source of the issue. Possibly, the developers are changing the database in a non-backwards compatible way during development.
– Pierre
Jan 2 at 17:49
Pierre, this is exactly what I was thinking. If you change the SQLite schema of data in the app then you must detect this and upgrade the schema and data. We should get a new build tomorrow so I will test this. I am a little worried that this is the case, and we will release a build in production sometime where deleting the app would be catastrophic.
– Bryan Schmiedeler
Jan 2 at 18:13
Pierre, this is exactly what I was thinking. If you change the SQLite schema of data in the app then you must detect this and upgrade the schema and data. We should get a new build tomorrow so I will test this. I am a little worried that this is the case, and we will release a build in production sometime where deleting the app would be catastrophic.
– Bryan Schmiedeler
Jan 2 at 18:13
add a comment |
1 Answer
1
active
oldest
votes
Production, Open, Closed, Internal tracks, it is all about visibility of your app. You could manage independent any of them.
After upload apk, each added to Artifact library. The main rule your apk always should has distinct of the versionCode. Change him in build.gradle file.
When you manage track for example internal track, right now your versionCode is 10, your developers made a lot of new features, then increase version code to 11, build release apk and reupload apk to internal track. It will automatically change your current version to new version of apk. You don't need to delete old apk before upload new one.
Sorry for my broken English :)
answered Jan 2 at 17:20
Dmitro IvanovDmitro Ivanov
748149
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f54010330%2fwhen-an-app-is-updated-in-the-google-play-console-only-for-development-does-th%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
Production, Open, Closed, Internal tracks, it is all about visibility of your app. You could manage independent any of them.
After upload apk, each added to Artifact library. The main rule your apk always should has distinct of the versionCode. Change him in build.gradle file.
When you manage track for example internal track, right now your versionCode is 10, your developers made a lot of new features, then increase version code to 11, build release apk and reupload apk to internal track. It will automatically change your current version to new version of apk. You don't need to delete old apk before upload new one.
Sorry for my broken English :)
answered Jan 2 at 17:20
Dmitro IvanovDmitro Ivanov
748149
add a comment |
Production, Open, Closed, Internal tracks, it is all about visibility of your app. You could manage independent any of them.
After upload apk, each added to Artifact library. The main rule your apk always should has distinct of the versionCode. Change him in build.gradle file.
When you manage track for example internal track, right now your versionCode is 10, your developers made a lot of new features, then increase version code to 11, build release apk and reupload apk to internal track. It will automatically change your current version to new version of apk. You don't need to delete old apk before upload new one.
Sorry for my broken English :)
answered Jan 2 at 17:20
Dmitro IvanovDmitro Ivanov
748149
add a comment |
Production, Open, Closed, Internal tracks, it is all about visibility of your app. You could manage independent any of them.
After upload apk, each added to Artifact library. The main rule your apk always should has distinct of the versionCode. Change him in build.gradle file.
When you manage track for example internal track, right now your versionCode is 10, your developers made a lot of new features, then increase version code to 11, build release apk and reupload apk to internal track. It will automatically change your current version to new version of apk. You don't need to delete old apk before upload new one.
Sorry for my broken English :)
answered Jan 2 at 17:20
Dmitro IvanovDmitro Ivanov
748149
Production, Open, Closed, Internal tracks, it is all about visibility of your app. You could manage independent any of them.
After upload apk, each added to Artifact library. The main rule your apk always should has distinct of the versionCode. Change him in build.gradle file.
When you manage track for example internal track, right now your versionCode is 10, your developers made a lot of new features, then increase version code to 11, build release apk and reupload apk to internal track. It will automatically change your current version to new version of apk. You don't need to delete old apk before upload new one.
Sorry for my broken English :)
answered Jan 2 at 17:20
Dmitro IvanovDmitro Ivanov
748149
answered Jan 2 at 17:20
Dmitro IvanovDmitro Ivanov
748149
answered Jan 2 at 17:20
Dmitro IvanovDmitro Ivanov
748149
answered Jan 2 at 17:20
Dmitro IvanovDmitro Ivanov
748149
748149
add a comment |
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f54010330%2fwhen-an-app-is-updated-in-the-google-play-console-only-for-development-does-th%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
2
you definitely don't need to delete the app to re upload a new one. i just release a new build after changing the versionCode as stated below.
– soldfor
Jan 2 at 17:33
No need to delete the app. If you described what you call "messed up", we may be able to help a little more understanding the source of the issue. Possibly, the developers are changing the database in a non-backwards compatible way during development.
– Pierre
Jan 2 at 17:49
Pierre, this is exactly what I was thinking. If you change the SQLite schema of data in the app then you must detect this and upgrade the schema and data. We should get a new build tomorrow so I will test this. I am a little worried that this is the case, and we will release a build in production sometime where deleting the app would be catastrophic.
– Bryan Schmiedeler
Jan 2 at 18:13