tauri-docs
tauri-docs copied to clipboard
tauri-apps
Validation App from Tauri homepage doesn't open on MacOS without ctrl-click
Describe the bug The example validation app from the homepage top banner doesn't open on Mac. MacOs rejects it because it isn't signed.
To Reproduce Steps to reproduce the behavior:
- Go to https://tauri.studio/en/partners
- Click on macOS - Dmg link on top banner
- Install app
- Try to launch app
Expected behavior Launches
Platform and Versions (please complete the following information):
OS: MacOS Node: - NPM: - Yarn: - Rustc: -
This is a problem, and I think it has to do with a couple things:
- we are not recreating (and signing) these apps on releases (which we should absolutely do)
- the docs site is are not pulling from the latest release samples (at the moment it is a manually entered link)
@jbolda & @rajivshah3 - what do you think we can do about number 1? @Laegel - what do you think we can do here about number 2?
@jmrossy - on a mac you do have to ctrl - click the app when you open it the first time and override the missing signature.
I am going to move this issue to the docs site and rename it. Thanks for the report!
Regarding the code-signing, I think that we should have that done (and configurable) within the github action
@nothingismagick For 2: I think we'll need to get Tauri's latest tag on the docs website, anyway. Doing this would allow us to create built apps links automatically (if we build each time there's a new release, of course). To get the latest tag, we can either inject a new environment variable (I guess the current action that rebuilds the docs would perfectly fit), consumed when building the docs or fetching the latest tags with an HTTP request when browsing the docs (a bit like the "Release notes") but the latter would be less optimized.
How do we want to version (if at all) the validation app? it doesn't exactly track 1-to-1 with tauri.js, does it? Since other deps could affect it as well.
every core release should have the validation app on the Github release assets. But that will be tricky since I believe we don't have a certificate for code signing / notarization on macOS?
I will sponsor this certification process from Apple Developer. Might take a few days to get it all sorted out though, and I am not sure yet WHICH company will be registered, there are a couple options... Lets discuss this in #core
For the "version" of the app, should we adopt the tauri core version number then? As tauri.js will mostly be a light wrapper, it seems fine to mirror the core version.