As the previous thread filled up, here is part 2 of the The Unarchiver thread.
It is much better to post bugs on the bug tracker, rather than in this thread! Anything posted on the bug tracker has much less chance of being forgotten by me!
So, post bugs here: http://code.google.com/p/theunarchiver/issues/list
Also, remember that if you post a bug about a file that is not work, you must also post the file itself, or else there is nothing I can do about it!
Is there somewhere in the settings I can change the language? I'm swedish and for some reason I got the app in norwegian...
Change it in the OS X preferences. There is a list somewhere in there of preferred languages. OS X picks the language for apps according to that list.
Quick question: I'm using 3.4 downloaded from this site (not from App Store) and I notice that The U. freezes at the end when it's done extracting. It just sits there for like 3-5 seconds. Any idea why this happens to me?
Not really. Does it print anything to Console.app?
yes, it printed this in console:
11/1/12 9:44:57.460 AM sandboxd: ([67903]) The Unarchiver(67903) deny file-issue-extension /Users/xxx/Downloads/A History.pdf
11/1/12 9:44:57.461 AM The Unarchiver: __CFPasteboardIssueSandboxExtensionForPath: error for [/Users/xxx/Downloads/A History.pdf]
Here is the crash? log:
Thanks for looking into this.
>>196
replying to myself :)
I've gone back to v3.2. v3.2 seems to be the last version that doesn't crash on my machine (MBP running Lion) due to sandboxing issue.
v3.3 also crashes:
11/1/12 10:03:02.106 PM sandboxd: ([74839]) The Unarchiver(74839) deny file-issue-extension /Users/xxx/Downloads/The Unarchiver.app
11/1/12 10:03:02.108 PM The Unarchiver: __CFPasteboardIssueSandboxExtensionForPath: error for [/Users/xxx/Downloads/The Unarchiver.app]
Well, it's clearly a sandbox error, so if you grab the legacy version that should fix it.
It's a bit mysterious why it happens, though. Is there something special about your machine? What version of OS X?
>>198
I don't think it's anything special at all. I run latest Lion.. 10.7.5. I haven't upgraded to ML for a multitude of reasons.. main one being that I'm in the middle of a project and don't want to deal with issues that might pop up due to OS change. :)
But yeah, The U v3.3+ crashes every time I extract something but the files are extracted just fine. It is annoying to have that 4sec delay when the process is finished. Also, OS X doesn't pop up a crash dialog which is also weird.
Do you have it set to open extracted files, by the way? If so, try changing that.
When extracting RAR-files, those that contain a single file but are split in multiple RAR-files, after selecting where to extract the file I get another dialog saying that the Mac OS X sandbox is blocking access and I need to click Search to continue.
This is obviously due the the sandbox. But if I understand the sandbox correctly it should be possible to say that a given file has a dependency on one or several other files and the user doesn't need to select those. For example, a text document may contain an image but the document only contains a reference to the actual image. This is how TextEdit works with the RTF format.
I think this is called "Related item", there's a video from WWDC 2012, "The OS X App Sandbox", that talks about this problem. It's around 33:30 minutes into the video clip.
I can't find any documentation about that, but if it is actually document-scoped bookmarks, that doesn't help because those have to be created after you have gained access to a file through some other means. It only works for granting access to related files in documents you have created yourself.
Besides, what The Unarchiver actually needs to do is to scan through all the files in the same directory as the archive to find those that are parts of the archive.
This video clip mentions both "document-scoped bookmarks" and "related items". They seem similar but as I understand it they're not the same feature/concept.
Except for the TextEdit and RTF format they also mention an other example with a movie file and a separate related subtitle.
The API they mention is NSFilePresenter and the method "primaryPresentedItemURL".
I don't know if these API can help in this case, but I think it's worth looking into. The behavior of The Unarchiver might be more dynamic then this API allows.
If this won't work here's another idea that will make it a bit more user friendly. When extracting files The Unarchiver will remember the last location where a file was extracted to. But if the last file I extracted was a RAR file, as explained above, The Unarchiver will instead remember the last path where I pressed "Search", not where it was extracted to. Can these to location be remembered separately?
Hello Unarchiver-Team,
I love The Unarchiver. But in my eyes the sandboxed version sucks. Big time. I have to confirm every time I unpack a file, and this annoys the hell out of me. Please go back to the un-sandboxed version, or provide one in parallel. I will probably change because of this, I want extraction, here, now - and not extraction, here, YES,REALLY, now.
Otherwise - keep up the awesome work.
Cheers, Axel.
Well, I wrote some quick test code, and apparently it does nothing at all except tell me it won't let me have access to any file, ever.
Nobody on the internet seems to have ever used it, either, so I have no idea if it actually possible to do anything useful whatsoever with it.
Since one of the latest updates the unarchiver doesn't automatically open the extracted folder anymore. I unchecked and rechecked this function but nothing helps, also re-installed...
This is probably an OS X sandbox bug. Apple won't let me use the workaround for it. Try updating your OS and hope they fixed it, or use the legacy version.
Hmm, I see. What about my other suggestion:
"When extracting files The Unarchiver will remember the last location where a file was extracted to. But if the last file I extracted was a RAR file, as explained above, The Unarchiver will instead remember the last path where I pressed "Search", not where it was extracted to. Can these to location be remembered separately?"
It can probably be done, but would be a bit messy. Either way, file an issue for it on the bug tracker or else I will forget about it.
Hi! i've just found some weird error/bug in unarchiver 3.3
i don't know how to explian or what ocorred, but unarchiver repeatedly corrupted the contents of the Eclipse tar.gz file from the website. It extracted and deleted the original file, as standard but i always ended up with a damaged folder for the eclipse program. I did the shasum of the original tar.gz and it was correct, but i always ended up with the same problem. finally discovered this thread (https://bugs.eclipse.org/bugs/show_bug.cgi?id=297993#c6 ) and tried to untar the same tar.gz file with the mac default archive utility, and everything was ok then!
oh, also tried downloading several versions of eclipse IDE before understanding my troubles but it happened the same with every version of it!
That's probably a bug that was fixed in 3.4 already.
3.5 has been released! Changes are:
And as usual, unar and lsar have also been bumped to 1.4. Mostly they share the same changes, plus a few bugfixes:
Does not Launch After Update!
Thanks for this tiny but reliable powerful app. But after the update to v3.5 it just does not launch. I am using MacBook Pro OS X 10.7.4, once The Unarchiver was working properly, under the same operating system.
Gives the messsage:
The Unarchiver cannot be opened because of a problem.
Check with the developer to make sure The Unarchiver works with this version of Mac OS X. You may need to reinstall the application. Be sure to install any available updates for the application and Mac OS X.
Click Report to see more detailed information and send a report to Apple.
Ditto on the crash after updating to 3.5
Running 10.6.8
Crash log can be found here: http://pastebin.com/EHq9qzpK
Double ditto on the crash with with 3.5.
Running 10.7.5
There seems to be some kind of really terrible bug in Xcode which causes newly compiled applications to fail on 10.6 and 10.7, but not 10.8. I am investigating how to get around it.
3.5.1 is now available, which should fix the bug.
http://theunarchiver.googlecode.com/files/TheUnarchiver3.5.1.zip
Trying to get Apple to hurry up and approve it on the app store too.
I can confirm 3.5.1 fixes the problem. Thanks for the quick fix!
Running The Unarchiver 3.5.1 legacy on PowerMac G5, 10.5.8, I get a consistent crash:
EXC_BAD_ACCESS (SIGSEGV)
KERN_INVALID_ADDRESS at 0x000000004300000c
The archive I used to cause the above crash was "TheUnarchiver3.5.1_legacy.zip"
I need a full crash dump to look into that.
Hi! I'm using 10.8.2, and it does not work properly, it seems like something is misconfigured.
App does not crash, but before, when I double-clicked a .zip file, it was automatically extracted. Now, when I double-click the zip file, I get the Preferences screen, as if the filename had not been passed to the app.
I reinstalled both from the App Store and from the last link you provided (#219) but nothing changed.
Thanks!
Are you using Default Folder X?
No, I don't use that or any other Finder helper tool that I'm aware of. Any test I can do to help?
Same issue here. Only the Prefences dialog. OS X 10.8.2
Version 3.5 and 3.5.1
Deleting the prefences files resolved the issue
As said by >>228, I deleted Preferences/cx.* but there was no luck. And cx.* are not generated again :-?
Sandboxed apps have their preferences inside their containers in ~/Library/Containers.
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.
Also having the issue of only the preferences opening when clicking on an archive - using the newest version
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.
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.
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?
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
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.
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?
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.
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.
Can you check for any other programs that would modify how other programs work, that you might have installed?
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.
Also, another user reported that upgrading Default Folder X may fix the issue.
Default Folder 4.5.3 did not fix for me. I still get preferences every time.
What about Typinator? Or any other program that messes with all other programs on your system?
Two things:
Both applications are installed via the App Store.
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
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?
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.
>>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:
The changes that carry over to unar and lsar, which are now at 1.5, are:
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
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.
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!