Chime 4 Breakfast 1.2.2
Accessibility identity fix
This release fixes the case where Chime reported "No access" even though Accessibility was enabled in System Settings.
Root cause
Local Xcode and DerivedData builds used the same bundle identifier as the downloaded app, but had a different code signature. macOS correctly treated the running build as a different Accessibility client, while the login item could keep launching that temporary copy.
What changed
- Normal source builds are now clearly named Chime 4 Breakfast Dev.
- Source builds use the separate identifier
app.chime4breakfast.debug. - Only the signed Distribution build owns
app.chime4breakfast. - Debug signing and launch scripts no longer replace or reset the downloaded app.
- CI now prevents these identities from ever collapsing again.
Update
Quit Chime 4 Breakfast, open the DMG, and replace the existing app in Applications. The Developer ID identity is unchanged, so the existing Accessibility grant should remain valid.
Apple notarized and Gatekeeper verified.
SHA-256: c3fa02678700a7bc075f7384dfae33ed16a95e1541f9e3d550d17b2e55b806c6