Fix the "broken app" bug

devinhalladay commented 8 years ago

Bug: When launching the app on a Mac after downloading, Mac OS X may tell the user that the app is broken and cannot be launched.

Reproduction steps:

Download the app via the website or via Github's releases
Change your Mac's security prefs to only allow apps from identified developers
Launch the app
The expected outcome is that the app will appear broken.

Current workaround:

Go into your system security prefs and allow opening apps from anywhere.
Launch the app.
The expected outcome is that the app will launch properly.

I need to create a fix for this as soon as possible, if anyone wants to take a stab at it I'd be more than grateful.

sandervankasteel commented 8 years ago

Your workaround doesn't work on mac OS Sierra (beta 5).

My current workaround of mac OS Sierra is, open the binary directly using a terminal.

devinhalladay commented 8 years ago

@sandervankasteel Thanks for the bug report! Someone else also reported this via Twitter and it turns out Apple has either removed or disable opening apps from unidentified developers in the macOS Sierra betas.

A temporary workaround is to run sudo spctl --master-disable in Terminal to disable their protection from unidentified devs.

I think I can register as a developer with Apple and rebuild the app with my certificate to eliminate this issue entirely—I'll try as soon as I have a chance (and an extra $99 laying around—I'm heading back to school in Baltimore tomorrow morning so money is tight for a couple weeks).

sandervankasteel commented 8 years ago

@devinhalladay thanks for your bloody quick response!

IIRC you only need the certificate to distribute apps in the Appstore and not for "normal" distribution on websites.

Your solution worked btw, thanks!

That being said, awesome work! 👍

sophielorenz commented 7 years ago

@devinhalladay Your terminal hack worked but only for a split second! If I close the application it reopens and reloads the darker UI. I uploaded proof that it worked, super bummed it was only for a few seconds, I really appreciate you making this app and am looking forward to it working sometime soon!

sophielorenz commented 7 years ago

Hold up. I reinstalled the app and it seemed to be working for a solid minute and then this pops up…

This happened after I gave it several more tries. It force closes itself and then immediately opens back up with the white UI, but will continue on a never-ending cycle of doing this.

ChiChou commented 7 years ago

A simple hack is to copy the whole .app directory with no metadata. Absolutely finder and cp command both keep the flag, so does tar. All you need is to copy the .app file by reading and writing the bytes manually.

These commands bypasses the GateKeeper for me:

npm install ncp; 
./node_modules/.bin/ncp /Applications/Broken.app ./Broken.app
rm -r /Applications/Borken.app
mv ./Broken.app /Applications/

devinhalladay commented 7 years ago

Hey all!! I've been so busy with school that I haven't had time to keep on development.

Here's the story: Spotify broke my development system by issuing a large restructure to their update system as well as to the way their application loads styling assets in the app on launch. I haven't had time to look into another workaround to get Spotio working again, but I haven't given up yet and as soon as I have a bit of time to look into this I will try to get all these issues solved and get Spotio up and running again as a functional theme.

In the meantime, thank you for your workaround @ChiChou, hopefully it will be useful for anyone else running into issues with Spotio being damaged because of GateKeeper.

In the next iteration of Spotio I think I will just take the plunge and subscribe as an Apple developer so I can manually sign the Spotio app, avoiding all this GateKeeper nonsense completely.

sophielorenz commented 7 years ago

Gah, I wish I were a terminal guru, but I’m not at all. I really didn’t understand your last email a bit to be honest. I will wait for the next version of Spotio and check back for updates. Thanks!

On Mon, Mar 27, 2017 at 10:36 AM CodeColorist

< mailto:CodeColorist notifications@github.com

wrote:

a, pre, code, a:link, body { word-wrap: break-word !important; }

A simple hack is to copy the whole .app directory with no metadata. Absolutely finder and cp command both keep the flag, so does tar. All you need is to copy the .app file by reading and writing the bytes manually.

These commands bypasses the GateKeeper for me:

npm install ncp; ./node_modules/.bin/ncp /Applications/Broken.app ./Broken.app rm -r /Applications/Borken.app mv ./Broken.app /Applications/

—

You are receiving this because you commented.

Reply to this email directly, https://github.com/devinhalladay/spotio/issues/3#issuecomment-289491869 , or https://github.com/notifications/unsubscribe-auth/AWBDZ5Vyu0_BZhqXcD-v3tTDWKAQ8supks5rp9d2gaJpZM4Jp6zQ .

devinhalladay / spotio

Fix the "broken app" bug #3