Is anyone signing and notarizing their compose desktop macOS app? There seems to be a regression af...

# compose-desktop

[Carter]

Is anyone signing and notarizing their compose desktop macOS app?

There seems to be a regression after upgrading from compose 0.3.1 and Kotlin 1.4.30 to compose 0.4.0-build182 and Kotlin 1.4.32

It compiles, signs, and uploads, but notarization is rejected by Apple a few minutes later. When I dig into the server logs from Apple, the error message is

"statusSummary": "Archive contains critical validation errors",

and

"message": "The signature of the binary is invalid.",

If I roll back to compose 0.3.1 and Kotlin 1.4.30, then the signing issue goes away again.

Is signing broken with the newer version, or did something change with how we’re supposed to configure the gradle build DSL for signing?

[olonho]

Does this problem exist in 0.4.0-build180?

[Carter]

Notarization also fails with build180, so it seems like the regression happened a while back.

[alexey.tsvetkov]

@Carter the issue should be fixed once https://github.com/JetBrains/compose-jb/pull/603 is merged

[Carter]

Awesome, thank you so much for the update and for pursuing a fix for this issue. I’ll look forward to this getting merged and included in an upcoming update.

[Carter]

I just successfully notarized my app with Compose 0.4.0-build185! 🦜