As the previous thread filled up, here is part 2 of the The Unarchiver thread.
It is much better to post bugs on the bug tracker, rather than in this thread! Anything posted on the bug tracker has much less chance of being forgotten by me!
So, post bugs here: http://code.google.com/p/theunarchiver/issues/list
Also, remember that if you post a bug about a file that is not work, you must also post the file itself, or else there is nothing I can do about it!
I can't unzip applications and run them using your utility. One high profile example is the Spotify application, which is downloaded as a zip file. I unzipped it using the latest version of The Unarchiver that I downloaded from the App Store, and subsequently could not run it. The application tries to run, and you can see that by an icon opening in the dock and jumping up and down, but when you click on that icon, it disappears. I am running OS X Lion on a MacbookPro5,3 with all updates installed.
I see that other people have mentioned this issue in the past few weeks, and I am asking that you please address this problem, as the Apple Archive Utility does not share this difficulty.
Also, I might add that it is easier for me to uninstall your application and use the Apple Archive Utility, than it is to move everything I need to unzip using your program to the /Users/ or /Volumes/ directories to bypass sandboxing, or to download an out-of-date version of your application through Google Code that will only continue to degrade as more updates are released to OS X Lion. That is a terribly user unfriendly suggestion. You might as well change your icon to duct tape if you're going to suggest users implement your application like that.
Anyway, I don't mean to overtly bash because I really like how minimal this program is designed, and I have used it for many months. That said, I didn't like how you responded to the user reports above, and I hope you can correct this issue before you lose any more of your user base besides just myself.
@128 !Waha.06x36
The issue is that The Unarchiver will not uncompress the .zip file for the specific file (when I posted the comment, the file I attached was for the MacUpdate file "Anti Flashback Trojan" (URL http://www.macupdate.com/app/mac/42571/anti-flashback-trojan); uncompressing it left the application corrupt and unable to launch. Using Apple's Archive Utility (v10.7.1) to uncompress the file resulted in a working application being extracted from the .zip file. I repeated this with The Unarchiver on a separate OS X instance and on my wife's Mac mini and all have the same issue with the same file. I wrote about the issue as well in my review of The Unarchiver on MAS.
Does it work with the legacy version?
Hello, just adding my experience here..
Recently I've been experiencing strange behaviour - Applications unzipped (using The Unarchiver, although I didn't realize it first) are unable to launch. They will just bounce in the dock. These are files unzipped in one of my User directories, usually Downloads.
Following some searching online, I've finally found out that this happens with The Unarchiver but works with files unzipped with the built-in utility. This happens on either of the v3.1 direct download or Mac App Store versions.
BUT... following msg #133 above, I tried the downloaded v3.1.1 legacy version and everything seems to work fine again. Apps are unzipped using The Unarchiver and they launch!
I'm glad the legacy version exists, but I hope you can fix the main Mac App Store version to work as expected. The cause of the no-launch is not apparent at first, so it'll cause a lot of grief. :)
It's an OS X bug, and it's triggered by disabling quarantine.
3.2 will have a workaround for it, but it's not perfect. Apple needs to fix this before it'll work perfectly.
Well, I just installed Ubuntu 12.04, and apparently unar and lsar are now packaged. So on these, you can just do sudo apt-get install unar to get them now.
It's still stuck at 0.99, though, but hopefully it'll get updated at some point. I should get 1.1 done too...
Many thanks for PPC support, and Legacy Version w/o sandboxing.
If I download the source code for the command line tools, version 1.0, there seems to be no way to build a PPC version of them or even a Universal Binary version. I see no makefile in there other than makefile.linux. How can I compile a PPC compatible version of lsar/unar v. 1.0?
1.0 is old. Use the latest The Unarchiver source archive instead, it contains everything.
Well, Apple finally let 3.2 through review. Changes this time are:
Most importantly, this should now hopefully fix extracted apps being broken. Hopefully. Let's see if Apple doesn't manage to mess it up again.
PowerBook G3 Pismo 500 MHz
10.4.11
TheUnarchiver3.1.1_legacy.zip
This is working well.
TheUnarchiver3.2_legacy.zip
This is crashing, because it needs a G4.
$file The\ Unarchiver
The Unarchiver: Mach-O universal binary with 2 architectures
The Unarchiver (for architecture i386): Mach-O executable i386
The Unarchiver (for architecture ppc7400): Mach-O executable ppc
Is a G4 now the minimum requirement?
Bill
It is probably due to the default settings of gcc 4.2. If you or anyone else can figure out what options to give gcc to build correctly for G3, I can fairly easily add those.
I can't do much directly though as I have no hardware to test on, so I'll need help with this.
I was glad to see that 3.2 release notes claim that it fixes the open-the-extracted-folder setting. Don't know if this was other people's problem, but for me, it was opening the folder that the extracted folder was IN, but it was not highlighting the folder that had just been extracted.
Now it opens the folder that was extracted; however, it forces it to open in the Finder, instead of my default file browser, which is Path Finder. This is not a huge issue, and I know it's a severe edge case, and I know the 3.2 fix probably can't work any other way. But if there's some way to fix this without too much trouble, I would love to see it.
Thanks for your time, and for the app itself.
You're probably going to have to wait until Apple fixes a bug related to this. Currently, I have to use AppleScript to send a message to open the folder, rather than just use the provided API call, because that call is broken. That means I have to send it to a specific application, which currently is the Finder. I'm not sure how to find out if somebody is using an alternate one.
Once Apple fixes this one I hope I can switch back to the old method which works better.
Okay, I just read that you fixed the issue with unzipping Apps...
I was going crazy about it... I tried downloading Cyberduck and MacGDBp and they couldn't run.
I noticed though that The Archive Browser doesn't have this issue... it worked fine!
1.1 should have it, but I got 1.2 out earlier with a workaround.
I see .sitx listed among the supported formats, but when I tried using 3.2 to open an encrypted .sitx, I got the "File is not fully supported" error.
Is this because of the encryption, or a more basic problem?
Encryption is not supported, at the moment.
Question about programm in Mac OS.
Why after an archiving of one file (folder) on some serial/split archives, in a format *.zip.001 and so on, these archives don't unarchived on double click of a mouse and on them there is no program icon of The Unarchiver?
i'm using version 3.2 of The Unarchiver.
There is an inversion in translation
In Preferences panel under extraction tab, for the option "Create a new folder for the extracted files".
"Never" should be "Jamais", but translated as "Toujours"
"Always" should be "Toujours", but translated as "Jamais"
Please file an issue on the bug tracker, so I'll remember to fix this for the next release.
No, I do not understand it.
>>152
Could you please add file extension .zip.001 (and so on) to defaults?
.001 is already a defined file type. Launch Service is incredibly buggy, though, and may be overriding it if you have some other program installed with a conflicting declaration.
There is a concern with 7zip archives with password (generated by 7zip 64bit / Windows se7ven). The Unarchiver does not display the fields for typing the password and told me that my file is corrupted. That archive for example. The password is "password".
http://bayfiles.com/file/aHjr/tZpgTZ/lake.7z
I use The unarchiver 3.2 when I try to extract an archive with a lot of part and one of it there isn't, the unarchiver display the error message about the last file.
For example with winrar if I try to extract an archive with 10 parts if the part5 miss WinRar show this missing and invite the user to add this part. Can you add this function?
Sorry for the writhed explanation.
Hi. I'm using The Unarchiver 3.2
When I'm batch extracting a set of files, for example choosing to open part01.rar in a set, I can only run a maximum of 5 in each batch. Any subsequent files receive an error message with 'crunching' Is there anyway to increase the number in the batch? -thanks
Can you be more specific? There should be no particular limitations.
WaHa can you answer to 158 question please?
Hi, Using The Unarchiver 3.2 and after Mountain Lion it says:
"This folder is not writable, so the archive can not be extracted here"
https://www.dropbox.com/s/b04yxfk4icr8507/Unarchiver%20Error.jpg
Love the app!
Probably the sandbox preventing it. Only /Users/ and /Volumes/ can be written. There does not seem to be any way around this.
The Unarchiver will not extract a zipped read only folder containing a read only file. Expander has no problems with this.
Please add an icon for .z02 .z03 etc. currently the app only shows the icon for .zip and .z01. The rest stays the generic empty page icon.
Great app.
Is there a log file generated by The Unarchiver? Any other way to communicate with The Unarchiver (possibly via command line)?
I try to extract an .ace archive but Unarchiver just closes: no extracted files, no error and warnings.
The Unarchiver does sometimes send log messages to the system log, so use Console.app to check that. Also, you can use the unar and lsar command-line tools, which should be on the Google Code download page.
Only old ACE files are supported, though, so that is probably your problem there.
It is not possible to directly recognize the content of .z02 and .z03 and such files, so giving them an icon would only let you click them and have The Unarchiver tell you it couldn't open them.
I use The unarchiver 3.2 when I try to extract an archive with a lot of part and one of it there isn't, the unarchiver display the error message about the last file.
For example with winrar if I try to extract an archive with 10 parts if the part5 miss WinRar show this missing and invite the user to add this part. Can you add this function?
Sorry for the writhed explanation.
Well, after the longest time ever waiting to get approved, The Unarchiver 3.3 is finally released. There aren't that many changes, but Apple changed their sandboxing rules in the meanwhile which caused on end of troubles.
Download links:
Changes are:
unar and lsar 1.2 were also released:
OS X binaries: http://theunarchiver.googlecode.com/files/unar1.2.zip
Older OS X binaries: http://theunarchiver.googlecode.com/files/unar1.2_legacy.zip
Windows binaries: http://theunarchiver.googlecode.com/files/unar1.2_win.zip
Source: http://theunarchiver.googlecode.com/files/unar1.2_src.zip
The changes are (mostly the same as in The Unarchiver 3.3 above):
Made a quick silent update of the 3.3 legacy version: Old OS X versions were failing to load the new icon with larger bitmaps, so I reverted to the old icon for the legacy version.
If you already got the old version and it caused problems, re-download. If the icon looks all right for you, there's no need to re-download.
Is the only difference between The Unarchiver 3.3 and 3.3Legacy the sandboxing? I still have 3.2, but don't want to futz with the App Store restrictions.
The differences are that legacy is not sandboxed, uses older APIs in some cases (that should still work in all versions OS X as far as I know), is built with an older version of gcc (which might mean it's a little slower, but I have not tested) and uses the older icon without the most gigantic image.
There is a bug in Unarchiver 3.3-legacy that wasn't there in 3.2-legacy. Specifically, the bug is in the un-tarring of tar archives. The Unarchiver adds underscores to the very end of some (but not all) of the filenames present in the original tar archive.
The only thing about these filenames that I can see is common to all the affected ones is that they have either a space or an underscore or a hyphen in them. This not to say that The Unarchiver messes up the filenames of all files in the tar archive whose names contain one of those characters. But it does mess up some of them. No such appending of underscores happens when I untar using the tar binary on the commandline.
More info: I tried simply listing the tar archive's contents with lsar (version 1.2). This revealed that the filenames that had underscores added by The Unarchiver are displayed by lsar as ending with "^@". Needless to say, the filenames don't actually end with "^@", and "tar -tf" does not claim that they end with "^@".
There is a bug in Unarchiver 3.3-legacy that wasn't there in 3.2-legacy. Specifically, the bug is in the un-tarring of tar archives. The Unarchiver adds underscores to the very end of some (but not all) of the filenames present in the original tar archive.
The only thing about these filenames that I can see is common to all the affected ones is that they have either a space or an underscore or a hyphen in them. This not to say that The Unarchiver messes up the filenames of all files in the tar archive whose names contain one of those characters. But it does mess up some of them. No such appending of underscores happens when I untar using the tar binary on the commandline.
More info: I tried simply listing the tar archive's contents with lsar (version 1.2). This revealed that the filenames that had underscores added by The Unarchiver are displayed by lsar as ending with "^@". Needless to say, the filenames don't actually end with "^@", and "tar -tf" does not claim that they end with "^@".
Since updating to The Unarchiver 3.3 (App Store version) I've been getting a number of sandboxing errors. Usually it seems to happen when I open multiple ZIP files at once.
Full sandboxing report (my username is omitted but the report is otherwise unchanged): http://pastebin.com/qaCieqW2
It will work if you just drop the files directly on The Unarchiver.
Can you be more specific in what order you do things, and when what happens, including any file dialogs The Unarchiver might use?
Actually, this is probably fixed now. Just wait for 3.4.
The Unarchiver 3.3 (App Store version) causes tons of log spam:
Sep 24 10:38:35 Hostname sandboxd[9373] ([9363]): The Unarchiver(9363) deny appleevent-send com.apple.finder
Sep 24 10:38:35 Hostname coreservicesd[28]: pid=9363 not allowed to send AppleEvents to com.apple.finder
Sep 24 10:38:35: --- last message repeated 487 times ---
Sep 24 10:38:35 Hostname coreservicesd[28]: *** process 28 exceeded 500 log message per second limit - remaining messages this second discarded ***
Sep 24 10:38:36 Hostname coreservicesd[28]: pid=9363 not allowed to send AppleEvents to com.apple.finder
Sep 24 10:38:36: --- last message repeated 499 times ---
Sep 24 10:38:36 Hostname coreservicesd[28]: *** process 28 exceeded 500 log message per second limit - remaining messages this second discarded ***
Sep 24 10:38:37 Hostname coreservicesd[28]: pid=9363 not allowed to send AppleEvents to com.apple.finder
Sep 24 10:38:37: --- last message repeated 499 times ---
...and on and on. This came while extracting a buildroot.tar.bz2 archive.
It should only happen on files that have Spotlight comments, because Apple refuses to let anybody change those from App Store apps, apparently.
If it happens on any other files, that's a bug.
>>183
No Spotlight comments. You can try to reproduce with http://buildroot.net/downloads/buildroot-2012.08.tar.bz2
Actually, those files all have comments. It's not clear why, and it's just a big hexadecimal string, but everything is working as expected. This shouldn't happen on regular files.
I might try to disable the comment-setting code in the sandbox, though, we'll see.
hi all,
i've installed this program one week ago and after 2 hours my mac freezed (the mouse icon stopped moving and all the system was blocked), i've OS X 10.2, could it be caused from this program?? =(
i also bring my mac to an Apple assistance point but after a week of testing they say that could be an app recently installed...
anyone else had this problem??
thank you
Since updating to Mountain Lion, I have two new problems with this.
One, on every extraction, the preferences panel opens and I have to close it.
Two, if I am extracting more than one zip file at a time, I get an error on the second and subsequent files. "Could not extrat the file "{file name}" from the archive "{archive name}": Could not create the folder" This is perhaps related to Dar's sandboxing report above.
If I extract them separately, everything goes as it should
Somebody had some similar problem with Xee, and that turned out to be caused by "Default-Folder X". Are you using that?
The second is fixed in 3.4, but Apple are dragging their feet.
Yes, adding The Unarchiver to the Default Folder exclude list solves the preference window problem.
Version 3.4 has been released at long last, after Apple dragged their feet more than ever before about getting it approved. Here are the changes:
That should fix some fairly annoying issues that 3.3 had. There is also now a fancy new landing page for http://unarchiver.c3.cx/.
(Make sure to also check out Archives for iOS!)
Also, v1.3 of unar and lsar have been released, but only contain the backend changes from The Unarchiver, which is:
Is there somewhere in the settings I can change the language? I'm swedish and for some reason I got the app in norwegian...
Change it in the OS X preferences. There is a list somewhere in there of preferred languages. OS X picks the language for apps according to that list.
Quick question: I'm using 3.4 downloaded from this site (not from App Store) and I notice that The U. freezes at the end when it's done extracting. It just sits there for like 3-5 seconds. Any idea why this happens to me?
Not really. Does it print anything to Console.app?
yes, it printed this in console:
11/1/12 9:44:57.460 AM sandboxd: ([67903]) The Unarchiver(67903) deny file-issue-extension /Users/xxx/Downloads/A History.pdf
11/1/12 9:44:57.461 AM The Unarchiver: __CFPasteboardIssueSandboxExtensionForPath: error for [/Users/xxx/Downloads/A History.pdf]
Here is the crash? log:
Thanks for looking into this.
>>196
replying to myself :)
I've gone back to v3.2. v3.2 seems to be the last version that doesn't crash on my machine (MBP running Lion) due to sandboxing issue.
v3.3 also crashes:
11/1/12 10:03:02.106 PM sandboxd: ([74839]) The Unarchiver(74839) deny file-issue-extension /Users/xxx/Downloads/The Unarchiver.app
11/1/12 10:03:02.108 PM The Unarchiver: __CFPasteboardIssueSandboxExtensionForPath: error for [/Users/xxx/Downloads/The Unarchiver.app]
Well, it's clearly a sandbox error, so if you grab the legacy version that should fix it.
It's a bit mysterious why it happens, though. Is there something special about your machine? What version of OS X?
>>198
I don't think it's anything special at all. I run latest Lion.. 10.7.5. I haven't upgraded to ML for a multitude of reasons.. main one being that I'm in the middle of a project and don't want to deal with issues that might pop up due to OS change. :)
But yeah, The U v3.3+ crashes every time I extract something but the files are extracted just fine. It is annoying to have that 4sec delay when the process is finished. Also, OS X doesn't pop up a crash dialog which is also weird.
Do you have it set to open extracted files, by the way? If so, try changing that.
When extracting RAR-files, those that contain a single file but are split in multiple RAR-files, after selecting where to extract the file I get another dialog saying that the Mac OS X sandbox is blocking access and I need to click Search to continue.
This is obviously due the the sandbox. But if I understand the sandbox correctly it should be possible to say that a given file has a dependency on one or several other files and the user doesn't need to select those. For example, a text document may contain an image but the document only contains a reference to the actual image. This is how TextEdit works with the RTF format.
I think this is called "Related item", there's a video from WWDC 2012, "The OS X App Sandbox", that talks about this problem. It's around 33:30 minutes into the video clip.
I can't find any documentation about that, but if it is actually document-scoped bookmarks, that doesn't help because those have to be created after you have gained access to a file through some other means. It only works for granting access to related files in documents you have created yourself.
Besides, what The Unarchiver actually needs to do is to scan through all the files in the same directory as the archive to find those that are parts of the archive.
This video clip mentions both "document-scoped bookmarks" and "related items". They seem similar but as I understand it they're not the same feature/concept.
Except for the TextEdit and RTF format they also mention an other example with a movie file and a separate related subtitle.
The API they mention is NSFilePresenter and the method "primaryPresentedItemURL".
I don't know if these API can help in this case, but I think it's worth looking into. The behavior of The Unarchiver might be more dynamic then this API allows.
If this won't work here's another idea that will make it a bit more user friendly. When extracting files The Unarchiver will remember the last location where a file was extracted to. But if the last file I extracted was a RAR file, as explained above, The Unarchiver will instead remember the last path where I pressed "Search", not where it was extracted to. Can these to location be remembered separately?
Hello Unarchiver-Team,
I love The Unarchiver. But in my eyes the sandboxed version sucks. Big time. I have to confirm every time I unpack a file, and this annoys the hell out of me. Please go back to the un-sandboxed version, or provide one in parallel. I will probably change because of this, I want extraction, here, now - and not extraction, here, YES,REALLY, now.
Otherwise - keep up the awesome work.
Cheers, Axel.
Well, I wrote some quick test code, and apparently it does nothing at all except tell me it won't let me have access to any file, ever.
Nobody on the internet seems to have ever used it, either, so I have no idea if it actually possible to do anything useful whatsoever with it.
Since one of the latest updates the unarchiver doesn't automatically open the extracted folder anymore. I unchecked and rechecked this function but nothing helps, also re-installed...
This is probably an OS X sandbox bug. Apple won't let me use the workaround for it. Try updating your OS and hope they fixed it, or use the legacy version.
Hmm, I see. What about my other suggestion:
"When extracting files The Unarchiver will remember the last location where a file was extracted to. But if the last file I extracted was a RAR file, as explained above, The Unarchiver will instead remember the last path where I pressed "Search", not where it was extracted to. Can these to location be remembered separately?"
It can probably be done, but would be a bit messy. Either way, file an issue for it on the bug tracker or else I will forget about it.
Hi! i've just found some weird error/bug in unarchiver 3.3
i don't know how to explian or what ocorred, but unarchiver repeatedly corrupted the contents of the Eclipse tar.gz file from the website. It extracted and deleted the original file, as standard but i always ended up with a damaged folder for the eclipse program. I did the shasum of the original tar.gz and it was correct, but i always ended up with the same problem. finally discovered this thread (https://bugs.eclipse.org/bugs/show_bug.cgi?id=297993#c6 ) and tried to untar the same tar.gz file with the mac default archive utility, and everything was ok then!
oh, also tried downloading several versions of eclipse IDE before understanding my troubles but it happened the same with every version of it!
That's probably a bug that was fixed in 3.4 already.
3.5 has been released! Changes are:
And as usual, unar and lsar have also been bumped to 1.4. Mostly they share the same changes, plus a few bugfixes:
Does not Launch After Update!
Thanks for this tiny but reliable powerful app. But after the update to v3.5 it just does not launch. I am using MacBook Pro OS X 10.7.4, once The Unarchiver was working properly, under the same operating system.
Gives the messsage:
The Unarchiver cannot be opened because of a problem.
Check with the developer to make sure The Unarchiver works with this version of Mac OS X. You may need to reinstall the application. Be sure to install any available updates for the application and Mac OS X.
Click Report to see more detailed information and send a report to Apple.
Ditto on the crash after updating to 3.5
Running 10.6.8
Crash log can be found here: http://pastebin.com/EHq9qzpK
Double ditto on the crash with with 3.5.
Running 10.7.5
There seems to be some kind of really terrible bug in Xcode which causes newly compiled applications to fail on 10.6 and 10.7, but not 10.8. I am investigating how to get around it.
3.5.1 is now available, which should fix the bug.
http://theunarchiver.googlecode.com/files/TheUnarchiver3.5.1.zip
Trying to get Apple to hurry up and approve it on the app store too.
I can confirm 3.5.1 fixes the problem. Thanks for the quick fix!
Running The Unarchiver 3.5.1 legacy on PowerMac G5, 10.5.8, I get a consistent crash:
EXC_BAD_ACCESS (SIGSEGV)
KERN_INVALID_ADDRESS at 0x000000004300000c
The archive I used to cause the above crash was "TheUnarchiver3.5.1_legacy.zip"
I need a full crash dump to look into that.
Hi! I'm using 10.8.2, and it does not work properly, it seems like something is misconfigured.
App does not crash, but before, when I double-clicked a .zip file, it was automatically extracted. Now, when I double-click the zip file, I get the Preferences screen, as if the filename had not been passed to the app.
I reinstalled both from the App Store and from the last link you provided (#219) but nothing changed.
Thanks!
Are you using Default Folder X?
No, I don't use that or any other Finder helper tool that I'm aware of. Any test I can do to help?
Same issue here. Only the Prefences dialog. OS X 10.8.2
Version 3.5 and 3.5.1
Deleting the prefences files resolved the issue
As said by >>228, I deleted Preferences/cx.* but there was no luck. And cx.* are not generated again :-?
Sandboxed apps have their preferences inside their containers in ~/Library/Containers.
