Forum Posts Feed
WriteMonkey for Windows: Mac beta
< Next Topic | Back to topic list | Previous Topic >
Posted by jaslar
Mar 31, 2018 at 08:14 PM
I’m downloading for Windows. Looks like 3 has folding!
Posted by Paul Korm
Apr 1, 2018 at 02:41 AM
Yes. Very very aware of all that. Thanks. However, the extra steps are needed for WriteMonkey—as I described, based on the developer’s notes for running WriteMonkey on Sierra/High Sierra. YMMV.
satis wrote:
>
>Paul Korm wrote:
>On macOS High Sierra you need to take steps to bypass Gatekeeper.
>
>
>
>Paul Korm wrote:
>On macOS High Sierra you need to take steps to bypass Gatekeeper.
>
>This is nothing new. Gatekeeper has been around since 10.7, and the
>solution isn’t complicated. If the app isn’t from the MAS or an
>‘identified developer’ select the app in the Finder and [O]pen it. macOS
>asks if you’re sure you want to open it - just click yes. If you’re
>still having an issue just to into Privacy and click to make an
>exception for a given app.
>
>Video:
>
>https://www.youtube.com/watch?v=jiUOODUR1GQ
Posted by Christian Tietze
Apr 4, 2018 at 07:15 AM
This is thanks to “App Translocation”, where .app bundles extracted into ~/Downloads/ are treated a bit differently: when you launch them, they will be copied to a secret location behind the scenes (= translocation) and opened from there. Even when you move the .app bundle out of Downloads and into /Applications/, the translocation stuff will still be operational. Thus the app may have a hard time knowing where it is, effectively breaking app updates, among other things.
Posted by Paul Korm
Apr 4, 2018 at 09:17 AM
Perhaps, but in the WriteMonkey case there appears to be more. Even if the .zip is downloaded directly to applications, the .app package can fail to launch correctly unless the developer’s instructions (as I mentioned above) are followed. The ‘incorrect’ aspect is that when the unzipped .app is run, it only launches the JS console and does not execute the program logic. It’s a beta product and the developer probably hasn’t had time to “productionize” the package for macOS.
Christian Tietze wrote:
This is thanks to “App Translocation”, where .app bundles extracted into
>~/Downloads/ are treated a bit differently: when you launch them, they
>will be copied to a secret location behind the scenes (= translocation)
>and opened from there. Even when you move the .app bundle out of
>Downloads and into /Applications/, the translocation stuff will still be
>operational. Thus the app may have a hard time knowing where it is,
>effectively breaking app updates, among other things.