Replies: 1 comment 1 reply
-
Hey @emha. My understanding is that to distribute any apps to other macOS devices in a way that doesn't require the user to make system-level changes, you must notarize the app, and to do so requires access to an active Apple Developer account (with associated costs). However, Apple do provide some explicit guidance about circumventing this requirement here, under the heading "If you want to open an app that hasn’t been notarized or is from an unidentified developer". |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hi there,
we are currently thinking about building a small app for our dev's so they can access all our toolings from the app. This will be an internally used app so we don't want to publish it. I tried and shared a sample app with one of my colleagues but she couldn't open the app (just talking about mac here).
A way around that could be that every dev just pulls the GIT repository and builds it themself but than we would have to communicate every change instead of using the updater so this would be my very last option.
We even re-enabled the osx setting to allow apps from every source but this didn't work either. Is there a way around the developer account and signing for just internal distribution? Or am I doing something fundamentally wrong that this doesn't work? 😆
The "error" is just: "This app can't be opened" (even with right-click -> open). The app is build for the correct architecture.
Thanks in advance :)
Beta Was this translation helpful? Give feedback.
All reactions