Post

Replies

Boosts

Views

Activity

Reply to xcodebuild linking error fille cannot be open()ed, errno=2
OK this line of code seems to have tripped Xcode up resulting in the above errors DebugLog("No planogram fixtures for \(level.store.code).\(\(level.store.number))") Note that the typo wrapping the 'level.store.number' twice - coupled with the fact that number is not a property on store seems to have been enough to confuse the compiler as no compiler error was being shown. Not sure why that code error suddenly started showing up now which allowed me to fix it. Seems the error above is indicating that some source file has failed to build so start by tracking down the file and look for the code error the compiler hasn't been displaying an error for.
Oct ’24
Reply to Checking DMG notarization. Rejected, but works fine
It is beyond baffling that there is no simple explanation of the steps that are required. Every explanation in the Apple documentation and in online explanations are fragmented and disjointed and appear to always omit some critical step. Like "notary tool doesn't require a signed DMG" - well OK but does Gatekeeper not require a signed DMG? Why does the Apple example of customising the Xcode archive process make no mention of Stapling anything - not in the document nor in the sample script ? Why is that - is stapling something that is optional - if it is not optional why is it not included in the sample script ? Similarly the sample script doesn't code sign the DMG file - why not ? Surely the sample script should produce a DMG file that is ready for distribution ? Hopefully I am just missing something simple here.
Topic: Code Signing SubTopic: Notarization Tags:
Mar ’25