Hi Christophe,

Before an app update is pushed to production devices, it is important that you test the new app on some devices.

The correct process to update an app via package in this case will be as follows:

1. Open the original package with the older version of the apk in the MobiControl Package Studio

2. Add the new apk and remove the older one from this package

3. Update the package version number to a number higher than your original version number for the package

4. Build the package

5. Now go to your MobiControl web console and switch to the packages tab and add this package. You will notice the package automatically appears under the already existing package but with updated version number

6. Switch to the Profiles tab and Edit the original profile which is pushing this package to the devices

7. When you look at this packages in the profile there will be a small "new (i)" icon next to the Package version

8. Clicking on this icon, a drop down list with the recently added version will appear

9. Select this new version of the package and click Save and Assign.

That should push the new version of the package via the same profile.

Please let me know if you have any questions.

Thanks

If the previous APK was installed onto the devices via SOTI Package then you do not really need the Uninstall APK Preinstall script. In fact, having this script could potentially wipe any app data that you may want to preserve. SOTI should be able to perform an APK update over the previous version if you just update the SOTI package with the new APK. If however the APK was manually installed you may want to include the Uninstall script .

Hello SMOD Soti :)

thanks for your solution , i've try but the installation is always in failed !

I receive this message : Profile " xxxx " version 2 failed to install ...

I have follow exactly what you describe in your last reply:

- open last package studio, delete old apk 

- add new apk (signed) and update the version tag

- add this pcg to mobicontrol console

- go to profile, edit profile, go to tab package , new icon was here => double click select newer version

- save and assign 

- but result is installation failed !

If i delete all profile, make a new package studio with the newer apk and assign to a device install is ok.

How i can try to see what's happen with the install is failed ?

thanks for all

Christophe

Hello matt, 

thanks for our comment that's great.

i'm beginner and i try to find a correct way for to update all our device.

thanks for your time on this forum

Hello all,

i have check some information and try again but every time i have install failed !

i have added on this forum a print screen about the activity log i've seen some error but i can't understand them ...

perhpas you can help about them ?

thanks for all

First forget about updating.  Have you successfully installed the new version to a device that does not have the old version installed?   If that fails also,  your newly created pcg is at least part of the problem.

Hello Raymond chan,

thanks for your reply yes ...if I build a new package add the new version of the apk , and add this package to a profile the status of this new profile is installed ...

All work fine

I'm still block with this issue ..and it's enough urgently ...

Any idea ..

I've check also some information => Apk is well signed => ok , and version is also incremented => ok

thanks for your time

Christophe

How many device brand/model(s) are affected?  Please list them out.

Was the file I/O error found in ALL targeted devices? or just a subset of devices of the same brand/model?

What is your server and agent version and build numbers?

Could you show a screenshot of the packages tab, with your problematic app item selected and its multiple version ID's shown?

Did you include any pre/post install and uninstall script in your pcg?  What about the advanced options selected in your app deployment rule/profile?

Hello again,

actually, i'm just trying to update one device just for to try to find a way for to update all device (700).

actually, we made all by hand => uninstall profile old => add new profile but it's take time of course.

the target device is zebra tc 75 with android 6.0 on all device.

server version is 13.3.0.3454 and agent is on version 13.3.2 build 1014

Yes, i've added a screen shot about the tab package inside the profile.

No, no script are inside the pcg ...

This morning, i have take two old apk made with vs 2015.

Add these two apk inside the package studio, create a profile, add this pcg into the profile.

Install version 1=> result ok => edit profile, change version on drop down list => install v2 => result ok

Perhpas there is a problem when we try to update an apk made with vs 2015 by one build with vs 2017 ?

Sorry i'm a beginner and i'm try to understand all ...

If i build a package with our apk made with vs 2017 the app is well installed...

hm hm, on afternoon i think i will try to update two apk made with vs 2017 and see what's happen ...

thanks for your help raymond, i will update this topic

have a nice day

christophe 

Hello all,

i've try two thing this afternoon.

1 - take 2 apk build with visual studio 2017, create a package, add the first apk, create a profile, assign this profile => install was ok

take the second apk, edit the pcg, delete old apk, add new one, update version tag, update package, edit profile change to newer version => install ..result is fail !

2 - i've downloaded the new client soti in version 13.5 install on my device and try to update the two apk build with vs 2017.

result install fail aslo ...

I've join a print screen (sotiClient135_apk2017) about the activity log ..

I'm lost, nothing found on internet ...

All suggestion or idea are welcome of course ..

Repeat your tests on another Android device brand/model.  If everything is OK,  the problem is likely to be in the firmware of your TC75, or incompatibilities between this firmware version with your current MobiControl server/agent software.   You may try different agent version/build-number to see if things get improved.

Please note that your Zebra device might also have some extra feature enabled with its ZX layer software to protect the apps already deployed, thus creating file I/O error when you try to update the app with newer version.   

I encountered similar problem ("file I/O error" when deploying an app out of 10 in the same package deployment rule with an updated agent and server) for one governmental customer last year.  The problematic devices were from Samsung at that time, though Soti support team and I could not pinpoint from various log  files whether it's the device firmware, the MC device agent, the MC server  or the apk itself that caused the problem. The problem pattern was not consistent with a particular model, a particular agent/firmware version, etc., and were found in less than 40 devices  out of a total of more than 1000 devices of 5-6 different device models.  

Thanks raymond for your idea and for sharing your experience ...

But i can't repeat the test because all our device are zebra tc 75 ...

Yes, i've try to make also this test with the new mobicontrol client v 13 .5 but the result is failed too.

Last test i have made today, with a fresh device (tc 75) on android 7.0 i've try to follow the procedure but every time the same error ...

ZebraApplicationInstallationManager ...updateApplication failed with error code -7

i'm stuck about this ..

 thanks for your help, i'm waiting some news from soti and will see ..

Re-testing with one or two other device model(s) is the quickest way to rule wrong server or pcg/policy settings out.  It won't take more than 10 minutes.   I would do it with any Android phone (even a personal one, which can get unenrolled after 10 minutes) if I were you. 

If the problem stems from your TC75 firmware or ZX settings,  trying a newer, or even the newest,  device agent version won't  help, and you might need to contact Zebra support team instead.

Good morning Raymond,

thanks a lot for the time your take for to reply me :)

Yes, yesterday I have explain the problem I meet when I made a update from our app.

we device to add a script into the package for to uninstall the last apk.

I have test with the script and I can update the app without a problem ...

Now, I will test on several device and see the result ...

yes, I think I try to contact zebra support ...

have a nice day

christophe

You might also check whether "Google Play Protect" has been enabled on your problematic device.   If enabled, it might block your installation.   It may be worth a test to have such option disabled. 

Good morning Raymond, thanks yes google play protect ..is not enabled ...

I think the problem is more deep with perhaps the assemblies in vs 2015 and vs 2017 ...

One of my collegue tell me, that the apk must be signed wit the same machine ..everytime ..

I can understand if we update the app by google store and other store but here we do that with mobicontrol and if I well understand Mobicontrol when it does an UPDATE the client mobicontrol uninstall all and install all IT S NOT AN UPDATE ..it's a clean and install ...

If I found a solution because today I will post a question about zebra I will post the solution here ...

thanks a lot ..

Christophe

If the problem really stems from the fact that your two apk not being signed with the same machine  in your development environment,  Zebra support team won't be able to help you.   The problem is likely to be related to your two version of apk using different certificates/keys to sign the app when creating the apk.

To confirm if that is the real cause,  just install the old version of the apk directly on a test device, then tap on the new version of the apk on the test device to try to upgrade.  If the operation fails,  then your problem does not have anything to do with either MobiControl software or Zebra firmware.  

Hello raymond,

Yes of course i can understand that zebra can't help us if the apk hasn't got the same keystroke for to sign ..

Well, i have take my two apk (one vs 2015 / one vs 2017) , upload to a device

install 1, install 2 => a screen appears and ask me to make an update => i accept => and i receive just a message as this : application no installed !

well, as i can understand it's not a problem with zebra or soti :) 

of course if i take two apk sign with vs 2017 same machine that's work ...

Now, it would be nice if in the activity log of the device a error message with something about the keystroke ...

Ok now i think the problem is resolved because now , in a few days we used everytime the same computer for to have the apk ..

Before, each developer generate the apk and distributed it when the time line is off ...

thanks a lot raymond ..

Do you work for soti ?

You're welcome.

I work part-time for UDS Data Systems in Hong Kong.

hello raymond,

ohhh nice localization, i work in luxembourg

see you next time for another problem :)