File I/O Error. Please check permssions - Android Plus

File I/O Error. Please check permssions - Android Plus

When I am attempting to update the version of a package in a profile and apply it to an Android phone, I am constantly receiving this error message no matter what I do. It is not a separate package, but simply a newer version of the same package.

This error occurs whether or not I have Google Play Protect enabled. I have also tried uninstalling the app completely from the device and the same error still occurs.

I am running MC version 15.3 and the devices in question are running Android OS 6 - 10 given the device.

Does anyone have any suggestions as to what I can do for determining the root cause of this issue?

10 Answers

Order By:   Standard | Newest | Votes
Matt Dermody | posted this 16 August 2021

It is a new version of the same Package containing what? An APK or a file or something else? If it is a new version of an existing installed APK then you need to ensure that the new APK has the same compile signature and that its version has been incremented at compile time to be higher than the current APK version. 

  • 0
  • 1
Evan | posted this 16 August 2021

Matt,

You are correct. This is simply an updated APK that I'm trying to push through this package. Seeing as this is an in house application, I would have to check with my developers to confirm that information about the compile signature and the version at compile time.

Would there be any error message in the logs that would indicate that the compile signature is the problem?

  • 0
  • 0
Evan | posted this 17 August 2021

Matt,

I had a chance to check with our development team on the compile signature and version at compile time, and he does not see any difference in previous app versions and our current version that I am trying to update to. What else can I check for to determine the root cause of this issue?

  • 0
  • 0
Marcus Breitenthaler | posted this 18 August 2021

Hi Evan,

 

i can readjust you error Message.

When a Software is installed and i try to Downgrade the App.

 

Could it be that the Version Number is not Higher then the installed one ?

Message:

Package "Test" version 4.0.1.599 failed to install. File IO error on device. Check Storage/Permissions.

  • 0
  • 0
Evan | posted this 18 August 2021

That is not the case. The version number I am attempting to upgrade to is higher than than the one the devices currently are running.

  • 0
  • 0
Marcus Breitenthaler | posted this 18 August 2021

Can you enter the Currenty Version number and the New Version number ?

 

Is this happen only on a specific OS Version.

What i mean what API Level has the Apk file ?

 

  • 0
  • 0
Evan | posted this 19 August 2021

I'm not sure I understand your question Marcus

Can anyone tell me where I can find this "compile signature" so that my developers can compare values between versions? That would be really helpful.

  • 0
  • 0
Matt Dermody | posted this 19 August 2021

Compile signature refers to how the app was signed. Did they use the same machine and certificate to sign the app between the different versions?

  • 0
  • 0
Robert Moore | posted this 20 August 2021

Evan, I am curious to know if you are using package studio to first package the application and then upload it into MobiControl or are you uploading the APK directly to MobiControl?

I have found that I have a similar File I/O error when I direct upload the APK files to MobiControl but if I wrap them into a package with package studio then I don't get the error. This error happens for me on fresh installs and on upgrades of a particular APK. I do have an open case with Soti to look into my issue in more detail.

  • 0
  • 0
Evan | posted this 01 September 2021

Turns out the solution to this one was that the developer along the way had dropped the Android version number from 23 to 21 in his build. When he changed it back to 23, I was able to deploy the app successfully.

 

I found this out by trying to install the app while monitoring the activity in Android Studio on my local PC, and the error message was generated which I was able to give to my developer for a solution.

  • 0
  • 0

Give us your feedback
Give us your feedback
Feedback