@Apple Normally yes, but the loophole is that this ‘Allow Anyway’ button only appears when I cancel the popup.
Ok, finally got it working by doing the following steps:
- When the popup appears press the ‘move to bin’ button
- Open your bin and drag the ‘Stripe’ executable to your desktop
- Double click it
- Then again in your Security & Privacy settings the ‘Allow anyway’ button appears. Clicking it now continues to install the Stripe CLI
Now in Wappler activating the Stripe Webhooks tab should work
1 Like
weird we use the command:
brew install --no-quarantine stripe/stripe-cli/stripe
so quarantine should be removed…
Back to the roots
If this happened with Stripe, it’ll also happen with NodeJS - which I had a (very) hard time fixing it:
I had to xattr all files written by NodeJS installation, it was really messy
well the --no-quarantine flag on homebrew should be doing the xattr for us.
With node npm there is a different story - there indeed we might do it ourselves but happily we don’t install many binary modules there. And now that we deliver those few binaries within wappler with the build in wappler node sevrer - it is no longer really necessary.
@Mennovandijk are you using the latest Wappler?
Maybe try to update homebrew first.
@george there still seems to be a quarantine issue in 4.9.1 but the above workaround no longer seems to be an option.
I don’t have the option of Move to Bin any more:
Choosing Show in Finder briefly shows the file but it seems to be automatically deleted as the Wappler/Homebrew process continues.
The only way of getting around it now is to
- Have it run
- Choose Open In Finder
- Keep the Finder window open while it is run again (DON’T CLICK EITHER OPTION IN THE ABOVE DIALOGUE)
- From the finder window that you opened earlier, find the Stripe folder and open the subfolders until you get to the executable file and copy it to your desktop
- Now click the OK button in the dialogue
- Open the stripe executable from your desktop
- Now you should be able to run the Webhooks terminal in Wappler
That’s not the point, I presume Wappler should be able to do it and something isn’t working quite right
Well we execute the same command so I was wondering if it was a permission issue because it is done from within Wappler or is it always the case even if executed from a terminal outside?
If it works from outside - then we will remove the automatic installation and provide manual instructions.
Is there any way to get Homebrew to wait for permission before proceeding/deleting the CLI executable?
What permission do you mean?
The Mac quarantine. Don’t worry, thinking about it, that wouldn’t work…
It’s just when you click the Show In Finder button on the prompt, Homebrew continues and because it has ‘failed’ and deletes the executable - I just thought there might be a way of interrupting that deletion but I can’t think of how you could do it
Till this problem is solved I suggest Wappler to disable automatic installation of stuff
Last time I had a really bad experience with NodeJS installation, and from the looks of it not many people complain because of the built-in NodeJS server doesn’t require NodeJS installed 
I’m happy to report that after a lot of investigating and cooperation with the homebrew team, we found the right way to officially and secure install the needed components.
So starting from the next update, there will be no warnings that Apple cannot check this software and everything will install just fine.
2 Likes
Fixed in Wappler 5.4.1