Hi folks,
I have troubles launching the 2015R3 - see Mac OSX (10.8.5) complaining message. I’ve downloaded it several times.
I never had this with all releases before.
Is the R3 not code signed ? How can solve it without playing around with the security options ?
R3 is code signed, I get the correct messages here when running 10.10 (I have it installed on two different machines).
I’ve seen this on apps downloaded from MAS. It was fixed by removing the app, restart and then download and install again. Or something like that 
One other user reported this but so far it’s not something we can reproduce. We have tried multiple version os OS X and different machines and VMs.
You ought to be able to right-click on the app and select Open to bypass the security settings.
Perhaps it is a messed up cert in the keychain? It might be worth trying a different user account to see if the problem persists.
someone should run spctl on the damaged version and get more info.
I’ve seen that with other software in the following case:
The reason is that Images (such as in the Resources-Folder) become 2 Files on the FAT-formatted volume: “picture.png” and “._picture.png” (the resource fork part).
And because it’s the first launch after Downloading, GateKeeper tries to verify the contents - and is not delighted to see that there are more files in the App-Bundle (more than were signed -> the “._” files are not included in the signature).
That’s when one gets the “App is damaged and should be moved to Trash” message.
The only workaround here is to download/extract and first run on a os x formatted volume. only after that, copy an App to a windows-formatted volume. because GateKeeper has marked the App as “ok” when first run, it’ll continue to work on another volume.
We have seen this with our apps as well. Otherwise, 15r5 downloads and runs just fine here on 10.8.5, 10.9.5, 101.5, and 10.11.
I had nothing but bad luck trying to get the 2015r3 betas to launch on my Mac running 10.8.5 unless I disabled Gatekeeper. I have also installed lots of other applications recently and only Xojo has caused me problems.
For most of the betas I received a different problem to the one reported here but Xojo closed the case as the not reproducable. However, around b27 I started getting the same error reported here. I did request that the feedback case was re-opened so that I could add additional information but the request was ignored.
The following is what I had planned to add:
Error in console when trying to launch Xojo:
15/10/2015 13:10:35.312 CoreServicesUIAgent[25952]: Error SecAssessmentCreate: The operation couldnt be completed. (OSStatus error -67054.)
Result from: spctl --assess --verbose --raw /Applications/Xojo\ 2015r3b27/Xojo.app
/Applications/Xojo 2015r3b27/Xojo.app: a sealed resource is missing or invalid
I encourage anyone running into this to create a Feedback case with the spctl info. Maybe it will help shed light on the issue. If it’s a problem on our end, we’d sure like to get it corrected.
[quote=222625:@Kevin Gale]I had nothing but bad luck trying to get the 2015r3 betas to launch on my Mac running 10.8.5 unless I disabled Gatekeeper. I have also installed lots of other applications recently and only Xojo has caused me problems.
For most of the betas I received a different problem to the one reported here but Xojo closed the case as the not reproducable. However, around b27 I started getting the same error reported here. I did request that the feedback case was re-opened so that I could add additional information but the request was ignored.
The following is what I had planned to add:
Error in console when trying to launch Xojo:
15/10/2015 13:10:35.312 CoreServicesUIAgent[25952]: Error SecAssessmentCreate: The operation couldnt be completed. (OSStatus error -67054.)
Result from: spctl --assess --verbose --raw /Applications/Xojo\ 2015r3b27/Xojo.app
/Applications/Xojo 2015r3b27/Xojo.app: a sealed resource is missing or invalid[/quote]
Try running RB App Checker Lite on the app and see what it has to say.
Evaluating the application Xojo 2015r3b27.app.
The application was signed by Apple Root CA, Developer ID Application: Xojo, Incorporated (6MG2NQJ3FZ).
Both the verified timestamp and the signing-time are: 14 Oct 2015 23:58:54.
The object code format is bundle with Mach-O thin (i386).
Both bundle and signing identifiers are com.xojo.xojo.
The signature specifies implicit requirements.
The requirements specify the Team ID 6MG2NQJ3FZ.
The signature specifies resource rules (v1).
The signature specifies resource rules (v2).
Requirements and resources didn’t pass static validation.
Error details: #-67054 {
Resources missing:
Contents/Resources/SDKStubs/.DS_Store
Error in architecture: i386
}
The code signature contains a snapshot of the applications Info.plist.
Version 15.3.0.2.31532 (15.3.0.31532) Xojo 2015 Release 3
The code signature contains 3 certificates.
Certificate Apple Root CA:
Your keychain contains this trusted root certificate.
Will expire on 9 Feb 2035.
Certificate Developer ID Certification Authority:
Will expire on 1 Feb 2027.
Certificate Developer ID Application: Xojo, Incorporated (6MG2NQJ3FZ):
Will expire on 5 Nov 2018.
SHA1 fingerprint: DB0D91C036EFB618895E01BFF6331ED0AECD4D82.
Team ID or Organizational Unit: 6MG2NQJ3FZ.
This matches the Team ID specified in the requirements.
The application is probably from an authorized Apple Developer.
The application is not sandboxed.
734 auxiliary executables have been found.
680 are unsigned.
54 are signed by Apple Root CA, Developer ID Application: Xojo, Incorporated (6MG2NQJ3FZ).
182 frameworks are suspect: they use system names but are NOT signed by Apple!
712 executables are in the Resources folder.
Kevin- can you try with the now-shipping version- do you have the same problem?
Just downloaded and installed the release version and I still have the same problem.
It could be a coincidence but the first time I launched the executable I received a crash report in the console relating to CoreServicesUIAgent. After I had performed a force-quit on the app in the Dock and re-launched I got the same CoreServicesUIAgent error that I mentioned above.
The crash report is:
21/10/2015 19:35:55.870 CoreServicesUIAgent[66353]: +[NSURL fileURLWithFileSystemRepresentation:isDirectory:relativeToURL:]: unrecognized selector sent to class 0x7fff7207efa0
21/10/2015 19:35:55.870 CoreServicesUIAgent[66353]: An uncaught exception was raised
21/10/2015 19:35:55.871 CoreServicesUIAgent[66353]: +[NSURL fileURLWithFileSystemRepresentation:isDirectory:relativeToURL:]: unrecognized selector sent to class 0x7fff7207efa0
21/10/2015 19:35:55.878 CoreServicesUIAgent[66353]: (
0 CoreFoundation 0x00007fff83906b06 __exceptionPreprocess + 198
1 libobjc.A.dylib 0x00007fff83e303f0 objc_exception_throw + 43
2 CoreFoundation 0x00007fff8399d26a +[NSObject(NSObject) doesNotRecognizeSelector:] + 186
3 CoreFoundation 0x00007fff838f502e forwarding + 414
4 CoreFoundation 0x00007fff838f4e18 _CF_forwarding_prep_0 + 232
5 CoreServicesUIAgent 0x000000010e8d91de CoreServicesUIAgent + 33246
6 CoreServicesUIAgent 0x000000010e8d8d11 CoreServicesUIAgent + 32017
7 CoreServicesUIAgent 0x000000010e8d963d CoreServicesUIAgent + 34365
8 CoreServicesUIAgent 0x000000010e8d5fad CoreServicesUIAgent + 20397
9 CoreServicesUIAgent 0x000000010e8d7363 CoreServicesUIAgent + 25443
10 Foundation 0x00007fff8a3da532 NSThread__main + 1345
11 libsystem_c.dylib 0x00007fff8a130772 _pthread_start + 327
12 libsystem_c.dylib 0x00007fff8a11d1a1 thread_start + 13
)
21/10/2015 19:35:55.879 CoreServicesUIAgent[66353]: *** Terminating app due to uncaught exception ‘NSInvalidArgumentException’, reason: ‘+[NSURL fileURLWithFileSystemRepresentation:isDirectory:relativeToURL:]: unrecognized selector sent to class 0x7fff7207efa0’
*** First throw call stack:
(
0 CoreFoundation 0x00007fff83906b06 __exceptionPreprocess + 198
1 libobjc.A.dylib 0x00007fff83e303f0 objc_exception_throw + 43
2 CoreFoundation 0x00007fff8399d26a +[NSObject(NSObject) doesNotRecognizeSelector:] + 186
3 CoreFoundation 0x00007fff838f502e forwarding + 414
4 CoreFoundation 0x00007fff838f4e18 _CF_forwarding_prep_0 + 232
5 CoreServicesUIAgent 0x000000010e8d91de CoreServicesUIAgent + 33246
6 CoreServicesUIAgent 0x000000010e8d8d11 CoreServicesUIAgent + 32017
7 CoreServicesUIAgent 0x000000010e8d963d CoreServicesUIAgent + 34365
8 CoreServicesUIAgent 0x000000010e8d5fad CoreServicesUIAgent + 20397
9 CoreServicesUIAgent 0x000000010e8d7363 CoreServicesUIAgent + 25443
10 Foundation 0x00007fff8a3da532 NSThread__main + 1345
11 libsystem_c.dylib 0x00007fff8a130772 _pthread_start + 327
12 libsystem_c.dylib 0x00007fff8a11d1a1 thread_start + 13
)
21/10/2015 19:35:56.823 com.apple.launchd.peruser.501[377]: (com.apple.coreservices.uiagent[66353]) Job appears to have crashed: Abort trap: 6
21/10/2015 19:35:56.961 ReportCrash[66362]: Saved crash report for CoreServicesUIAgent[66353] version 95.11 (95.11) to /Users/keving/Library/Logs/DiagnosticReports/CoreServicesUIAgent_2015-10-21-193556_Kevins-MacBook-Pro.crash
[quote=222720:@Kevin Gale]Error details: #-67054 {
Resources missing:
Contents/Resources/SDKStubs/.DS_Store
Error in architecture: i386
}
[/quote]
Aha. That’s interesting.
IMHO it’s best to remove the .DS_Stores from an application as they only seem to cause pain.
I’ve used the AppQuarantine from http://brockerhoff.net
which solved me issued. I don’t what the tools modified but at least I can launch Xojo now.
[quote=222954:@Rob Egal]I’ve used the AppQuarantine from http://brockerhoff.net
which solved me issued. I don’t what the tools modified but at least I can launch Xojo now. :)[/quote]
Did you Set the quarantine or did you remove it?
[quote=222954:@Rob Egal]I’ve used the AppQuarantine from http://brockerhoff.net
which solved me issued. I don’t what the tools modified but at least I can launch Xojo now. :)[/quote]
It removes the Quarantine extra attribute from the application, then GateKeeper doesn’t kick in and check the application. Same as disabling GateKeeper in the Security settings of the System Preferences.
Which web browser are you using?
Ive been getting reports of this for some of my apps once I started actually code signing them, yes Im a little behind. The same message that the app is damaged if they have the allow only registered developers turned on. It doesnt happen all the time though which is strange, perhaps people dont really know what their settings are 
I just ran the app in question through the aforementioned RBAppChecker and it reports this error on the xojo framework file, does this make any sense? Everything else in the output looks fine. I used App Wrapper to code sign everything if that has anything to do with it I dont know.
removed the quarantine (form Safari).