“missing package product”

I'm working with a number of multi-platform apps that have local packages, and sometimes have your problem because I'd forgotten key steps. For each Target (platform), build the Library (package) before building the main product of that target (e.g. MacOS). You will probably have to rebuild the Library (package) after any Clean Build Folder. For each target, at the General tab of the Target explorer, make sure you've included the library (package output) in the Frameworks, Libraries and Embedded Content. Each target needs to have the Library specified, not just once at the project level. I've had problems with local packages when I've included the source(s) in my app's project, rather than having the package in a separate directory and included in the app project. Best wishes and regards, Michaela

You archive a dynamic library using the standard process, so Product > Archive, but you’re correct that you can’t distribute a dynamic library from Xcode. Most of the time that doesn’t matter because you don’t need to sign and notarise a dynamic library. Rather, someone who uses your dynamic library in their product is expected to sign and notarise it as part of their distribution processing. In some cases it is necessary to do this, for example, when you’re creating a plug-in for some other app. In such situations you must manually sign, package, and notarise your product. For advice on how to do that, see: Creating Distribution-Signed Code for Mac Packaging Mac Software for Distribution Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

I think the problem is due to the container schema that's not deployed to the production environment. Strangely everything works except the sharing functionality. But now the question is: if I deploy to the production environment the users will lose their data?

For more up-to-date advice on how to sign and package Mac products, for both the Mac App Store and independent distribution using Developer ID, see: Creating Distribution-Signed Code for Mac Packaging Mac Software for Distribution Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

From TN2413 In-App Purchase FAQ > How do I create a hosted non-consumable product?There is a current bug that prevents Xcode 6 from uploading hosted content to iTunes Connect. To workaround this issue, use Application Loader to upload a package containing your hosted content. See below for steps on how to do so:In the Xcode Archives Organizer, select the archive containing your hosted content.Click Export.In the dialog that appears, choose Export as an Installer Package.Click Next to start generating your package, then select Export to save your package (a file with a .pkg filename extension).Use Application Loader to upload the above package. See Using Application Loader for more information about it.

Thank you for your inputs.What bothers us with notarization requirements is that there is no way to test it.You know, testing is fail first, understand the why, then fix.We did put our product on macOS 10.14.5 beta and public release, and we though we were be able to fail there, but we never experienced a failure to demonstrate that notarization helped us to fix it in order to have it run.Implementing notarization in our context represents some kind of work, as we currently build and package our bundles with a build agent.In order to prioritize the implementation of the notarization process in our automated build workflow, I have to explain the why to my product owner and my stakeholder.Currently the why is only because Apple told us to do it, not because we are able to reproduce the failure on macOS beta software by not doing it.If I follow you clearly on the user testing workflow you are suggesting, we will surely encounter a failure.But that won't be a testing failure in the Gate

This worked for me:1. Use XCode 7.3.1 (not the Xcode beta) to archive.2. Go to the archive file > Show Package Contents > Products > Applications > {AppName} > Show Package Contents > Info.plist3. Change `BuildMachineOSBuild` to 15G31 (or the most up-to-date prod build number of the macOS) and save it.4. Now export this archive for iOS App Store Deployment5. Forward the .ipa file to a co-worker who runs production version of the macOS.6. Use Application Loader to upload the .ipaLesson learnt: Do not update the macOS to beta version on your primary development machine.