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!

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

I love the Unarchiver, but it would be terrific if it supported Delete After Extraction which is available in Archive Utility. Move To Trash is good but it's not of any use on network shares, you need a straight Delete for that.

Thanks!

So, it's time for another update. 3.8 is out, and this time I am so sick of Apple's approval nonsense that I am not going to bother waiting for them. I'm releasing 3.8 now, and whenever Apple feels like approving it, it will show up on the App Store. Expect a week or two, if things go quickly.

Changes are:

• Added Brazilian Portugese translation.
• Added support for XIP files.
• Fixed some crashes and unsupported files for RAR.
• Better support for RAR Mac OS X SFX files.
• Fixed crashes for certain CAB and PDF files.
• Added support for comments in Amiga LhA files.
• Fixed French translation.

lsar and unar 1.7 are also out, with mostly the same change list.

• Added -v option to just print version and exit.
• Added support for XIP files.
• Fixed some crashes and unsupported files for RAR.
• Better support for RAR Mac OS X SFX files.
• Fixed crashes for certain CAB and PDF files.
• Added support for comments in Amiga LhA files.

XADArchiveParser.m: In function '+[XADArchiveParser scanForVolumesWithFilename:regex:firstFileExtension:]':
XADArchiveParser.m:790:2: warning: passing argument 1 of 'sortUsingFunction:context:' from incompatible pointer type
XADArchiveParser.m:790:2: note: expected 'enum NSComparisonResult ()(struct objc_object *, struct objc_object *, void *)' but argument is of type 'NSInteger ()(struct objc_object *, struct objc_object *, void *)'
gcc -std=gnu99 -O2 -Wno-import -Wno-multichar -g -D_FILE_OFFSET_BITS=64 -isystem /usr/pkg/include -DGNUSTEP -DGNU_RUNTIME=1 -D_NATIVE_OBJC_EXCEPTIONS -fgnu-runtime -fexceptions -fobjc-exceptions -fconstant-string-class=NSConstantString -MMD -MFBuild/XADArchiveParserDescriptions.d -MTBuild/XADArchiveParserDescriptions.o -c XADArchiveParserDescriptions.m -o Build/XADArchiveParserDescriptions.o
XADArchiveParserDescriptions.m: In function '-[XADArchiveParser(Descriptions) descriptiveOrderingOfKeysInDictionary:]':
XADArchiveParserDescriptions.m:205:2: warning: passing argument 1 of 'sortedArrayUsingFunction:context:' from incompatible pointer type
XADArchiveParserDescriptions.m:205:2: note: expected 'enum NSComparisonResult ()(struct objc_object *, struct objc_object *, void *)' but argument is of type 'NSInteger ()(struct objc_object *, struct objc_object *, void *)'
XADArchiveParserDescriptions.m: In function 'DottedNumber':
XADArchiveParserDescriptions.m:274:11: error: request for member 'formatterBehavior' in something not a structure or union
XADArchiveParserDescriptions.m:275:11: error: request for member 'numberStyle' in something not a structure or union

>>315

Your GNUStep is probably outdated.

Why The Unarchiver doesn't unarchive automactly my .zip folder?

>>317

I am not sure what you mean.

Hello there,
I'm having a problem with the unarchiver and jar files, I do not want to use the unarchiver to archive jar files, but there is no possible way of doing it otherwise, and if there is no way of fixing it, how can I uninstall the unarchiver?

>>328

Use Get Info in the Finder to pick another program to open the files. Also, go easy on the Reply button.

I downloaded a zip which was password protected. I was never prompted for a password and ended up with corrupted files. It seems like they were blindly decompressed without decrypting or something to that effect.

Is there any way to fix these files or am I completely fucked up the ass and should throw my macbook away?

I tried re-zipping them then trying to force unzip with the password using the zip and unzip commands to no avail.

I downloaded a zip which was password protected. I was never prompted for a password and ended up with corrupted files. It seems like they were blindly decompressed without decrypting or something to that effect.

Is there any way to fix these files or am I completely fucked up the ass and should throw my macbook away?

I tried re-zipping them then trying to force unzip with the password using the zip and unzip commands to no avail.

I created a tar of a folder with subfolders in Windows 7.

When I extract them on mac, all the files are extracted, but the folder structure is not recreated.

Instead i get all files extracted to the top folder with filenames with "\"s. Example:

TopFolder\SubFolder1\file1.txt.

In windows this same files extracts correctly.

Am I missing an option or something?

Thanks.

>>332

I'd say the tar code expects forward slashes, and I don't think backwards slashes are correct in a tar file. But try to see if "tar xvf file.tar" in Terminal.app extracts it correctly or not. If it does, I will have to fix that.