The below is an off-site archive of all tweets posted by @mjtsai ever

February 16th, 2016

@rosyna @drewthaler Similar issue in that some AppleScripts don’t work from sandbox, even when run using NSUserAppleScriptTask.

via Tweetbot for Mac in reply to rosyna

@rosyna @drewthaler If it’s a Gatekeeper issue, it’s one that only applies when the launching process is sandboxed.

via Tweetbot for Mac in reply to rosyna

@rosyna @drewthaler Not handy. DTS eventually explained it to me; they were initially unaware, too. I fear more undocumented cases like this

via Tweetbot for Mac in reply to rosyna

@rosyna @drewthaler No, there are cases where the document can't be opened if the app for it isn’t sandboxed, even if you punch a hole.

via Tweetbot for Mac in reply to rosyna

@rosyna @ameaijou @drewthaler I don’t think the link that you posted offers blanket exceptions. Plus, those are temporary.

via Tweetbot for Mac in reply to rosyna

@Schwieb @rosyna @ameaijou @drewthaler The fact that it’s not documented makes it seem risky to rely on.

via Tweetbot for Mac in reply to Schwieb

@rosyna @ameaijou @drewthaler Second issue is if I pare down to what’s supported, think things are OK, then run into bug or new restriction.

via Tweetbot for Mac in reply to rosyna

@rosyna @ameaijou @drewthaler First issue is what’s not possible, even with non-MAS entitlements, at least in a documented/supported way.

via Tweetbot for Mac in reply to rosyna

@rosyna @drewthaler For example, -[NSWorkspace openFile:]. The rules have changed several times w/ OS versions and are not documented.

via Tweetbot for Mac in reply to rosyna

@rosyna @ameaijou @drewthaler Yes, I’m saying there should be more. I don’t want to run into a road block *after* adopting sandboxing.

via Tweetbot for Mac in reply to rosyna

AppleWorks and the Capriciousness of Nostalgia: mjtsai.com/blog/2016/02/1…

via IFTTT

How to Fix the Safari t.co Twitter Problem: mjtsai.com/blog/2016/02/1…

via IFTTT

More Mac App Store Certificate Problems: mjtsai.com/blog/2016/02/1…

via IFTTT

@rosyna @ameaijou @drewthaler But only specific targets/ports that are known at compile time, right?

via Tweetbot for Mac in reply to rosyna

@rosyna @drewthaler I’m not just talking about file system access. But, re: files, really want to be able to fix ownership/permissions.

via Tweetbot for Mac in reply to rosyna

@rosyna @drewthaler And it doesn’t, AFAIK, address APIs that area available but behave differently when the app is sandboxed.

via Tweetbot for Mac in reply to rosyna

@rosyna @drewthaler If you’re referring to the big red button, that doesn’t sound like something that should be relied on.

via Tweetbot for Mac in reply to rosyna

@ameaijou @rosyna @drewthaler No, I mean the entitlements should go beyond what Apple would accept in the store.

via Tweetbot for Mac in reply to ameaijou

@danielpunkass @michaelpryor Yep. I once got a refund for FogBugz. A few years later, tried it again. Now been using it for about 7 years.

via Tweetbot for Mac in reply to danielpunkass