XojoTempSigning folder in a built app?

General
1

Hi,

Xojo seems unable to build my project correctly. The resulting app has two folders in the first level of the “.app” bundle: “Contents” and “XojoTempSigning”.
“Contents” only has “Resources”, which contains a single folder from a build step; that folder is empty, so “Contents” itself weights only 8 KB.
On the other hand, “XojoTempSigning” contains a single folder, “Contents”, which is the real folder containing the correct app (but, obviously, at a wrong place). It looks to me like the Xojo signing process failed to finish correctly.

Just wondering whether someone already saw that and understands what’s going on. :man_shrugging:

2

Hi @Arnaud_N

  • What macOS and Xojo versions?
  • What values have you used for signing?
  • Are the certificates still valid?
  • Is some “pending to agree” stuff at the Apple side of your developer account?
  • Are there post-build scripts involved?
  • Is your project saved to a folder that can, somehow, interrupt the signing? (I.e: synced folders / disks)
1 Like
3

Hi Javier,

Thanks for your reply.
• Mac OS Tahoe 26.2 and Xojo 25.3.1.66632.
• Signing isn’t enabled (it’s an in-house app, and I don’t sign it every time); yet, I see a “Signing…” phase on building.
• There’s a build step involved, used to copy 3 folders inside the “Resources” folder. No other.
• The folder holding the project isn’t synced, though it’s a network share.

4

Because of macOS, the IDE still does an ad-hoc signature. Otherwise the app wouldn’t even run locally.

1 Like