About six months ago, Apple announced that Notarization was going to be mandatory. In particular, it doesn't say anything about Notarization.
#Qt mac install issues code#
That code signing documentation was first written in 2008 and has not been updated in over two years.
![qt mac install issues qt mac install issues](https://i0.wp.com/daviesmediadesign.com/wp-content/uploads/2019/11/GMIC-QT-Plugin-Website-for-MAC.jpg)
#Qt mac install issues how to#
Please see my earlier suggestions on how to do an end-around of Gatekeeper. Qt is just a dead end on the Mac - end of story. I'm not going to take the same diplomatic approach as eskimo. A decent VM will support snapshots, making it easy to roll back to an inital state and test again. When doing any kind of testing on Gatekeeper or other system-level interactions, I strongly recommend testing in a VM. Otherwise, you have to use the new "log" command line tool as well as its predicate language for searching for relevent log entries in the past. It has to be up and running before you do your test. You can't use Console.app like you would have years ago. That suggests you might be unaware of significant changes to the macOS logging infrastructure over the past few years. And I'm not sure what you mean by "looking at console logs displayed". I also doubt you are going to find any meaningful information in the logs. Some things, like self-modifying apps, are just not supported. If you find that your built binary isn’t following the nested code rules, you may be able to fix that using the technique outlined in this post.Īpple Developer Relations, Developer Technical Support, Core OS/Hardware let myEmail = "eskimo" + "1" + In most cases. That is by far the most common cause of problems like this. Now, if you want to fix this for yourself - or, perhaps, cooperate with other members of the community that rely on the same tools - then my #1 recommendation is that you look at how your built binary complies with the rules in the Nested Code section of Technote 2206 macOS Code Signing In Depth. And if your tools vendor is not keeping up with platform developments, that’s something you need to factor into your tooling choices. For example, Oracle seems to do a good job of this on the Java front. They should be keeping abreast of the latest platform developments and updating their tools accordingly. You need to look to your tools vendor for support here. The “funky bundle structure” that john daniel refers to presents deployment challenges, but it is possible to use a non-standard bundle structure and be compatible with modern versions of macOS.