Are we planning to get TripleA notarized by Apple before the upcoming deadline?
currently, we recommend users installing to Mac OS bypass Gatekeeper by going to the security preference pane and overriding the warning given by the OS whenever opening an app for the first time unless it came from the apple app store.
My understanding is that after the deadline users will no longer be able to override these warnings.
"As a reminder, Mac software distributed outside the Mac App Store must be notarized by Apple in order to run on macOS Catalina."
"In September, we temporarily adjusted the notarization prerequisites to make this transition easier and to protect users on macOS Catalina who continue to use older versions of software. Starting February 3, 2020, all submitted software must meet the original notarization prerequisites."
Well technically TripleA (or any other java application) isn't apple software. We just generate a file that influences the behaviour of the Java Virtual Machine by a high degree.
That being said the only "native executables" are java and the install4j installer (which is also partly written in java).
So AFAIK it's pretty much up to the developers of install4j to find a solution to this problem
@RoiEX thanks just thought i'd mention it in case people were unaware.
Hmm had another look at this, it might actually be a problem.
Not that hard to overcome, but we basically need an apple device for this in order to generate a certificate.
Alternatively we could in theory submit to the app store, but we'd need a apple "developer ID" for this as well
Captain Crunch last edited by
screw Apple -.-
I don't think I'll ever be on Mac, so just mostly curious: does this mean that Mac users will still be able to play, like now, but keeping getting annoying warnings they cannot turn off, or does this mean they might not be able to use TripleA anymore?
one more thought on this, actually once we get notarization, the install process will actually be simpler than it is now bc we will no longer need to give instructions for bypassing gatekeeper (at least with catalina not sure if it would affect older systems or not).
but keeping getting annoying warnings they cannot turn off, or does this mean they might not be able to use TripleA anymore?
there will definitely be a warning and I'm not sure if the installer will continue to work.
However users will stil be able to run triplea manually (by downloading the JRE and TripleA separately), but this is a major inconvinience tbh.
The biggest problem is that I have no idea what exactly needs to be done so there are a lot of unclear questions to be answered.
Ideally we'd find a way so that the devs can manage everything as a group and don't have to rely on a single point of failure (which has gotten better over the years with out server management, but there are still some issues)
@RoiEX i think you just submit your code and it gets scanned automatically somehow.
On an abstract level you're probably right, but where do we need to submit it to and can we do that automatically using our current workflow?
@RoiEX looks like you do it using xcode somewhow:
"Make sure to submit all versions of your software. While Xcode 10 or later is still required to submit, you don’t need to rebuild or re-sign your software before submission."
i think i might already have a developer id and i definitely have xcode but i never really use it.