App won't remember where to extract archives OR folder permissions

[GoogleCodeExporter]

Have already removed the app from my machine (using AppCleaner) and reinstalled 
from the App Store. Every time I try to extract an archive, I get the popup 
"Where should The Unarchiver extract archives?" Every time, I click "Extract to 
the same folder" but the app asks the same thing every time. Similarly, when 
trying to extract an archive, I get the message "The Unarchiver does not have 
permission to write to this folder. To allow The Unarchiver to write to this 
folder, simply click 'Extract'. This permission will be remembered for this 
folder, and The Unarchiver will not need to ask for it again." Despite what the 
message says, I am asked for permission EVERY TIME I extract an archive.

When I get the first "Where should The Unarchiver extract archives?" popup, the 
following line appears in Console:
3/14/14 10:12:39.884 AM lsboxd[594]: Denied process 1586(UNKNOWN) access to 
shared list cx.c3.theunarchiver.LSSharedFileList

After I click "Extract", Console shows the following:
3/14/14 10:14:09.412 AM The Unarchiver[1586]: view service marshal for 
<NSRemoteView: 0x102025b60> failed to forget accessibility connection due to 
Error Domain=NSCocoaErrorDomain Code=4099 "Couldn’t communicate with a helper 
application." (The connection was invalidated from this process.) 
UserInfo=0x60800006d940 {NSDebugDescription=The connection was invalidated from 
this process.}
timestamp: 10:14:09.411 Friday 14 March 2014
process/thread/queue: The Unarchiver (1586) / 0x100681000 / 
com.apple.NSXPCConnection.user.endpoint
code: line 2972 of /SourceCache/ViewBridge/ViewBridge-46.2/NSRemoteView.m in 
__57-[NSRemoteView viewServiceMarshalProxy:withErrorHandler:]_block_invoke
domain: communications-failure

15-inch, Mid 2010 MacBook Pro
Processor: 2.66 GHz Intel Core i7
Memory: 8 GB 1067 MHz DDR3
Software: OS X 10.9.2 

Original issue reported on code.google.com by akya...@gmail.com on 14 Mar 2014 at 5:18

[GoogleCodeExporter]

This sounds like some kind of sandbox bug. Very strange.

Try downloading the legacy version from the homepage and using that.

Original comment by paracel...@gmail.com on 14 Mar 2014 at 5:27

[GoogleCodeExporter]

The legacy version seems to work fine; no persistent location or permission 
messages.

Thanks!

Original comment by akya...@gmail.com on 14 Mar 2014 at 6:32

[GoogleCodeExporter]

I had the same issue/errors with the MAS version so I removed it (the app, 
~/Library/Preferences/cx.c3.theunarchiver.plist and 
~/Library/Containers/cx.c3.theunarchiver/ folder) and installed 3.9.1 from the 
website.  Unfortunately I'm still having a problem, even more so actually.  Now 
it asks every time if it should extract to the same folder as the archive or 
ask every time.  After that, it then shows the open/save dialog along with the 
"Where should The Unarchiver extract archives?" dialog window.
It seems to not be able to save/read the permissions between sessions as it 
asks these every time.

Attached is a log file of all the error messages from Console system.log when 
running TheUnarchiver in the above example.  There appears to still be a 
sandbox issue in regards to appleevents access requested by TheUnarchiver.

Original comment by j...@bingham.co on 31 Mar 2014 at 12:10

Attachments:

• TheUnarchiver.log

[GoogleCodeExporter]

There are a lot of errors in there that sound like internal OS X bugs...

You could try to run "defaults delete cx.c3.theunarchiver" and see if that 
helps, first, though.

Original comment by paracel...@gmail.com on 31 Mar 2014 at 10:20

[GoogleCodeExporter]

Thanks for looking.  I've since seen the XPC errors in other apps too so I'll 
have to look into those.
I'm still getting the Sandbox: appleeventsd errors only with TheUnarchiver 
though.

After a bit more testing, I've still got some problems that perhaps you can 
address.

Although I manually removed the entire container when I switched from the MAS 
version to the website version, I deleted the prefs via the "defaults delete" 
command as you have asked.  I'm still getting the following error in the 
console.
3/31/14 11:32:54.948 AM lsboxd[237]: Denied process 3808(UNKNOWN) access to 
shared list cx.c3.theunarchiver.LSSharedFileList

Looking in the container, that file is an alias pointing to 
~/Library/Preferences/cx.c3.theunarchiver.LSSharedFileList.plist, which does 
not exist.  But if the Sandbox is blocking access, you wouldn't be able to 
read/write to it anyways.  I even tried deleting the alias to let the app 
access it as a real file but that didn't help.  The Sandbox is still blocking 
it.

However, the archives are extracting even with that error, mostly...
I'm able not able to open archives in my home dir.  I get an error dialog 
window with "Could not extract the file "DIR/FILE.log" from the archive 
"ARCHIVE.zip": Could not create the folder."  In the console, it is recorded as
3/31/14 11:35:38.000 AM kernel[0]: Sandbox: The Unarchiver(3902) deny 
file-write-create /Users/jeff/.TheUnarchiverTemp0

Since the Sandbox permissions are based on the highest directory in the path, I 
granted myself write access to / and extracted a zip at that location, thus 
allowing TheUnarchiver write perms for the entire drive.  Not the best 
workaround but now I'm able to extract in any location without any issues, 
including my home dir now.

So although this workaround is allowing me to use TheUnarchiver again without 
problems, I'd prefer not to have to do it this way.
If you want to troubleshoot this problem further to track down the bug, I'm 
happy to help out.  Perhaps you have a debug-logging version of the app that 
would give you more info?

Oh, and if it helps, I'm running OSX 10.9.2 and TheUnarchiver 3.9.1 from the 
website

Original comment by j...@bingham.co on 31 Mar 2014 at 5:56

[GoogleCodeExporter]

Actually this only happened to me when using the Appstore version.
Installed the latest version from the code.google homepage and everything is 
normal.

Original comment by isaac.di...@gmail.com on 2 Sep 2014 at 8:24

[GoogleCodeExporter]

Confirmed on MAS version 3.9.1 on Yosemite 10.10.0 final release

Original comment by guillaum...@gmail.com on 21 Oct 2014 at 10:18

[GoogleCodeExporter]

The Unarchiver 3.9.1 (MAS) on Yosemite 10.10.1 - on a new Mac mini.

Preferences are set to extract into the source folder, and I was getting the 
permission error on every extraction.  

After reading the aboves,,, when I got the error, I bumped the save dialog to 
the next level up (the surrounding folder) and extracted.  Now, subsequent rars 
are extracting without the permission issue.

Original comment by dantear...@gmail.com on 11 Dec 2014 at 12:29