i’ve been testing the new release of our desktop a...

# compose-desktop

[Mario Javier Medina Cocom]

i’ve been testing the new release of our desktop application and several of my coworkers and i are seeing this error, what could be causing it?

[Oleksandr Karpovich [JB]]

What Compose version was used to build the app?
Does this or similar error occur on intel mac?
Does it happen only for packaged app or when running from the code too?

[Mario Javier Medina Cocom]

1 - compose 1.3.1-rc01

[Mario Javier Medina Cocom]

2 - Yes same error with intel

[Mario Javier Medina Cocom]

3. its only happening for packaged

[Oleksandr Karpovich [JB]]

If I'm not mistaken we had skiko updated later.
If you have a chance to try 1.3.1 that would be great

[Mario Javier Medina Cocom]

sure, i will try. thanks

[Oleksandr Karpovich [JB]]

I'm wondering if this is related to the issue described above. When a signed app on Mac was enforcing the entitlements.
https://kotlinlang.slack.com/archives/C01D6HTPATV/p1678957583077879?thread_ts=1678880842.552899&cid=C01D6HTPATV


I'll try to find out

[mikehearn]

I commented elsewhere, but the cause here is a signature mismatch. If you sign without disabling Apple's library validation feature then you can get this error. Compose Desktop tutorial tells people to disable this feature but Apple claim Gatekeeper will treat such apps to more extensive checking because they're less secure.

[mikehearn]

One fix is for Compose to delete and re-extract the library if it can't be loaded from the cache.

[mikehearn]

I have used one of my Apple DTS tickets to ask them what exactly Gatekeeper might do differently/when it might block the app, if library validation is disabled. This is relevant for CfD users who also don't use Conveyor, because the CfD gradle plugin tutorial tells you to turn this security feature off. If Apple don't like it, it's a problem, but their docs are vague.

[mikehearn]

I'll let you all know what they say.