Post

Replies

Boosts

Views

Activity

Reply to Checking DMG notarization. Rejected, but works fine
Quinn, Thanks for your replies! My workflow is the following: Build my APP Codesign my APP Create a DMG from my APP Notarize DMG... Staple notarization to DMG Create ZIP from APP (from step 1) for Auto-Update Notarize ZIP... Staple notarization to original APP (from step 1) Delete ZIP Create a new ZIP from APP. Is it correct? I've understood about timestamp servers. I tried again a command from your article: spctl -a -t open -vvv --context context:primary-signature googlechrome.dmg and now it works on iMac (Intel) Big Sur 11.2.3. Earlier it didn't work on DTK with Big Sur 11.1.0
Topic: Code Signing SubTopic: Notarization Tags:
Mar ’21
Reply to Checking DMG notarization. Rejected, but works fine
Sometimes codesign for a DMG doesn't work correctly: codesign -s "Developer ID Application: COMPANY" --timestamp -i MyApp MyApp.dmg I got an error: "The timestamp service is not available." and DMG was not completely signed. APP bundle was signed correctly (a minute earlier) and notarized (several minutes later). I re-launched the script again and next time DMG was signed rightly.
Topic: Code Signing SubTopic: Notarization Tags:
Mar ’21
Reply to Checking DMG notarization. Rejected, but works fine
Another question. I build a special ZIP with APP bundle for Auto Update feature. This ZIP is being notarized. How I can check that APP bundle is notarized and a difference with only codesigned APP bundle? spctl -a -t exec -vvv MyApp.app always shows the same result for codesigned APP, regardless notarization: MyApp.app/: accepted source=Notarized Developer ID origin=Developer ID Application: COMPANY (RDPXXXXXX)
Topic: Code Signing SubTopic: Notarization Tags:
Mar ’21
Reply to Checking DMG notarization. Rejected, but works fine
Quinn, Thanks for your reply and advices! I added codesign for a DMG image. And then spctl shows that DMG is correct: MyApp.dmg: accepted source=Notarized Developer ID It seems that many Mac developers (including me) were not aware that it also necessary to codesign DMG in addition to codesigning of APP bundle and notarization. 2. Probably I found a typo in your article "Testing a Notarised Product". It says: Disk image spctl -a -t open -vvv --context context:primary-signature WaffleVarnish.dmg However this command shows nothing for any correctly notarized app (including my app, Chrome, Audacity, etc). If I add "-v" to your command: spctl -a -t open -vvv --context context:primary-signature WaffleVarnish.dmg -v It shows a result for Chrome: googlechrome.dmg: accepted source=Notarized Developer ID
Topic: Code Signing SubTopic: Notarization Tags:
Mar ’21
Reply to Problem with xcrun altool - CFURLRequestSetHTTPCookieStorageAcceptPolicy_block_invoke
Quinn, Thanks for your reply. I have no problem with notarization (it works) except of weird error about deprecated function in Terminal. I tried to exclude -p and enter password on request from Terminal. The same message appears. I don't use any quotas. Then I checked --list-providers as you suggested: xcrun altool --list-providers -u my@email.com -p mypassword 2021-01-27 14:03:25.616 altool[22323:119084] CFURLRequestSetHTTPCookieStorageAcceptPolicy_block_invoke: no longer implemented and should not be called ProviderName ProviderShortname PublicID														 WWDRTeamID WnSoft LLC	 WnSoftLLC				 69a6xxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx XXXXXXXXXXXX It would be nice if Apple could fix it to avoid confusion.
Topic: Code Signing SubTopic: Notarization Tags:
Jan ’21
Reply to Localization problem in NSOpenPanel
Thanks for your all replies. I found a solution: Localization doesn't work if I use a symbolic link to an executable file. The cross-platform compiler (Freepascal) created an executable outside APP bundle, and a symbolic link inside /MacOS folder. It seems to be a bug in macOS, because I run APP bundle and localization must work. So I copied manually real executable to /MacOS folder (as for a release version) and now everything works fine. 2. Also I discovered that I can use one of two options: A. Add CFBundleLocalizations records for each supported language. B. Or add an empty folder for each language in /Contents/Resources - fr.lproj , de.lproj , etc. Any of these variants for to use OS language in NSOpenPanel and NSSavePanel. I hope that this info will be useful for for somebody else.
Topic: App & System Services SubTopic: Core OS Tags:
Jan ’21
Reply to Localization problem in NSOpenPanel
All internal localization in my cross-platform app are stored in other files. I tried to add an empty fr.lproj folder in /Resources - no result. I checked VLC app with a correct NSOpenPanel. It contais fr.lproj in /Resources/ > InfoPlist.strings: CFBundleName = "VLC"; CFBundleDisplayName = "VLC"; CFBundleShortVersionString = "3.0.11.1"; CFBundleGetInfoString = "Copyright © 1996-2020 the VideoLAN team"; NSHumanReadableCopyright = "Copyright (c) 1996-2020 VLC authors and VideoLAN"; I added the same InfoPlist.strings file to my fr.lproj - the same result - everything in NSOpenPanel on English
Topic: App & System Services SubTopic: Core OS Tags:
Jan ’21