I’ve set my “Development Team ID” and have set the “Code-signing Identity” to “Developer ID Application” in the “Xcode (MacOSX)” exporter inside the Projucer. When I compile, I get the following error:
Note:MyProject - AUv3 AppExtension has conflicting provisioning settings. MyProject - AUv3 AppExtension is automatically signed for development, but a conflicting code signing identity Developer ID Application has been manually specified. Set the code signing identity value to “Mac Developer” in the build settings editor, or switch to manual signing in the project editor.
(similar errors for VST, AU, AAX targets as well)
in Xcode it looks like this:
It compiles fine if I uncheck “Automatically manage signing” and also if I remove “Developer ID Application” from the Projucer, so that the default of “Mac Developer” is used.
Thanks, that’s an interesting idea. But it does sound like a workaround. Using Developer ID works fine with the JUCE 4 Projucer. @jules: is this a bug or expected behaviour? (Or am I just missing something obvious?)
Build once to ensure that signing works as expected. Now close Xcode and open your project’s project.pbxproj in a text editor. project.pbxproj is inside your projects Xcode project package (so for the JUCE demo it’s located at JUCE/examples/Demo/Builds/iOS/JuceDemo.xcodeproj/project.pbxproj). Then search for DEVELOPMENT_TEAM =. This will be your developer id - make a note of it. For some reason this id does not match the one that Xcode shows.
You can now use the above id in the projucer and JUCE will correctly generate your xcode projects for signing with your developer id.
I’ve spent several hours to try to get a JUCE plugin to work correctly with application ID certificates. After trying all tricks described above, the only one that seems to work is to set the Mac Developer ID Application (from the key chain) and setting provisioning style to manual.
Perhaps the projucer can be updated as follows: if ‘Mac Developer’ is used as code signing identity, set the provisioning style to automatic (as it is now), while using ‘manual’ when a Mac Developer ID application is used?
This still seems to be an issue with Projucer 6. Could anyone from the JUCE team take a look at this? It’s merely a matter of setting “ProvisioningStyle” to “Manual” when a code-signing identity is specified in Projucer as far as I can understand?