I have used Xojo for many years and never seen this. About 2 weeks ago it started that when I build an app, it will run. But after reboot, it will not run. There is box that says app cannot be opened due to a problem, check with the developer to make sure this app works with this version of OSX.
I have recently put on Yosemite, but not sure if that is a direct cause and effect. Below are a section of the report.
I have multiple apps that no longer boot on OSX Yosemite 10.10.1. Each time I want to use the apps, I have to build after each boot up and they work fine until restart or power on. Can someone offer any advice on how to solve this?
OK so it is a dropbox related problem. My collaborator and I have been using dropbox for a long time without issue(both on Mac, both on the lastest Yosemite but I have a Mac Pro tower and my collaborator is on Mac Book Pro). This is a recent issue within the past few weeks, coincidentally after moving up to Yosemite. If I drag that droxbox build and content to the desktop, it still fails. But if I drag the Xojo project and content to the desktop and make a fresh build, then it will restart. This is a work around but certainly will make for lots of hassles collaborating. At least this solves the bigger immediate problem though.
For what it’s worth, I ran into something similar to this a few months ago. Dropbox is not syncing the frameworks properly. It copies them, the OS no longer sees the framework as a bundle, but just as a folder.
I ended up having to change how I was using Dropbox because of this. I still maintain the project repository in Dropbox, but the build folder has to be in a local, non-synced folder. Then, if we have to place a .zip archive of the build application back into Dropbox in order to share between systems.
If building a project that is located on drop box creates an app that does not work but copying the project locally & building works then this suggests “something” about dropbox is at fault.
Can’t tell you what though as I dont know
One of the most obvious reasons would be that DropBox uses a non Mac OS file system. So no permissions, and broken bundles. Your app does not start because building on an alien file system breaks all permissions within. Just as if one builds on PC, opens the Tar archive and copies the result.
Dropbox or any cloud folder for that matter is bad for saving projects and building. The issue has been documented many times.
Copy the project folder to your local disk and everything will be fine.
I guess this is a Dropbox+Yosemite problem because it started when I upgraded to Yosemite. The only strange fact is this only appear to happens with Xojo applications and, specifically, with the Xojo.framework. Though I didn’t test extensively with other applications.
Now, I tried to compare a such “damaged” application with another identical but residing outside Dropbox.
I compared all files in the bundle byte by byte and the two applications are IDENTICAL.
In fact, just copying the “damaged” application in another place and then replacing the original one with the copy, solve the the problem. Not the same moving the application somewhere else and then moving it again on Dropbox: still doesn’t work.
I also tried to check the validity of the Xojo.framework signature with codesign. Again it’s valid.
Hence, the problem must be somewhere else than the binary…
I’d like to spot where the problem is, just to give some hints to the Dropbox+Apple guys on solving the problem.