That would only apply to the packed .dmg file.
The contents of the .dmg, i.e. the app itself, should not be changed and should not lose any attributes?
I think so, too. But maybe worth a test if this packed .dmg makes a difference.
You were right. If we add this attribute after downloading, everything works fine.
Unfortunately, this doesn’t solve our problem if we want to update seamlessly via Sparkle, but at least it’s a workaround.
1 Like
Looks like that Apple is cracking down behaviors like a not authorized software (like anything not App Store 
) that connects to the internet and bring in another executable (like Trojans does).
No, the intent is not new. But downloading an app from a website or a socket usually means that it needs to be moved manually to the apps. If not the app is translocated. The app should always start.
Nope. From a website, downloaded clearly by an user intent, is one thing, they even have a flag for that, but downloaded by some automation from the guts of an app MAY be something improper, like virus or Trojan. That’s looking from the bright side of life, because from shades they may have started to block such things to force all updates using their official “services” from their store and forcing people to pay all the fees they want for anything, also increasing the hard time for sideloading.
I guess that if it were due to an Apple policy based on the way we update software, then none of our applications would work.
However, it only doesn’t work for two applications the other 11 work fine.
All applications also use the same plugins, same Xojo version.
1 Like
Those 2 contain something that triggers the behavior. Something makes them different from those other 11. Any chance of compiled with different Xojo versions (different SDKs) or different plist keys? Or maybe it is just something from the internal structures and included resources. Something in the contents is triggering the different behavior if all them uses the same engine and one is trapped in one machine, and another one is not, on the same machine. And this trigger may be a new trigger, so Apple side if confirmed.
Also use latest Sparkle for Tahoe enhanced compatibility, 2.8.1+