APK carrying Old data
I don't even know where to start. This is something I never expected. So I published my app on app store, all works fine but when any user logs in with their username and password instead of loading user's data my app loads the test sqllite data 'I never stored' in my app. Once I go to the app and 'Clear Storage' and ask users to login, then they get the correct data.
It seems like the apk is somehow carrying the sqllite database with test data.
I understand this is not enough information although I am completely confused. On the top the data is not the latest test data.
Is it like my app is packing sqllite with it with data or is it getting dumped somewhere on Google Play store and get attached with everyone's installation? .
android sqlite xamarin asked Nov 18 '18 at 12:15
AliAli
1,0511319
add a comment |
I don't even know where to start. This is something I never expected. So I published my app on app store, all works fine but when any user logs in with their username and password instead of loading user's data my app loads the test sqllite data 'I never stored' in my app. Once I go to the app and 'Clear Storage' and ask users to login, then they get the correct data.
It seems like the apk is somehow carrying the sqllite database with test data.
I understand this is not enough information although I am completely confused. On the top the data is not the latest test data.
Is it like my app is packing sqllite with it with data or is it getting dumped somewhere on Google Play store and get attached with everyone's installation? .
android sqlite xamarin asked Nov 18 '18 at 12:15
AliAli
1,0511319
What database did you use?
– tm13
Nov 18 '18 at 12:24
Azure mobile services database, it's sqllite
– Ali
Nov 18 '18 at 12:25
You should check new user's entered data with the data saved in database. If they are not the same, you should database. Did you do like this?
– tm13
Nov 18 '18 at 12:27
User only gets the data as per their user ID, I have all the custom auth and everything setup. Even if it's a new user, the initial data they see is my test data I saved 3 months ago. Upon clear the app storage data when they log in again, it all works fine... This led me to a conclusion that some how the apk is carrying the sqllite database with it in which I stored some test data (3 months ago)
– Ali
Nov 18 '18 at 12:30
add a comment |
I don't even know where to start. This is something I never expected. So I published my app on app store, all works fine but when any user logs in with their username and password instead of loading user's data my app loads the test sqllite data 'I never stored' in my app. Once I go to the app and 'Clear Storage' and ask users to login, then they get the correct data.
It seems like the apk is somehow carrying the sqllite database with test data.
I understand this is not enough information although I am completely confused. On the top the data is not the latest test data.
Is it like my app is packing sqllite with it with data or is it getting dumped somewhere on Google Play store and get attached with everyone's installation? .
android sqlite xamarin asked Nov 18 '18 at 12:15
AliAli
1,0511319
I don't even know where to start. This is something I never expected. So I published my app on app store, all works fine but when any user logs in with their username and password instead of loading user's data my app loads the test sqllite data 'I never stored' in my app. Once I go to the app and 'Clear Storage' and ask users to login, then they get the correct data.
It seems like the apk is somehow carrying the sqllite database with test data.
I understand this is not enough information although I am completely confused. On the top the data is not the latest test data.
Is it like my app is packing sqllite with it with data or is it getting dumped somewhere on Google Play store and get attached with everyone's installation? .
android sqlite xamarin android sqlite xamarin asked Nov 18 '18 at 12:15
AliAli
1,0511319
asked Nov 18 '18 at 12:15
AliAli
1,0511319
asked Nov 18 '18 at 12:15
AliAli
1,0511319
asked Nov 18 '18 at 12:15
AliAli
1,0511319
asked Nov 18 '18 at 12:15
AliAli
1,0511319
1,0511319
What database did you use?
– tm13
Nov 18 '18 at 12:24
Azure mobile services database, it's sqllite
– Ali
Nov 18 '18 at 12:25
You should check new user's entered data with the data saved in database. If they are not the same, you should database. Did you do like this?
– tm13
Nov 18 '18 at 12:27
User only gets the data as per their user ID, I have all the custom auth and everything setup. Even if it's a new user, the initial data they see is my test data I saved 3 months ago. Upon clear the app storage data when they log in again, it all works fine... This led me to a conclusion that some how the apk is carrying the sqllite database with it in which I stored some test data (3 months ago)
– Ali
Nov 18 '18 at 12:30
add a comment |
What database did you use?
– tm13
Nov 18 '18 at 12:24
Azure mobile services database, it's sqllite
– Ali
Nov 18 '18 at 12:25
You should check new user's entered data with the data saved in database. If they are not the same, you should database. Did you do like this?
– tm13
Nov 18 '18 at 12:27
User only gets the data as per their user ID, I have all the custom auth and everything setup. Even if it's a new user, the initial data they see is my test data I saved 3 months ago. Upon clear the app storage data when they log in again, it all works fine... This led me to a conclusion that some how the apk is carrying the sqllite database with it in which I stored some test data (3 months ago)
– Ali
Nov 18 '18 at 12:30
What database did you use?
– tm13
Nov 18 '18 at 12:24
What database did you use?
– tm13
Nov 18 '18 at 12:24
Azure mobile services database, it's sqllite
– Ali
Nov 18 '18 at 12:25
Azure mobile services database, it's sqllite
– Ali
Nov 18 '18 at 12:25
You should check new user's entered data with the data saved in database. If they are not the same, you should database. Did you do like this?
– tm13
Nov 18 '18 at 12:27
You should check new user's entered data with the data saved in database. If they are not the same, you should database. Did you do like this?
– tm13
Nov 18 '18 at 12:27
User only gets the data as per their user ID, I have all the custom auth and everything setup. Even if it's a new user, the initial data they see is my test data I saved 3 months ago. Upon clear the app storage data when they log in again, it all works fine... This led me to a conclusion that some how the apk is carrying the sqllite database with it in which I stored some test data (3 months ago)
– Ali
Nov 18 '18 at 12:30
User only gets the data as per their user ID, I have all the custom auth and everything setup. Even if it's a new user, the initial data they see is my test data I saved 3 months ago. Upon clear the app storage data when they log in again, it all works fine... This led me to a conclusion that some how the apk is carrying the sqllite database with it in which I stored some test data (3 months ago)
– Ali
Nov 18 '18 at 12:30
add a comment |
1 Answer
1
active
oldest
votes
This featured named Auto Backup
Auto Backup for Apps automatically backs up a user's data from apps that target and run on Android 6.0 (API level 23) or later. Android preserves app data by uploading it to the user's Google Drive—where it's protected by the user's Google Account credentials.
for disabling AutoBackup, apply this changes in your application Manifest:
<manifest ... >
...
<application android:allowBackup="false" ... >
...
</application>
answered Nov 18 '18 at 12:32
beigiradbeigirad
18510
Thank you so much, that actually makes sense. Just a question, shouldn't it save user only data under autobackup and restore when user logs in again, why it is restoring my test data for all the users
– Ali
Nov 18 '18 at 12:36
@aliusman You're wrong. It does not restoring test data for all your users, your device and the device google account takes backup of last data on this device. It's not depend on your data and application state, it depends on your device and google account.
– beigirad
Nov 18 '18 at 12:43
Ok let me have another look into it, that was the first complaint I received from almost all my alpha users that they see test data upon login or creating new account until they clear the app storage data and login again to see empty state
– Ali
Nov 18 '18 at 12:45
And the data they see is 3 months old, its not even in live actual database anymore on the server :) this is just crazy
– Ali
Nov 18 '18 at 12:47
That's true. This data does not clear by reinstalling or fresh installing or clear data and so on. You just turn it off.
– beigirad
Nov 18 '18 at 12:49
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%2f53360748%2fapk-carrying-old-data%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
This featured named Auto Backup
Auto Backup for Apps automatically backs up a user's data from apps that target and run on Android 6.0 (API level 23) or later. Android preserves app data by uploading it to the user's Google Drive—where it's protected by the user's Google Account credentials.
for disabling AutoBackup, apply this changes in your application Manifest:
<manifest ... >
...
<application android:allowBackup="false" ... >
...
</application>
answered Nov 18 '18 at 12:32
beigiradbeigirad
18510
Thank you so much, that actually makes sense. Just a question, shouldn't it save user only data under autobackup and restore when user logs in again, why it is restoring my test data for all the users
– Ali
Nov 18 '18 at 12:36
@aliusman You're wrong. It does not restoring test data for all your users, your device and the device google account takes backup of last data on this device. It's not depend on your data and application state, it depends on your device and google account.
– beigirad
Nov 18 '18 at 12:43
Ok let me have another look into it, that was the first complaint I received from almost all my alpha users that they see test data upon login or creating new account until they clear the app storage data and login again to see empty state
– Ali
Nov 18 '18 at 12:45
And the data they see is 3 months old, its not even in live actual database anymore on the server :) this is just crazy
– Ali
Nov 18 '18 at 12:47
That's true. This data does not clear by reinstalling or fresh installing or clear data and so on. You just turn it off.
– beigirad
Nov 18 '18 at 12:49
add a comment |
This featured named Auto Backup
Auto Backup for Apps automatically backs up a user's data from apps that target and run on Android 6.0 (API level 23) or later. Android preserves app data by uploading it to the user's Google Drive—where it's protected by the user's Google Account credentials.
for disabling AutoBackup, apply this changes in your application Manifest:
<manifest ... >
...
<application android:allowBackup="false" ... >
...
</application>
answered Nov 18 '18 at 12:32
beigiradbeigirad
18510
Thank you so much, that actually makes sense. Just a question, shouldn't it save user only data under autobackup and restore when user logs in again, why it is restoring my test data for all the users
– Ali
Nov 18 '18 at 12:36
@aliusman You're wrong. It does not restoring test data for all your users, your device and the device google account takes backup of last data on this device. It's not depend on your data and application state, it depends on your device and google account.
– beigirad
Nov 18 '18 at 12:43
Ok let me have another look into it, that was the first complaint I received from almost all my alpha users that they see test data upon login or creating new account until they clear the app storage data and login again to see empty state
– Ali
Nov 18 '18 at 12:45
And the data they see is 3 months old, its not even in live actual database anymore on the server :) this is just crazy
– Ali
Nov 18 '18 at 12:47
That's true. This data does not clear by reinstalling or fresh installing or clear data and so on. You just turn it off.
– beigirad
Nov 18 '18 at 12:49
add a comment |
This featured named Auto Backup
Auto Backup for Apps automatically backs up a user's data from apps that target and run on Android 6.0 (API level 23) or later. Android preserves app data by uploading it to the user's Google Drive—where it's protected by the user's Google Account credentials.
for disabling AutoBackup, apply this changes in your application Manifest:
<manifest ... >
...
<application android:allowBackup="false" ... >
...
</application>
answered Nov 18 '18 at 12:32
beigiradbeigirad
18510
This featured named Auto Backup
Auto Backup for Apps automatically backs up a user's data from apps that target and run on Android 6.0 (API level 23) or later. Android preserves app data by uploading it to the user's Google Drive—where it's protected by the user's Google Account credentials.
for disabling AutoBackup, apply this changes in your application Manifest:
<manifest ... >
...
<application android:allowBackup="false" ... >
...
</application>
answered Nov 18 '18 at 12:32
beigiradbeigirad
18510
answered Nov 18 '18 at 12:32
beigiradbeigirad
18510
answered Nov 18 '18 at 12:32
beigiradbeigirad
18510
answered Nov 18 '18 at 12:32
beigiradbeigirad
18510
18510
Thank you so much, that actually makes sense. Just a question, shouldn't it save user only data under autobackup and restore when user logs in again, why it is restoring my test data for all the users
– Ali
Nov 18 '18 at 12:36
@aliusman You're wrong. It does not restoring test data for all your users, your device and the device google account takes backup of last data on this device. It's not depend on your data and application state, it depends on your device and google account.
– beigirad
Nov 18 '18 at 12:43
Ok let me have another look into it, that was the first complaint I received from almost all my alpha users that they see test data upon login or creating new account until they clear the app storage data and login again to see empty state
– Ali
Nov 18 '18 at 12:45
And the data they see is 3 months old, its not even in live actual database anymore on the server :) this is just crazy
– Ali
Nov 18 '18 at 12:47
That's true. This data does not clear by reinstalling or fresh installing or clear data and so on. You just turn it off.
– beigirad
Nov 18 '18 at 12:49
add a comment |
Thank you so much, that actually makes sense. Just a question, shouldn't it save user only data under autobackup and restore when user logs in again, why it is restoring my test data for all the users
– Ali
Nov 18 '18 at 12:36
@aliusman You're wrong. It does not restoring test data for all your users, your device and the device google account takes backup of last data on this device. It's not depend on your data and application state, it depends on your device and google account.
– beigirad
Nov 18 '18 at 12:43
Ok let me have another look into it, that was the first complaint I received from almost all my alpha users that they see test data upon login or creating new account until they clear the app storage data and login again to see empty state
– Ali
Nov 18 '18 at 12:45
And the data they see is 3 months old, its not even in live actual database anymore on the server :) this is just crazy
– Ali
Nov 18 '18 at 12:47
That's true. This data does not clear by reinstalling or fresh installing or clear data and so on. You just turn it off.
– beigirad
Nov 18 '18 at 12:49
Thank you so much, that actually makes sense. Just a question, shouldn't it save user only data under autobackup and restore when user logs in again, why it is restoring my test data for all the users
– Ali
Nov 18 '18 at 12:36
Thank you so much, that actually makes sense. Just a question, shouldn't it save user only data under autobackup and restore when user logs in again, why it is restoring my test data for all the users
– Ali
Nov 18 '18 at 12:36
@aliusman You're wrong. It does not restoring test data for all your users, your device and the device google account takes backup of last data on this device. It's not depend on your data and application state, it depends on your device and google account.
– beigirad
Nov 18 '18 at 12:43
@aliusman You're wrong. It does not restoring test data for all your users, your device and the device google account takes backup of last data on this device. It's not depend on your data and application state, it depends on your device and google account.
– beigirad
Nov 18 '18 at 12:43
Ok let me have another look into it, that was the first complaint I received from almost all my alpha users that they see test data upon login or creating new account until they clear the app storage data and login again to see empty state
– Ali
Nov 18 '18 at 12:45
Ok let me have another look into it, that was the first complaint I received from almost all my alpha users that they see test data upon login or creating new account until they clear the app storage data and login again to see empty state
– Ali
Nov 18 '18 at 12:45
And the data they see is 3 months old, its not even in live actual database anymore on the server :) this is just crazy
– Ali
Nov 18 '18 at 12:47
And the data they see is 3 months old, its not even in live actual database anymore on the server :) this is just crazy
– Ali
Nov 18 '18 at 12:47
That's true. This data does not clear by reinstalling or fresh installing or clear data and so on. You just turn it off.
– beigirad
Nov 18 '18 at 12:49
That's true. This data does not clear by reinstalling or fresh installing or clear data and so on. You just turn it off.
– beigirad
Nov 18 '18 at 12:49
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%2f53360748%2fapk-carrying-old-data%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
What database did you use?
– tm13
Nov 18 '18 at 12:24
Azure mobile services database, it's sqllite
– Ali
Nov 18 '18 at 12:25
You should check new user's entered data with the data saved in database. If they are not the same, you should database. Did you do like this?
– tm13
Nov 18 '18 at 12:27
User only gets the data as per their user ID, I have all the custom auth and everything setup. Even if it's a new user, the initial data they see is my test data I saved 3 months ago. Upon clear the app storage data when they log in again, it all works fine... This led me to a conclusion that some how the apk is carrying the sqllite database with it in which I stored some test data (3 months ago)
– Ali
Nov 18 '18 at 12:30