I just downloaded Xojo 2015 R3 and installed on El Capitan? in which I can getting the following error upon launch:
- “You can’t open the application “Xojo” because PowerPC applications are no longer supported”
Now thats funny because there is no PPC code in it
server:~ npalardy$ lipo -info /Applications/Xojo\ 2015\ Release\ 3/Xojo\ 2015r3.app/Contents/MacOS/Xojo
Non-fat file: /Applications/Xojo 2015 Release 3/Xojo 2015r3.app/Contents/MacOS/Xojo is architecture: i386
server:~ npalardy$ lipo -info /Applications/Xojo\ 2015\ Release\ 3/Xojo\ 2015r3.app/Contents/Frameworks/*.dylib
Non-fat file: /Applications/Xojo 2015 Release 3/Xojo 2015r3.app/Contents/Frameworks/AppearancePakCocoa.dylib is architecture: i386
Non-fat file: /Applications/Xojo 2015 Release 3/Xojo 2015r3.app/Contents/Frameworks/Crypto.dylib is architecture: i386
Non-fat file: /Applications/Xojo 2015 Release 3/Xojo 2015r3.app/Contents/Frameworks/GUIKitCocoa.dylib is architecture: i386
Non-fat file: /Applications/Xojo 2015 Release 3/Xojo 2015r3.app/Contents/Frameworks/HTMLViewerCocoa.dylib is architecture: i386
Non-fat file: /Applications/Xojo 2015 Release 3/Xojo 2015r3.app/Contents/Frameworks/IDEUtils.dylib is architecture: i386
Non-fat file: /Applications/Xojo 2015 Release 3/Xojo 2015r3.app/Contents/Frameworks/InternetEncodings.dylib is architecture: i386
Non-fat file: /Applications/Xojo 2015 Release 3/Xojo 2015r3.app/Contents/Frameworks/OpenSSLPlugin.dylib is architecture: i386
Non-fat file: /Applications/Xojo 2015 Release 3/Xojo 2015r3.app/Contents/Frameworks/PluginBridgeCocoa.dylib is architecture: i386
Non-fat file: /Applications/Xojo 2015 Release 3/Xojo 2015r3.app/Contents/Frameworks/RBScript.dylib is architecture: i386
Non-fat file: /Applications/Xojo 2015 Release 3/Xojo 2015r3.app/Contents/Frameworks/REALSQLDatabase.dylib is architecture: i386
Non-fat file: /Applications/Xojo 2015 Release 3/Xojo 2015r3.app/Contents/Frameworks/RegEx.dylib is architecture: i386
Non-fat file: /Applications/Xojo 2015 Release 3/Xojo 2015r3.app/Contents/Frameworks/SQLiteDatabase.dylib is architecture: i386
Non-fat file: /Applications/Xojo 2015 Release 3/Xojo 2015r3.app/Contents/Frameworks/SSLSocket.dylib is architecture: i386
Non-fat file: /Applications/Xojo 2015 Release 3/Xojo 2015r3.app/Contents/Frameworks/Shell.dylib is architecture: i386
Non-fat file: /Applications/Xojo 2015 Release 3/Xojo 2015r3.app/Contents/Frameworks/SpawnCompiler.dylib is architecture: i386
Non-fat file: /Applications/Xojo 2015 Release 3/Xojo 2015r3.app/Contents/Frameworks/XML.dylib is architecture: i386
Non-fat file: /Applications/Xojo 2015 Release 3/Xojo 2015r3.app/Contents/Frameworks/libGzip.dylib is architecture: i386
I believe you… that is why its odd.
here is a screenshot:
I’m getting all kinds of weird crash reports from users on El Capitan, none of which occur in our testing environment. It’s actually really starting to piss me off. If you have a Yosemite backup, try booting from that and seeing if that solves your problem.
Is this the final release from Xojo.com ?
Over the weekend, I did a fresh install of El Capitan. The strange part now is, I just rebooted and its launching just fine.
here is an error report from the logs:
[quote]10/21/15 9:38:10.092 PM CoreServicesUIAgent[1414]: Application failed to launch (id = com.xojo.xojo, version = 15.3.0.31581 reason = kLSNoRosettaEnvironmentErr)
com.apple.message.result: failure
OSActivityID: 0x000000000001dbfd
com.apple.message.domain: com.apple.launchservices.launchfailures.rosetta
com.apple.message.signature: com.xojo.xojo - 15.3.0.31581
SenderMachUUID: 97895A5B-E71E-3B6D-9D88-59CEDEFBE7A5
[/quote]
that is where I downloaded from. can someone download from the main link to confirm? the file downloaded is Xojo2015r3.dmg
Sounds more and more like Windows… Have you tried turning it off and on again?
So much for a “speed and stability” release
definitely an oddity with El Capitan.
thank you everyone for your input. It’s working now.
ElCapitan has done all sorts of weird low level things to me. Eagerly awaiting the .1 release…
There was something wrong with your version. The picture you posted shows Xojo.app being dated October 16, 2015 at 6:15 PM.
The final release I downloaded from Xojo.com is dated October 17, 2015 at 12:15 AM.
Only the latest beta, before FC1, that is two releases away, is dated Oct. 16.
Patiently waiting til they hit .2, 3. or maybe 4 
I’m going to have to make the jump, I’ve got too many customers with errors that are simply not happening on the two El Capitan test machines. Only machines left are my work machine and base test machine (which stays with it’s original OS).
[quote=222862:@Sam Rowlands]Out today! http://www.macrumors.com/2015/10/21/apple-releases-os-x-10-11-1-el-capitan/
I’m going to have to make the jump, I’ve got too many customers with errors that are simply not happening on the two El Capitan test machines. Only machines left are my work machine and base test machine (which stays with it’s original OS).[/quote]
Have been running it as a beta for a while. 10.11.1 seems much better. Given the random nature of certain things reported here, though, I simply hope it holds.
I too get users complaining about errors. Mostly related to specialfolder issues. I cannot reproduce it my test machines.
Fingers crossed if it is fixed for 10.11.1
[quote=222862:@Sam Rowlands]Out today! http://www.macrumors.com/2015/10/21/apple-releases-os-x-10-11-1-el-capitan/
I’m going to have to make the jump, I’ve got too many customers with errors that are simply not happening on the two El Capitan test machines. Only machines left are my work machine and base test machine (which stays with it’s original OS).[/quote]
and a new version of XCode… heck shall I install it or not? Will Xojo iOS Apps work with it…
They should.
if not, I will try out one of these new emojii symbol, guess which one 
Are those customers on Admin or Standard Accounts? The problems might be related to the new rootless security and / or System Integrity Protection
For example I noticed that you are not able to create certain folders in El Capitan if they do not exist already (like certain libs folders), not even using sudo in the terminal.
Yes, thats the new System Integrity thing. Just hiding the Library folder and locking the system out except for root wasnt enough We have to remove root access to those things too. You can turn it off, but it requires booting to safe mode and doing some terminal commands, hardly something you can ask users to do if there is something your program doesnt like.
Im not sure how they even update the system if even my authenticating to root wont let me write to them. Do we have root and SuperRoot now? I should read up how that works…