-
Notifications
You must be signed in to change notification settings - Fork 13
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix problem with packaged Unified Auctions UI app #591
Comments
Did you download the |
That's expected behaviour until we register at developer.apple.com, pay them something like $100 per year and then get a certificate the sign the app. We want to go this route, since it centralises the packaging and this doesn't prevent apple revoking the certificate at any time. But this is a macOS thing only and the only action we should take here is to add readme line somewhere to right-click + open the application for the first time. I think every power user knows about it and many big applications just ignore this "unverified developer" thing whatsoever. |
This did not help. Was still not able to open the app
Worked. Didn't know this workaround... thx for pointing out and of course makes sense to go this route if power users know and we add this hint to the readme |
Would there be another issue to add the readme note/workaround?
|
Re-opened the issue to tackle the leftover part.
I like both proposals and hence would vouch to do both. Especially the 2nd one as it is really at the touchpoint of the user journey where it is needed. We can't ensure that everyone checks the Readme but together with this indicator users will be aware |
Technical notes:
|
Goal
Install and run the application from release notes
Context
I tried to put myself in the shoes of a normal user to get the Unfied Auctions UI app running:
.dmg
fileNote: Building the application locally via running
npm run build
in the/electron
folder of this repo works perfectly fineAssets
Tasks
The text was updated successfully, but these errors were encountered: