As the previous thread filled up, here is part 2 of the The Unarchiver thread.

• The old thread is here: http://wakaba.c3.cx/sup/kareha.pl/1151796773/
• The homepage is here: http://wakaba.c3.cx/s/apps/unarchiver
• The Google Code page is here: http://code.google.com/p/theunarchiver/

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!

It would be great if the tool recognized CP/M .lbr archives with lzh "crunched" members, e.g. a file originally named SRC.Z80 would be contained as SRC.ZZ0. Currently, it extracts the crunched file and leaves it compressed. I have not been able to find a Linux based tool that can subsequently handle it.

>>2

Post an issue and provide test cases.

Also, did you try just running unar on the extracted file?

>>2

Actually, I notice I have at least one testcase already with that kind of files. It seems they unpack just fine if I run unar on them for a second time.

However, you are right that it would be a lot more useful to unpack them automatically. Feel free to file an issue about that, at least, so I don't forget.

The Unarchiver 2.7.1 could not open a ZIP archive which is larger than 4GB.
Could you fix this problem?

I am using Intel Mac OS X 10.6.8.

The ZIP archive is too large to send to you.

I have created another ZIP archive using Mac OS X Finder.
(1) Select '/Developer' folder on my Mac.
(2) Choose 'Compress "Developer"' in the File menu of Finder.
The ZIP file is about 6GB. The Unarchiver could not open the ZIP archive.

>>7

I managed to recreate the problem, and will look into it. Thanks!

>>7

Ok, I found the problem. The Finder does not create valid Zip64 files when it makes files that are bigger than 4GB. I added a workaround to try and read them anyway.

So I've just downloaded the unarchiver and it's asking me for a password before it unzips my files. I have no idea what this might be. Could you help me out?

>>10

Not really. You'll have to ask whoever made the files.

First off,

I just want to say what a great app The Unarchiver is and am so happy to discover's maker to be one and the same of one of my favorite sites, wakaba. I am thoroughly impressed with all your coding endeavors and sing your praise.

I stumbled here actually looking for information about command line functions. I noticed Transmission in its preference with the option to Call script when download completes and was wondering if I could plug in a few lines into Automator and maybe make an .rar detection and .rar extraction type thing with Automator.

>> 9

Thank you!

How is your RAR implementation free? Did you implement the virtual machine from scratch? This confuses me.

>>18

Every part is implemented from scratch, including the virtual machine.

Just downloaded on my iMac running Leopard. Is there an option to JUST "view" the archive files WITHOUT unarchiving it into a folder?? I was hoping your utility had that since the default Mac utility also did the same & I do not always want t a new folder created. Thx in advance.

mine constantly gets to about 99.9% done with unarchiving it and just freezes up completely with everything i download.

Hi there - I had posted this 2 weeks ago but have not seen a response yet. Any help will be appreciated -- << Just downloaded on my iMac running Leopard. Is there an option to JUST "view" the archive files WITHOUT unarchiving it into a folder?? I was hoping your utility had that since the default Mac utility also did the same & I do not always want t a new folder created. Thx in advance. >>

Youre app is awesome. Had nearly ten app or command line tries but always problems with the special characters of a zip file I got from a customer. Took me 3 hours to try and fail again and again. Now it was done in 30 seconds.
Thank you, my friend!

Your doc page mentions command-line versions of the tool (lsar and unar). It would be great to include them, along with man pages, on the App Store download. Even if those are just under the .app wrapper and one needs to find them and link to them, it'd be a good addition.

>>25

I might once they are out of beta (which should be next release), if I can figure out a decent way to do it.

I plan to use The Unarchiver in an application. The lsar program does its work great, it just lists the archive files.

One suggestion: please make both lsar and unar exit with an error code when errors occur during the list/extract operation.

>>27

They should do that already, I think?

>>28
$ unar arch.rar ; echo $?
Extracting arch.rar... Couldn't open archive.
0

They exit with an error message, not an error code.

>>29

What version?

>>30
$ unar -h
unar v0.4 (Oct 19 2011), a tool for extracting the contents of archive files.

>>31

Try the current version in the hg repository.

>>32
The hg repository version does exit with an error code. Thanks.

So, I have been working on a new version for some time now. There aren't all that many visible changes, but as I've made lots of changes to the internals of the code, I've probably introduced some fresh new bugs. Therefore, the version has been bumped to 3.0, so that people can see the scary ".0" and know that there might be a few problems.

To avoid the worst problems, I've made an alpha version available, and would very much like for as many brave people as possible to grab it and try to use it, and report any problems. It should work fine most of the time - I am not aware of any outstanding bugs at the moment - but obviously I alone can not test it under all circumstances. Therefore, please grab it and try it.

http://theunarchiver.googlecode.com/files/TheUnarchiver3.0alpha1_64bit.zip

Please don't post it on any software listing sites until it reaches the official release status, though, it is somewhat mean to expose unsuspecting people to unfinished software.

Also, the uploaded version is Intel and 10.5 or greater only, the same that would go on the App Store. The final version will be available for older OSes and PPC, though.

Now, for the change list:

• As mentioned, lots of internal rewrites. The Unarchiver and the command-line tools now use mostly the same code to unpack, unlike earlier when The Unarchiver was stuck with old code. This has probably introduced bugs, so watch out.
• Some UI changes: The icon is now always visible to make it easier to deal with crashes, the file list now shows multi-part archives better, and the password view actually shows the filename of the file.
• It is now possible to explicitly set the encoding for passwords.
• Experimentally added support for never creating an enclosing directory, as has been requested. I am not entirely sure this won't cause problems, though, so it might get removed if it does and can not be easily fixed. Please report experiences with it, good or bad.
• Fixed strange UI lockup that would happen sometimes with password-protected files.
• Full support for WinZip Zipx, including Wavpack and JPEG modes.
• Support for Mac OS X extended attributes in Zip, Tar, and Xar. Also supports setting Spotlight comments from archive comment fields.
• Support for extracting resources from Flash SWF files. Embedded images and sounds can be extracted into separate files.
• Support for Ar and Deb archives.
• Support for self-extracting 7z.
• Support for LBR with embedded crunched and squeezed files.
• Better support for huge Zip files.
• Better support for old StuffIt (thanks to Friendly Archivist),
• Bugfixes for Zip, RAR, Tar, Cpio, HQX, CAB, Zoo, PackIt,

For programmers:

• There is now a XADSimpleUnarchiver class that does a lot of work that XADArchive used to do.
• XADArchive will now use XADSimpleUnarchiver internally. XADArchive is also (still) deprecated, so I am not going to guarantee it will work flawlessly. Feel free to report bugs in XADArchive, but if they are very complicated I might not fix them. New features will not be added to XADArchive either, except those it gets for free through XADSimpleUnarchiver.
• The XADPath interface has changed in various ways, some of them backwards incompatible. Hopefully nobody is relying very much on specific features of this class, but if you do, your code might break with the new version. If you need help fixing it, feel free to ask me.
• Archive entries now have a XADIndex field for easy ordering. There are also new fields giving the index of the next and first solid entry.

In addition, version 0.99 of the command-line utilities has been released. The 0.99 version number signifies that the interface for them should now be the one that will go into 1.0, and which will be stable from 1.0 onwards, but there might still be some tweaks before that. Hopefully nothing will change, though.

Mac OS X version: http://theunarchiver.googlecode.com/files/unar0.99.zip
Windows version: http://theunarchiver.googlecode.com/files/unar0.99_win.zip
Source code: http://theunarchiver.googlecode.com/files/unar0.99_src.zip

• All the file-format-related improvements from post >>34 also apply to this version of unar and lsar.
• The command-line interface has changed drastically. Things have been renamed, moved around and lots of stuff has been added.
• The JSON code output by lsar in JSON mode has also changed.
• unar now has interactive prompts to deal with file collisions and similar things. There are also options to override the prompts.
• unar can now enclose extracted files in subdirectories, much like The Unarchiver. There are various command-line options to control the behavior.
• lsar now has a long format (-l) which displays more information about files.
• The programs now exit with error codes on errors.
• The Windows version no longer needs the OpenSSL dll file, and now only relies on Foundation1.0.dll.
• There is now a separate source code archive for unar and lsar. It contains mostly the same as the The Unarchiver source archive, except for the GUI-specific parts.

Grabbin' it.

Any chance this could open Nero .NRG files?

>>37

Some proprietary ISO formats work. I think .CDI works, but I forget if I tested .NRG. Try dropping one on the icon and seeing if it works. I haven't yet added icons for them, though. I'll try to get that done for the final release.

The simple listing of lsar 0.4.0 (only file path, no filesize, etc.) would be nice to have again. Maybe a --short -s option?

>>39

I guess I could possibly also just revert the standard view to the old format. I added the more elaborate one before implementing -l, so it's a bit redundant now.

hi the unarchiver seems to require a password before it unzips my file but i don't know of any password. please help! thank you!

>>41

Ask whoever made the file.

Here is another alpha release of 3.0:

http://theunarchiver.googlecode.com/files/TheUnarchiver3.0alpha2_64bit.zip

Just a few changes: Support for broken RAR files created by some unidentified archiver, and Japanese, German, Russian and Italian translations.

What I'd really need now are some more translations! I can't seem to get a hold of a lot of the people who did the previous translations, and so I'll need to find some new volunteers. If you'd feel like translating The Unarchiver into your language, please grab the source archive, and then go through the .nib and .strings files in the English.lproj folder, and translate them all, then send me the results.

The source is here: http://theunarchiver.googlecode.com/files/TheUnarchiver3.0alpha2_src.zip

>>35
IMO making xadmaster in a DLL or merging lsar as an option/switch of unar can make the binary size smaller.

I'm trying to create Bash completion specifications for lsar and unar. When it tries to complete an archive name, I'd like it to only offer the names of archive files. Is there a list of extensions that I could use to filter the list of filenames?

>>45

Not really. The Unarchiver doesn't look at extensions much.

You could try to dig out all the extensions listed in the Info.plist file that that the Mac OS X version uses to register for filetypes, maybe.

lsar says this file is corrupted xttp://pastebin.com/VvYp3ir6

>>47
agh, lsar directly from mercurial source.

>>47

Looks like a really new issue, I'll look into it later. For now, try hopping back a few revisions and see if it goes away.

http://apps.bandisoft.com/bandizipx/
doesn't it look like The Unarchiver?

bug report

OSX Lion 10.7.2,The Unarchiver 2.7
Unarchivering x,-,+
and Minimize.
Don't exist to app.

>>50

Hahahah, it sure does. And they're not supplying any source, which is a license violation.

>>52
Sue them for $100,000/day.

I have downloaded the unarchiver for my Mac, however, I can't seem to open the file. It shows this screen and nothing more.

Any suggestions?

Hi. Sorry for the delay.

>>40
Please do. That'd help a lot.

>>49
If I update to the revision 660:db09ff7312a9, just before the tip 661:7006e72e3a01 "Apply Zip64 fix from Greg Seitz", the error disappears.

try to put all of them on or try to up date your computer

The attached file will expand with version 1.6.1 but not 2.7.1

Version 2.7.1 gives error "Could not write to the destination directory."

-Bill

God, BandiZipX even sells in App Store for $1.99 USD!
http://apps.bandisoft.com/bandizipx/

Cyrillic is totally not supported. Every zip and rar has broken filename.

>>59

Please file a bug, with example files and information about what the correct output should be.

Hi,

http://bjfrj.blogspot.com/2012/01/john-talabot-fin-2012.html

the pwd protected rar archive above can not be opened with The Unarchiver. It extracts without problems with Alexander Roshal's unrar 3.60 on the cmd line.

Regards,
Klaus

>>61

It works fine here. What version are you using?

>>55

Should be fixed now, I think.

Time for another alpha version. It's mostly done now, though:

http://theunarchiver.googlecode.com/files/TheUnarchiver3.0alpha3_64bit.zip

However, I am still lacking translations! The Danish, Spanish, French, Korean, Portugese, Swedish and traditional and simplified Chinese translations have not been updated for 3.0. I'd really like to find someone to translate these before the final release, and also any other language which is not supported yet.

(I guess I should just do the Swedish one myself, but I'm not sure I even know Computer Swedish...)

Changes from alpha 2 include:

• Enabled sandboxing. Hopefully this doesn't break anything. This could use some testing!
• Support for old High Sierra CD images.
• Support for LZMA2 in 7z.
• Support for multi-volume StuffIt files.
• Cleaned up the filetypes and added some ISO image formats, like CDI, NRG and MDF.
• Fixed some self-extracting LZH files. (That means Touhou 7.5.)
• Filename encoding handling bugfixes.
• Zip64 fixes.
• Symlinks in zip files were broken.
• Less crashing on supported and unsupported sitx files.
• Fixed junk added to the ends of uncompressed encrypted files in RAR.
• Bugfixes for DiskDoubler, tar and MacBinary.

Well, 3.0 is finally released.

http://itunes.apple.com/app/the-unarchiver/id425424353?mt=12&ls=1
http://theunarchiver.googlecode.com/files/TheUnarchiver3.0.zip

It also has a new site:

http://unarchiver.c3.cx/

A summary of the changes, as listed in the earlier posts:

• Support for WinZip Zipx.
• Support for extracting images and sounds from Flash SWF files.
• Support for various Unix formats, such as ar and deb.
• Support for more CD and DVD image formats, such as MDF, NRG and CDI.
• Better support for Zip64 (large zip files) and extended attributes.
• Better support for 7z (self-extracting files, and LZMA2).
• Better support for some old formats, like LBR, StuffIt and DiskDoubler.
• There is now an option to never create an enclosing folder when extracting an archive.
• The icon is now always shown, even when extracting.
• The Unarchiver is now sandboxed.
• Lots of bugfixes.

Also, it is still lacking translations! It is most definitely time for people to step up and contribute some!

Also, the version of The Unarchiver linked in the last post is the one built for the Mac App Store. It has no support for PPC or older versions of OS X. I hope to get a version built that does have this support, but it's getting a bit complicated, so it will be delayed a little bit.

Similarly, there is no WIndows build for unar.exe and lsar.exe yet. These will also follow shortly.

Oh, also, one change that went unlisted: unar and lsar now have less a less terrible Makefile.

Does it means that if i have already bought the Archive Browser, it is no use for me to install the Unarchiver simultaneously?

Hi!

As a French user, I've seen that unfortunately you no longer support French (among others) on the last version of unarchiver, and you were looking for some volunteers :)

I might try to do it and help you to translate it in French (and maybe in Spanish, but let's deal with the French first), but I was wondering.... how ? How could I "submit" a translation, what is the best way to do it according to your needs, ... ?

Sincerely,
Elendil.

Hi,

I could help too for the French translation. Feel free to contact me !

Hi,

I could help too for the French translation. Feel free to contact me !

>>68

It depends on which interface you prefer. The Unarchiver is simpler.

>>69

Download the the source code from http://theunarchiver.googlecode.com/files/TheUnarchiver3.0_src.zip, then use Xcode to translate all the files in English.lproj, and save them in a fr.lproj directory. You can try copying this into the The Unarchiver along with the others to see if it works.

If you get something working, post it on http://code.google.com/p/theunarchiver/issues/list

Ok, there aren't a lot of strings to translate. I'll do it as I need to relax a little, and post it tonight ;-).

Hi again,

I've opened an issue as you asked, with the French translation file attached (http://code.google.com/p/theunarchiver/issues/detail?id=445&q=french)

hey !WAHa.06x36 & guys. can you help me test this? i'm on lion 10.7.3 and i've read sandboxing is causing problems for some developers and users already.

download isoul from macupdate and decrunch it with v2.7.1. launch isoul and after accepting the quarantine warning (this application was downloaded from safari, blah, blah) it should launch ok.

now try to decrunch it with v3. after accepting the quarantine warning, isoul will just stay bouncing on the dock. clicking on its icon will make it exit without warning. if you try to launch it a second time it will launch ok.

this behavior is happening on other apps and i think that it's caused by sandboxing and a quarantine bug in lion. not sure if it's caused by the unarchiver alone or a combination of lion, safari and the unarchiver (i haven' tested trying to download with another browser). can someone try to reproduce it? thanks.

isoul (direct link from macupdate)
http://www.macupdate.com/download/33320/iSoul%200.5.0.b1.zip

sources about sandboxing and qurantine issues:
http://reviews.cnet.com/8301-13727_7-57374676-263/workarounds-for-quarantine-bug-in-os-x-lion/
http://stackoverflow.com/questions/9544874/how-can-i-stop-my-app-from-setting-the-quarantine-bit

The extract from SWF feature is great, I'd love to have the same for PDF files:

• extract the text into a single txt file
• extract the vectors into a raw post script file per page
• extract the images into png or jpeg files depending on the type

>>75

I've noticed similar problems with other apps, and if you extract shell scripts they will not run at all from the Terminal.

I don't think this is technically a bug in The Unarchiver, more an unintended consequence of some OS X features. It should perhaps be reported to Apple.

Also, does Archive Utility do the same thing or not?

you're right it's apple's fault but caused by sandboxing. many people complaining about the shell scripts (also editing with textedit will screw them up but textwrangler and bbedit won't).

both the unarchiver 2.7.1 and archive utility (sandboxed?) work fine.
i guess it's a matter of waiting for the next major os x update (10.7.3 didn't fix it) or mountain lion.

thanks man and best to you.

If you or anybody else find any information about how to work around this, or if anything else needs to be done to fix it, do post an issue about it on the bug tracker.

according to my link above (stackoverflow.com) the LSFileQuarantineEnabled should be set to FALSE in the application's Info.plist (the unarchiver, in this case) but even so, the bug always sets the quarantine flag on items processed by it. another guy suggested removing the quarantine flag programmatically (in this case, to remove it from the decompressed file) but it can't be done since the app is sandboxed. he also confirms that outside the sandbox, this bug doesn't occur. he filed a bug (i guess with apple) so it's a matter of waiting. i'll post if i have more news on this. keep up.

I had the unarchiver installed via mac app store, there was an update today, which i installed. Now when I try to unzip anything I get the error that the dir has no write permission. Other unzippers work just fine. How can I go back to the older version which had no problems? I checked chown and chmod on the ls -hal of the dirs and files, and they are all in order.

>>81

Due to sandboxing, only some paths are allowed. Currently, this is /Users/ and /Volumes/. What is the full path to the places you are trying to extract files from? I can try to add more in the next version.

In the meanwhile, you can get the old version from the Google Code downloads page.

I look forward to seeing the PPC version. I hope the Archive Browser will be PPC-compatible too.

There is no mention anywhere on the new Unarchiver homepage, the old Unarchiver page, or CNET that this latest version is Intel-only. I had to download to find out it wouldn't work.

>>82

re: your sandboxing...

i get the write permission dialog when I try to unzip to /unShared/incoming/

if I choose [extract elsewhere...] and navigate to /unShared/incoming/ the archive is extracted without issue.

i want the old behavior back, please.

i'll be very pleased to do some translation work for The Unarchiver if i have such a chance. i think i'm qualified to do that interpretation from English to Chinese(Simplified Chinese for Chinese Mainland). Just let me know it how to do it?

>>84

Unfortunately, Apple mandates sandboxing, and it is not possible to tell the sandbox that you want to access all files everywhere, at least not that I have found. So you are unfortunately stuck with it.

If you are really desperate, you can build your own version with the sandbox disabled. Maybe I will try to make the build for older version also not use the sandbox, we'll see what is possible.

>>83

The Archive Browser uses lots of 10.6-only functionality, so it will unfortunately never run on PPC.

>>85

I already had one offer for translation into Chinese, but I haven't received anything back yet for that. So I am not sure how to coordinate things so that you do not do the same work.

>>19
Wait, so you created a completely free implementation of a RAR extractor? One that can handle newer RARs?
Why isn't this big news? Or are there some sort of hush-hush patent issues involved?

>>88

It was pretty big news earlier. FSF announced it as one of their high-priority projects completed.

Since the latest Unarchiver release, when extracting a rar file with multiple parts there is always an error near the end saying the file is corrupted and the whole file contained within the archive is not uncompressed. The files are not corrupted. I tried to extract them using 3 other applications and they all perform well. This sarted happening with the latest 21 March version.

>>86

ok, gotcha, thanx for the info. workaround implemented by creating a /Users/tmp/

sigh.

>>90

I need some actual files that fail if I am going to be able to do anything about it.

The new 3.0 version claims that cannot extract a zip inside my
/Ruse/IdeaProjects folder which is writeable and the version 2.7 can write there easily, I can write there anything from finder, better zip can write there too, but unarchiver 3.0 cannot at all.

Any idea?

>>93

See >>84 and >>86.

How do I uninstall the Unarchiver on my mac osx? Every time I try to open a RAR file it crashes. I can't find it in my applications folder. Please help.
lisakovshoff@gmail.com

>>95

It is whereever you or the App Store put it. I can not say where that is.

>>65
I can translate this great tool to danish (for free of course). Please contact me if you need me :)
felix.drud@gmail.com

does it support .jar

>>98

Yes. .jar is just .zip renamed.

In the options I have selected: Open the extracted folder on successful extraction.

As far as I can recall, the behavior for the previous 2.x.x versions with this option enabled was to open the enclosing folder with the extracted file/folder already SELECTED/highlighted.

In v3.0, it opens the enclosing folder, but DOES NOT automatically select the extracted file/folder. This can be frustrating when you have many files/folder already in the enclosing folder.

>>100

Yeah, somewhere along the line a bug crept in there. I'll try to get it fixed for 3.2.

Ok, 3.1 has finally been approved, and is now out. Changes are:

• Fix crashing on 10.6.
• Added French and Swedish localizations. More localizations are still needed! If you can, consider submitting one yourself!
• A few other small bugfixes.
• Build for old OSes and PPC available again.

It does not fix any of the sandbox issues, because it is still unclear what can be done. I have started a DTS issue about it with Apple, but they haven't gotten back with a full reply yet. In the meanwhile, if this is causing problems for you, try the legacy version which should not have sandboxing enabled, and report back if it works better! I could really use some feedback on this.

Confirmed, 3.1 (legacy) fixed sandbox issues; I downloaded the same applications that failed under 3.0 and they extracted and launched correctly on 3.1.

Where did you put the PPC version? The Unarchiver 3.1 "legacy" version is Intel.

>>104

Hmm, it's supposed to be PPC too, but maybe it isn't. That's a mistake.

Ok, Xcode is just not building the PPC version even though I have the PPC compiler installed, and selected. Geez. I have no idea what's up with that.

If anyone has any clue how to get this to build right, I'd really appreciate hearing about it.

Hey! I want translate it to dutch! What e-mail can i use to send an e-mail?

>>107

paracelsus@gmail.com

However, I think someone just offered to do that earlier this morning. I haven't heard anything back yet though.

What's the last version that definitely works on a PPC running 10.4.11? Thanks.

>>109

2.7.1 should run, and 3.1 would also run if I could just convince Xcode to compile it. Hopefully soon I will figure it out.

Version 3.1 is still not working outside those "special" folders. I have a folder called /Install where I put all my downloaded stuff and The Unarchiver does not work.

I hate it when a super piece of software stop working when a new version is released... Can you please fix this?

>>111

Get the legacy version. There appears to be no way to request write access to the entire filesystem with the sandbox.

Hey, does The Unarchiver support multi-part RARs for unzipping? Thanks!

>>113

Yes.

So, in the end, I put together an alternate build system using make, so that I could build a version that runs on PPC. It is now released as 3.1.1:

http://theunarchiver.googlecode.com/files/TheUnarchiver3.1.1_legacy.zip

The only change here is the added PPC support. There will not be an update to 3.1.1 for the App Store version, as there are no changes that affects that version.

I'd appreciate some feedback on how well this version works!

Thank you for the PPC version 3.1.1
It is working on a PowerBook G3 Pismo 500MHz.
Tested with a .7z, and some very old .sit and .hqx
-Bill

Yes, thanks for the extra effort to make the PPC version.

I tested it on a bunch of archives - no problems so far.

All right, then I should be set for PPC releases for the forseeable future, since I no longer need to rely on Xcode (just need an old copy of gcc from that).

However, since it's a separate build system, some bugs might creep in if I forget to keep it up to date. If any of you PPC users notice anything amiss in future versions, tell me about it so I can fix it, because it will likely not be that well tested, as I have no access to a PPC machine regularly.

I currently have version 3.1 installed on Mac OS X 10.7.3. There are instances were my compressed far files will give me an error with far file number 17. It only happens with file number 17 for some reason. When I try to uncompress with Keka for example, I get no error and the files in question decompress correctly. Like I said, this is happening on multiple occasions, and the error is always with file number 17.

I meant to say "compressed far files" not "compressed far files".

>>119

I'd need the actual files in order to do anything about it.

This version still throws an error saying the files are corrupted when extracting a file compressed into several rar files. The files are not corrupted since other tools are able to extract the files correctly. I'm really hoping this is solved soon so I can get back to using this great app as my only unarchiving tool :) If I click ok to dismiss the error the extracted file is never complete.

>>123

Again: I need the files in question, or I can do nothing about it.

It's kind of hard to send you 1GB files. All I can say is that this started happening two updates ago.

>>125

Well, then I can't do anything about it.

>>127

What exactly is the problem?

I got the same Problem like some other guys here. I get an error (file is corrupted) when I try to unpack some files. I have no problem to unpack the files with Stufflt Expander.

Problem with:
The.Big.Bang.Theory.S05E13.PROPER.720p.HDTV.x264-ORENJI
The.Big.Bang.Theory.S05E04.720p.HDTV.x264-ORENJI
(Examples)
I guess you can find them somewhere in the net. Releases from other group don't make problems. I guess maybe ORENJI use some special settings.

Thank you for your wonderful tool.
best regards

btw I use The Unarchiver on a MacBook Pro and a MacBook Air, both with Lion 10.7.3

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.

>>132

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. :)

>>134

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...

>>118

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?

>>137

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:

• Added a workaround for a sandbox bug in Mac OS X that was causing extracted apps to not launch properly.
• Added Polish, Spanish, Turkish, Latvian and Portugese translations.
• Fixed opening folders in the Finder after extraction.
• Fixed extraction of partial RAR files.
• Fixed spurious warnings about resource forks for some Zip files.

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

>>140

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.

>>142

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!

>>144

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?

>>146

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"

>>149

Please file an issue on the bug tracker, so I'll remember to fix this for the next release.

Can you answer a question (148)?

No, I do not understand it.

>>152
Could you please add file extension .zip.001 (and so on) to defaults?

>>153

.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

>>159

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!

>>162

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.

>>166

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.

>>165

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:

• http://theunarchiver.googlecode.com/files/TheUnarchiver3.3.zip
• http://theunarchiver.googlecode.com/files/TheUnarchiver3.3_legacy.zip

Changes are:

• Updated to support Apple's new stricter sandboxing rules. This means the program will need to nag the user more often, but should also mean that extraction should work better in non-standard locations. May also have introduced new bugs, so be careful and report any problems.
• Support for extracting bitmap images from PDF files.
• Support for AppleSingle files.
• Arabic and Norwegian translations.
• Legacy version hopefully works on G3 again.
• Bugfixes.

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):

• Support for extracting bitmap images from PDF files.
• Support for AppleSingle files.
• Experimental support for extracting Mac data forks in HFV Explorer style on Windows.
• Fix some crashing and other issues on Windows.
• Bugfixes.

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.

>>173

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

>>177

It will work if you just drop the files directly on The Unarchiver.

>>178

Can you be more specific in what order you do things, and when what happens, including any file dialogs The Unarchiver might use?

>>178

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.

>>182

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

>>184

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

>>187

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:

• Added Retina display support.
• Fixed an OS X sandbox issue that would cause multiple extractions to fail.
• Bugfixes for Tar and PDF extraction.
• Bugfix for the extraction progress bar for some 7z files.
• A few translation updates.

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:

• Bugfixes for Tar and PDF extraction.

Is there somewhere in the settings I can change the language? I'm swedish and for some reason I got the app in norwegian...

>>192

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?

>>194

Not really. Does it print anything to Console.app?

>>195

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:

http://pastebin.com/UPfCz3iX

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]

>>196

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.

>>199

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.

>>201

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".

https://developer.apple.com/library/mac/#documentation/Foundation/Reference/NSFilePresenter_protocol/Reference/Reference.html#//apple_ref/occ/intfp/NSFilePresenter/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.

>>204

One is provided already.

>>203

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...

>>207

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.

>>206

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?"

>>209

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!

>>211

That's probably a bug that was fixed in 3.4 already.

3.5 has been released! Changes are:

• Added support for password-protected 7z files.
• Added an experimental AppleScript interface.
• Added a progress bar overlay on the dock icon.
• Chinese translation.
• Handle files opened from Mail.app better.
• Better support for very old StuffIt archives, including password-protected ones.
• Fixed a bug where the app might stop launching at all under rare circumstances.
• Fixed some crashes on old OS X versions.
• Various bugfixes for PDF, hqx and sitx.

And as usual, unar and lsar have also been bumped to 1.4. Mostly they share the same changes, plus a few bugfixes:

• Added support for password-protected 7z files.
• Better support for very old StuffIt archives, including password-protected ones.
• Fixed some crashes on old OS X versions.
• Various bugfixes for PDF, hqx and sitx.
• Make lsar testing report wrong passwords properly.
• Make Windows versions stop printing meaningless warnings.

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"

>>221

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!

>>224

Are you using Default Folder X?

>>225

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 :-?

>>229

Sandboxed apps have their preferences inside their containers in ~/Library/Containers.

I am having the same problem, also on 10.8.2.

Both 3.5 and 3.5.1 will only show Unarchiver preferences when double-clicking an archive. It will not extract the archive unless I then Open the archive.

I deleted the preferences in ~/Library/Containers. This did not help. Preference files are re-created, but archives are not extracted on launch.

Choosing File->Open does still work. I noticed that the sandboxed app told me to ask for permission to extract to my Desktop. After that, quitting The Unarchiver, and double-clicking the archive still does the same thing. It just displays Preferences.

Reverting to 3.4 solves the problem for now.

>>230
Same as >>231 , it did not work. Reverting to 3.4 (>>232) works.

Also having the issue of only the preferences opening when clicking on an archive - using the newest version

>>235

There are many types of self-extracting archives, and The Unarchiver supports only some of them. Post the file on the bug tracker and I can look into whether it is possible to add support for it.

>>231-234

I can't reproduce this. Do any of you have a second machine to test on, to see if it has the same problem?

I have DFX installed. I turned it off, logged in and out, and reinstalled the current 3.5.1 (sandboxed) version. It will not open a rar file, when clicking on the file. Only the preferences opened.

I then installed legacy 3.5.1 (non sandboxed) version and it opened the same rar file as expected.

I then re-enabled DFX, and the legacy version opened the same rar file again, as expected.

The only issue is having to deal with the quarantine dialog every time the app launches.

Here's the console message, when attempting to open the rar file with the current version:

11/20/12 9:50:09.210 PM xpcd[221]: (null): have symlinks: (
)

Here's the console message when using the legacy 3.5.1 to open the same file:

11/20/12 9:52:17.744 PM The Unarchiver[13544]: A call to OSACopyScriptingDefinition() by NSScriptSuiteRegistry returned an error. Is this application's OSAScriptingDefinition Info.plist entry valid? If its value is 'dynamic', is there an 'ascr'/'gsdf' Apple event handler registered?

Hope this helps.

>>237

It worked for me in a second machine (MBA this year) until a minute ago, when I updated from the App Store, same OS version (10.8.2). Tell me if I can do any test for you.

Could anyone else check if they get the same console message as >>238?

>>239

Which version did you update from, that worked? 3.4?

>>241
I guess it was (I'm not sure, sorry). I installed it around 3 weeks ago from App Store

hi,
i have a problem with the unarchive program after the last upgrade, infact the softwr don't run. when there will be another upgrade?

ps some month ago i have maked a donation

>>246

I uploaded the fixed version to the App Store over a week and a half ago. It is up to Apple to approve it, and they are not doing anything. In the meanwhile, you can download the fixed version from the download page.

The fixed version is finally out on the App Store. I am really not impressed with how long this took Apple to get around to.

lets get a 1024 by 1024 icon. makes a huge difference.

>>249

There should be one alread? The App Store refuses apps without one.

To everyone who has been having problem with only the preferences window opening in The Unarchiver:

It seems that having the program Typinator running while you launch The Unarchiver will cause this issue. I am not sure if this is the only program that causes this, but basically it appears to be a problem with Typinator. I have reported the problem to them, and if you are a paying customer of theirs, it might help if you report it too.

I'll see if there is a way to put in a workaround for this, but if not, you will just have to either turn of Typinator or wait for them to release a bug fix.

The Unarchiver only opens the preferences window for me. I do not, and have never, used Typinator. Some other program can also cause this issue.

I'm currently running 5.4b1 of Typinator, and I just reinstalled the current 3.5.1 (sandboxed version). It works as expected.

I know there was a recent beta update to Typinator, since installing the legacy 3.5.1 version. Not sure how many revisions there were between the initial problem cropped up, and the current "fix".

I'll report it to the Typinator people as well.

Version v3.5.1 seems to have a problem with unpacking archives in folders when i set the prefs not too. any one else having this problem?

version 3.5.1 is all ways creating new directory/folders when unpacking archives when i set the prefs not too. 3.4 didn't do it worked fine, anyone else having this issue?

version 3.5.1 is all ways creating new directory/folders when unpacking archives when i set the prefs not too. 3.4 didn't do it worked fine, anyone else having this issue?

>>254

Yes, that's a known bug, I seem to have messed something up in 3.5. It will be fixed in 3.6 most likely.

>>252

Does it do that even when you click an archive?

Yes. When I doubleclick an archive I get the preferences. I can then choose Open and click the archive. It will then extract. Then I close the preferences.

>>259

Can you check for any other programs that would modify how other programs work, that you might have installed?

>>253

Also, I can confirm that the 5.4 beta 1 version works better. Under normal usage, it seems to let The Unarchiver work normally.

(Strangely, it seems to have the same bug if I run The Unarchiver through the debugger with breakpoints set, but that shouldn't affect normal users.)

>>260
I killed the "Default Folder X Helper" process, i.e. killed Default Folder X and now the archive is extracted immediately (no preferences).

This is not a solution as I use Default Folder X frequently.

I installed the latest version as of today (v3.5.1). When I try to open any archive, "Preferences" is shown instead. I'm on a Mac mini (late 2012) running OS X 10.8.2.

>>262

You should report the bug to the Default Folder X creators.

>>263

See above: Either Typinator or Default Folder X seem to cause this problem.

>>262

Also, another user reported that upgrading Default Folder X may fix the issue.

>>264
>>265
Upgrading Default Folder X from 4.4 to 4.5.3 fixed the problem.

Default Folder 4.5.3 did not fix for me. I still get preferences every time.

>>267

What about Typinator? Or any other program that messes with all other programs on your system?

Two things:

1. I'm having some problems unpacking some RAR archives using The Unarchiver. It those archives that consists of serveral RAR files. It says the archive file corrupted. It works fine unpacking the RAR files with Stuffit Expander
2. When unpacking the same files with Stuffit Expander it doesn't have to search for other files (or whatever The Unarchiver does, which I have to manually approve due to the sandbox)

Both applications are installed via the App Store.

>>269

I need the files to do anything about it.

Bug Report :

When I was tried select and extract multiple zip and rar files, the unarchiver stop extracting randomly. some files was extracted, but some files wasn't.

I expected that filename encoding is a reason.
There was a file that didn't have encoding information. If single file was open, the unarchiver display encoding selection dialog box. But the file was mixed with other files, then the unarchiver stop extracting. But some case, unarchiver display selection box while extracting of multiple files.

Please check this problem. Thanks.

I do not use Typinator only Default Folder and I still keep getting the preferences constantly

>>271

This may actually be an OS X bug. Sometimes it seems files are dropped when you click multiple files.

>>272

It is most likely caused by some other program. Try to see what other similar programs you might have, and disable them and see if that helps.

I bought The Unarchiver and clicked on "install". A grey icon appears on Launchpad with a liitle white dot on what appears to be a progress bar but nothing happens, and clicking on the icon produces no effect. I tried clicking on "install" again and just got a repeat of the previous result. My O.S. is mountain Lion.
What can be done?

>>274

You'll have to ask Apple. I have control over any part of the download and install process.

Apple tell me to contact you about the problem! I guess I'll just have to avoid your programs in future if I'm just going to be be sent round in circles. Sorry!

I do not use "Typinator" or "Default Folder X", but I also have this problem with Preferences ... :-(

I tried starting in safe mode and then Archive Utility was all that worked. Tried on a test new user partition and still get the prefs window every time. I have no idea what else would cause that that i could adjust or remove.

>>276

As I said, I have no control over the installation. I couldn't possibly do anything about it.

>>278

If you somehow manage to figure out what it is, do let me know too, so I can warn people in the future.

>>266
Fixed for a short while. Now the preferences-pane-pain is back again.

There's another report that SwitchResX causes this, too.

3.6 has been released. Changes:

• Added support for the Internet Archive WARC format.
• Fixed the "Never create folder" option, which had accidentally been disabled.
• Fixed a bug in Polish translation that made Polish version crash sometimes.
• Fixed a bug that caused file formats to not be unselectable in the file type list.
• Fixed bugs in XAR/.pkg, CAB, HQX and Compress.
• Fixed a few more rare bugs and crashes.
• Made the legacy version work on 10.5 again.

The changes that carry over to unar and lsar, which are now at 1.5, are:

• Added support for the Internet Archive WARC format.
• Fixed bugs in XAR/.pkg, CAB, HQX and Compress.
• Fixed a few more rare bugs and crashes.
• Made the OS X binaries work on 10.6 and 10.7 again.

Thanks. 3.6 legacy seems to fix the crashing problem I reported for 3.5 on PPC 10.5.

The new version still brings up my preferences each time

>>285

The situation is still the same: This is caused by some other program. You need to figure out which one. See the earlier comments for hints.

Hi. I'm having a bug in my mac related to your software. The program itself is working fine (and I just updated it, still works but my bug is still here), but every time I use the Open With button for any archive I get 4 repetitions of The Unarchiver. I attached a picture showing the problem. Any ideas on how to fix this? Thanks.

>>287

It is an OS X bug, so you would have to report it to Apple.

HELLO I HAVE A PROBLEM!!!
When I click on .zip .rar files The Unarchiver just opens Preferences window and does not unziiping files, I have to manually go to File and set Unarchive to Desctop. I've tried to unninstall and clean after that, but still no luck. What can I do? Help me!

>>290

Update Default Folder X, Typinator or SwitchRes X.

Rather odd??? I've been having that preference problem and now suddenly it is gone. The only thing I have done different is to install an update for DivX Player. And now it works like before. Hope this helps find what caused the problem.

Even stranger now as it stopped and is back to the preferences again.

This file makes The Unarchiver crash/hang: ftp://ftp.hp.com/pub/softpaq/sp49501-50000/sp49585.exe

Mar 9 22:12:27 The Unarchiver[1403]: *** -[NSFileManager moveItemAtPath:toPath:error:]: source path is nil
Mar 9 22:12:27 The Unarchiver[1403]: (

	0   CoreFoundation                      0x00007fff8d139f56 __exceptionPreprocess + 198
	1   libobjc.A.dylib                     0x00007fff8fc2dd5e objc_exception_throw + 43
	2   CoreFoundation                      0x00007fff8d139d8a +[NSException raise:format:arguments:] + 106
	3   CoreFoundation                      0x00007fff8d139d14 +[NSException raise:format:] + 116
	4   Foundation                          0x00007fff8c832c7c -[NSFileManager moveItemAtPath:toPath:error:] + 107
	5   XADMaster                           0x000000010009995d +[XADPlatform moveItemAtPath:toPath:] + 62
	6   The Unarchiver                      0x0000000100005cb2 The Unarchiver + 23730
	7   CoreFoundation                      0x00007fff8d12970d -[NSObject performSelector:withObject:] + 61
	8   Foundation                          0x00007fff8c7b0d70 __NSThreadPerformPerform + 214
	9   CoreFoundation                      0x00007fff8d0a84f1 __CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE0_PERFORM_FUNCTION__ + 17
	10  CoreFoundation                      0x00007fff8d0a7d5d __CFRunLoopDoSources0 + 253
	11  CoreFoundation                      0x00007fff8d0ceb49 __CFRunLoopRun + 905
	12  CoreFoundation                      0x00007fff8d0ce486 CFRunLoopRunSpecific + 230
	13  HIToolbox                           0x00007fff89f502bf RunCurrentEventLoopInMode + 277
	14  HIToolbox                           0x00007fff89f5756d ReceiveNextEventCommon + 355
	15  HIToolbox                           0x00007fff89f573fa BlockUntilNextEventMatchingListInMode + 62
	16  AppKit                              0x00007fff8e92a779 _DPSNextEvent + 659
	17  AppKit                              0x00007fff8e92a07d -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 135
	18  AppKit                              0x00007fff8e9269b9 -[NSApplication run] + 470
	19  AppKit                              0x00007fff8eba2eac NSApplicationMain + 867
	20  The Unarchiver                      0x0000000100002198 The Unarchiver + 8600
	21  The Unarchiver                      0x0000000100001fc4 The Unarchiver + 8132
	22  ???                                 0x0000000000000002 0x0 + 2
)

>>294

It seems I can reproduce that here. Thanks!

>>294

Should be fixed now.

"Please choose filename encoding for this archive" error.

I have a very old archive of a hard drive that is a Windows Zip format file. I thought I had extracted it successfully using Unarchiver before, but needed to extract it again as the dates in the extracted folder had changed and I wanted a clean extracted version I could then make into a protected ISO image.

I have upgraded to Lion 10.7.3 and have upgraded Unarchived form 2.5 to 3.6.1 from the App Store.

I am now getting the error "Choose the filename encoding for this archive" over half way through the extraction. I found you chord change the encoding in the Advanced preferences dialogue. I did this, but what effect does this have on the rest of the archive? The encoding it wanted was "Japanese (Shift) JIS" and the file it was complaining about was a web favourite.

I know it is not crucial, but I would like all these files to be extracted as is. There is very little information about this error or what to do about it. I do have "Japanese (Shift) JIS" installed on my mac, as I went to the Tokyo Tower website and was able to display the Japanese page successfully and change to JIS encoding without any problem. I don't read Japanese and don't want any of the files in the archive to have incorrect encodings. The normal encoding of the archive should be Western.

Will the file it complains about not be extracted? What about files after that that have the now (incorrect) Japanese encoding?

Information about this would be much appreciated.

Thank you very much in anticipation.

>>297

That is not an error. It just means The Unarchiver is not sure what encoding the file uses, and is asking you which to use. Pick the right and click OK.

SOLVED!!! I have found out why The Unarchiver keeps going to the preferences....I have noticed that it gets extra code inserted into it and the application that is doing it is TEXT TOOLS.

There are very few components to the Mars Text Tools:

The plugin (TTFilter.bundle) located at /Library/Application Support/MarsThemes/plugins, and
A folder containing this document (as a PDF file) and the Uninstall program. That folder is at /Library/Application Support/MarsThemes/TextTools

To uninstall the Text Tools, open an application where they're active, open the Text Tools menu (easiest way is from the Application's main menu) and select "Uninstall Text Tools." If you have trouble finding an application that's running the Tools, open the folder referenced above and run the UninstallTextTools application.

I had a problem doing it this way and had to use the uninstaller. The Uninstall program is at /Library/Application Support/MarsThemes/TextTools

I have tested it several times now and when that Text Tools app is uninstalled, all works well. This also was causing crashes in VirusBarrier and a few other apps that were randomly crashing. Not a single problem since i removed them.

Hope this helps a bit and gives an idea what that code was doing

>>301

Good to know!

v3.7 has been released:

• Added Bulgarian translation.
• Fix a bug that would make files with invalid filenames not work in Zip and Exe files.
• Fix some small memory leaks.
• Read-only attributes for files in archives are now ignored. This caused some files not to extract correctly in older versions.
• Fix a bug with parsing Tar files.

And unar and lsar have been updated to 1.6:

• Added switch for quiet mode.
• Added contributed bash completion scripts.
• Fix a bug that would make files with invalid filenames not work in Zip and Exe files.
• Fix some small memory leaks.
• Fix a bug with parsing Tar files.

During extracting a multi-volume Rar archive (inside this: http://www34.zippyshare.com/d/55545561/225223/32134124121thirty.rar) the app (v3.7) stops with the message "The archive file is corrupted". If you press Stop or Continue button the app crashes: http://pastebin.com/qSv5Mitq . Similar crash (http://pastebin.com/yS3A6EmX) applies to the command line (unar, lsar -t) tools. Other tools/apps doesn't signal any errors in the archive when testing or extracting it.

>>306

Yes, I can reproduce this.

I found another one that is bring up the preferences: Appriority

The unar/lsar command line tools have been added to Homebrew, they can be installed with brew install unar.

Realized that The Unarchiver usually takes a little bit more of time to
extract archive files in comparison to other apps like Keka.
Although no matter how long it takes I have no other choice since it's the only app
that supports encoding choice when unarchiving.
Any... workarounds idea so far?