Not able to Install atemOSC on my work computer because not issues by an Identified Developer

[marsy62]

Hi,

I am not able to Install atemOSC on my work computer because not issues by an Identified Developer.

At work, our administrators do not allow us to do us, by policy.

Is there a possibility that the software will be signed as such in the future ?

[marsy62]

Hi,

How about making atemOSC an app with a "identified developer" ?

May I attach the error message (in French, but I can translate if needed) and the specs of my computer ?

Best regards.

Makha Sy

[mtoohey31]

Unfortunately, if my understanding is correct, it costs $99 USD/year to get a membership to the Apple Developer program, which is what the developer would need to do to get around this warning. However, since this application is open source, if you would like to foot the bill yourself, or if you know someone who pays for this, you could get them to build it with their developer license.

[SteffeyDev]

We set it up to build with my developer license, I put my personal key in Travis CI. If the signing is no longer working then that's probably just a bug in the build process.

[mtoohey31]

Actually I think the signing is working, didn’t check before I sent this, but you can probably mark the issue as resolved. You could double check on your if you want to be sure before you close it. On Aug 22, 2020, 10:11 AM -0400, Peter Steffey notifications@github.com, wrote:

We set it up to build with my developer license, I put my personal key in Travis CI. If the signing is no longer working then that's probably just a bug in the build process. — You are receiving this because you commented. Reply to this email directly, view it on GitHub, or unsubscribe.

[marsy62]

Hi Daniel,

Thanks for the response. I understand better now.

What process should I follow to build it myself on my computer ?

Makha Sy

Le 22 août 2020 à 14:08, Ninja99 notifications@github.com a écrit :



Unfortunately, if my understanding is correct, it costs $99 USD/year to get a membership to the Apple Developer program, which is what the developer would need to do to get around this warning. However, since this application is open source, if you would like to foot the bill yourself, or if you know someone who pays for this, you could get them to build it with their developer license.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHubhttps://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fdanielbuechele%2FatemOSC%2Fissues%2F166%23issuecomment-678645532&data=02%7C01%7C%7C6e136bc9c8e440de2d1408d846a4d01f%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637337020975438119&sdata=SzZzrYJLXUDFugmb5xa98GeFZiGw2fI2LYbhzy1W8oM%3D&reserved=0, or unsubscribehttps://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FANLLIR3MU327RV2QB6AAGY3SB7GM7ANCNFSM4OANOXXA&data=02%7C01%7C%7C6e136bc9c8e440de2d1408d846a4d01f%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637337020975438119&sdata=jv3daVKmE1oNL5dVXTYw5RXKDYgZg9pxUouRB40a6k0%3D&reserved=0.

[SteffeyDev]

So looks like Apple has made stricter requirements for apps, we now need to sign and notarize both the app and the dmg. I'll tackle that when I have the chance, but for the meantime added instructions on the README on how to bypass the warning.

[marsy62]

Thanks so much for simolving this issue with version 4.0 ! Congratulations !!

[SteffeyDev]

You're welcome, glad it works!