Test update installation

Solar2D General Questions/Discussion
#1

Hello,

I put my app on the store. My customers have reported problems, so I’m working to fix them.

I did upgrade but I did not put it in the store(google play). 

The problem is this: I tried to install this update on several android devices. On some models the update is installed, on the other hand it seems impossible (intall only if I uninstall the previous version downloaded from the store).

Would i know if it is normal? And especially if these issues will also occur when I put the new version in the store

#2

I had trouble understanding the question, but it sounds like you said.

  1. I have some devices where the old version of my app was installed from the store.

  2. I built a new version of the app. (No mention of what keystore you used… debug or production)

  3. I tried to install the app on the devices from step 1 above (no mention of how you did this: adb, other?)

  4. I couldn’t install on some devices unless I first removed the original copy of the app.

While, I’d say we need more details, this sound normal to me.

If you have tried to install a new build of your app on a device where it exists already, these things can happen:

A. If the builds have different package IDs, you’ll end up with two copies of the app on your device.

B. If the IDs match, but you used a different keystore, you may be forced to delete the existing one first.  ADB can do this 

adb install -r theApp.apk

However, if you have a mismatch and dates are goofy… or in some other case…

C.  In some cases however, you will simply have to delete the original app yourself before trying to re-install.

Having said all that, the real question is…

If you build your app (using the same keystore as was used for the original) and you upload that to the store, will your users have to manually delete their installed app first?

The answer is, “No.”   Google Play won’t even let you upload the app if it doesn’t fit the right criteria to allow an easy replace on update.

#3

"If you build your app (using the same keystore as was used for the original) and you upload that to the store, will your users have to manually delete their installed app first?

 

The answer is, “No.”   Google Play won’t even let you upload the app if it doesn’t fit the right criteria to allow an easy replace on update."

 

That’s what I was hoping for.

 

 

But I would like to be clearer:

 

  1. I have some devices where the old version of my app was installed from the store.

 

  1. I built a new version of the app. (With the same keystore of the version in the store, But new code version as per manual)

 

  1. I tried installing the version of point 2 on the devices in point 1.

 

  1. I could not install on some devices unless I first removed the original copy of the app.

 

Thank you for your understanding. I apologize if I did wrong the question with my English

#4

Sure thing.

How did you try to install?  Did you use adb or some other method?

Also, is there any change the device was almost full?  Sometimes, the ADB -r install will fail if the device is almost full.  It isn’t smart enough to calculate the space requirements.

#5

I apologize for the delay I had problems…

I did not use ADB because I thought it was less “realistic”. 

I simply copied an APK into the phone and tried to install it.

#6

I had trouble understanding the question, but it sounds like you said.

  1. I have some devices where the old version of my app was installed from the store.

  2. I built a new version of the app. (No mention of what keystore you used… debug or production)

  3. I tried to install the app on the devices from step 1 above (no mention of how you did this: adb, other?)

  4. I couldn’t install on some devices unless I first removed the original copy of the app.

While, I’d say we need more details, this sound normal to me.

If you have tried to install a new build of your app on a device where it exists already, these things can happen:

A. If the builds have different package IDs, you’ll end up with two copies of the app on your device.

B. If the IDs match, but you used a different keystore, you may be forced to delete the existing one first.  ADB can do this 

adb install -r theApp.apk

However, if you have a mismatch and dates are goofy… or in some other case…

C.  In some cases however, you will simply have to delete the original app yourself before trying to re-install.

Having said all that, the real question is…

If you build your app (using the same keystore as was used for the original) and you upload that to the store, will your users have to manually delete their installed app first?

The answer is, “No.”   Google Play won’t even let you upload the app if it doesn’t fit the right criteria to allow an easy replace on update.

#7

"If you build your app (using the same keystore as was used for the original) and you upload that to the store, will your users have to manually delete their installed app first?

 

The answer is, “No.”   Google Play won’t even let you upload the app if it doesn’t fit the right criteria to allow an easy replace on update."

 

That’s what I was hoping for.

 

 

But I would like to be clearer:

 

  1. I have some devices where the old version of my app was installed from the store.

 

  1. I built a new version of the app. (With the same keystore of the version in the store, But new code version as per manual)

 

  1. I tried installing the version of point 2 on the devices in point 1.

 

  1. I could not install on some devices unless I first removed the original copy of the app.

 

Thank you for your understanding. I apologize if I did wrong the question with my English

#8

Sure thing.

How did you try to install?  Did you use adb or some other method?

Also, is there any change the device was almost full?  Sometimes, the ADB -r install will fail if the device is almost full.  It isn’t smart enough to calculate the space requirements.

#9

I apologize for the delay I had problems…

I did not use ADB because I thought it was less “realistic”. 

I simply copied an APK into the phone and tried to install it.