Workaround: copy [whatever].apk to [whatever].zip
cp whatever.apk whatever.zip
Then Archive Manager will work with the .zip version
![enter image description here](https://i.stack.imgur.com/FGYhO.jpg)
I know this question was posted over a year ago, but after running into what looks like the exact same issue I might be able to provide some answers. The most likely cause of this interoperability problem is OneDrive's implementation of the ZIP64 extension, and to be more precise the value of the "total number of disks" field in the "zip64 end of central dir locator". In the OneDrive files, this value is set to 0 (zero), whereas most reader tools expect a value of 1.
For more information here's a detailed write-up I posted on my blog:
https://www.bitsgalore.org/2020/03/11/does-microsoft-onedrive-export-large-ZIP-files-that-are-corrupt
If you're comfortable with a bit of Hex editing, you can provisionally "fix" affected files by changing the first byte of the "total number of disks" field in a hex editor, again see my blog post for details.
UPDATE: partially prompted by my blog post someone has written a Perl script that fixes these files automatically, see this link for more details:
https://unix.stackexchange.com/a/590034
Direct link to the script:
https://github.com/pmqs/Fix-OneDrive-Zip
In addition, this support page from Microsoft says (3rd 'Notes' section from top):
Downloads are subject to the following limits: individual file size limit: 10GB; total zip file size limit: 20GB; total number of files limit: 10,000.
So for a 45 GB directory you might hit these size limits as well.
Best Answer
Install the package
avfs
then execute:Say you have a zip file in
~/Documents/file.zip
, thenYou could also browse the content in Nautilus, but you need to add a trailing
#
character by hand to the path (Ctrl-L to access the address bar).