lazydroid/auto-update-apk-client

Parse Error when attempting update

Closed this issue · 8 comments

I have looked and looked for this issue and I am totally lost

Recently I get updates fail to install

When the update check happens I am notified there is an update . However when you select to get the update I am getting the following on all devices that try

Parse Error
There was a problem while parsing the package..

The logcat shows an entry

E/AutoUpdateApk: /data/data/com.[snippedout].oak/files/http:/www.autoupdateapk.com/fetch/AMIfv94BJqZmpJdzm_igbkkI2bD1hVOZwV7Nv2vtzUH1kL2_Kjwd827_JsJA6UN6YrP6uXi1dgWkL1thO9JcNUFaqBHaB8mLPWf-XldfNczabGWID-1QsDUm/Tr5KnZ5YEGIK9Ur2mbC0MZOpOvJWGlvmjXAostzvlsW-DR3LrBfpsUG6I2gIqi4/oak.apk: open failed: ENOENT (No such file or directory)

It used to work but no longer since a month now

What could be wrong

App is compiled to v5 api

I have the same issue.....have tried for DAYS to contact site owner but no reply.....if I do not hear back soon I will have to unsubscribe....such a shame :(

I also have the same problem. Have been attempting to contact them as well. Nothing at all.
Really unreliable support. Would understand if this project was discontinued but their is no notification or details leading to it. As well as they are still getting paid for this......

I thought i was the only one experiencing this kind of problem, looks like they wont continue to support this.

guess I should "pull down" my apps and cancel my subscription :(

On 2/3/2016 1:32 AM, leenolasco wrote:

I thought i was the only one experiencing this kind of problem, looks
like they wont continue to support this.


Reply to this email directly or view it on GitHub
#71 (comment).

Facing the same issue..

I was up upto 3am last night/morning digging into this.

It appears it might be due to out of date functionality

The notification usage is depreciated, it gets the details that there is a update, and a download link (very long url), if I paste this into a browser it downloads, however it fails to start the download and I suspect this is because its using out dated HTTP functions...

I tried to fix it but was struggling. I even redirected the download to pull from my own web server instead of from autoupdate server and it still failed. It fails because it cannot start a download using the HTTP methods ... the client is no good anymore for newer api.

I am pulling my app and looking to use the google play private options maybe

I am still developing my first application and its not completely ready for full deploy to the client so I have not setup any subscription yet , not going to bother now......

Ok for anyone still using this - it seems like it might be a permissions problem.

If you try to execute the file in your apps /files folder, it won't run (even externally) - but move the same file into a public area (say your download folder) and it will now execute.

Ok, to solve it:

Search for all instances in the files of:
context.getFilesDir().getAbsolutePath()

And change to:
Environment.getExternalStoragePublicDirectory(Environment.DIRECTORY_DOWNLOADS)

This will now use the downloads folder for the download (file gets deleted after)

Also need to edit the checkUpdateTask function.

Change:
FileOutputStream out = context.openFileOutput( fname, Context.MODE_WORLD_READABLE);

to:
FileOutputStream out = new FileOutputStream(Environment.getExternalStoragePublicDirectory(Environment.DIRECTORY_DOWNLOADS) + "/" + fname);

And you're done. Should work fine now :)