CoreCode

thanks for the confirmation! i do not believe there is a connection to Sparkle issues. they have always ignored the 'real' code-signature but their recent releases require (Ed)DSA signatures which...

> Almost certainly that causes the auto-update to fail (going from the old signed-build to the new signed-build). nope, should be ok. Sparkle signatures are completely different to the macOS-native...

hm. the new build is again signed by an "Apple Development" certificate. thats no good. it needs to be signed with a "Developer ID" certificate...

``` codesign -dvv /Users/cc/Downloads/TextBar.app Executable=/Users/c/Downloads/TextBar.app/Contents/MacOS/TextBar Identifier=com.RichSomerfield.TextBar Format=app bundle with Mach-O thin (x86_64) CodeDirectory v=20500 size=7334 flags=0x10000(runtime) hashes=218+7 location=embedded Signature size=4868 Authority=Apple Development: Rich Somerfield (H626MD25P8) Authority=Apple Worldwide Developer Relations Certification...

ugh those Apple geniuses. the 'Apple Development' certificate is correct - if you want to upload the package to the Mac App Store. however if you want to distribute directly...

definitely.

awesome, thanks!

the CFBundleGetInfoString entry needs to be removed from your Info.plist this has been deprecated for more than 10 years the CFBundleVersion / CFBundleShortVersionString entries should be set to something that...

this is NOT fixed in version 7.7.0 please re-open

i'm not saying it is a major bug or significant. still even if it isn't a dealbreaker, it should be fixed: • every Mac user expects to be able to...