I use Fork for source code control and it no longer reads the .xojo_project file to show me the individual code changes. It treats it like a binary file. Could be because, for some reason, my license keys disappeared in Xojo on my desktop computer. Without license keys you can’t work with .xojo_project files.
I downloaded my license keys and added them back. Am I going to recover this file now or will I have to do something else. Maybe save it to binary and then back to .xojo_project and then recreate git setup.
I did not lose the license keys on my MacBook so I can see if I can download the latest version there.
Are you saying save as binary to another folder and then save as xojo_project to yet another folder and then copy/overwrite to the original leaving to preserve the source code control status?
I copied my entire git parent folder to create a current snapshot. I then opened my masquerading binary project from the copied directory and saved as text project in the original git parent directory.
Turns out I hosed this up pretty good in the time between the licenses disappearing and when I realized that was the problem. I’m just going to trash it and roll back to the last version that was good. Luckily it’s not a lot of work and I do save binary projects frequently enough.
This has been happening to me for a few months whenever there’s a macOS Big Sur update. I think I read somewhere that Xojo thinks you’re on a different device after these updates. So I’ve formed a habit after every Big Sur update of logging into my Xojo account, deleting my licence “instances”, then going into Xojo and requesting a new licence (Xojo menu → License Keys → Update). They’re going to have to sort this out as it will begin to bite too many users.
This is very dangerous because it doesn’t tell you it’s saving as a binary file, but overwrites the .xojo_project file with the binary project. The only way to see is suddenly the xojo_project file is now several MB. I have to make sure I’m logged in and that the licences are present. Quite often the license is not added automatically from the account, so I’ve downloaded the .xojo_license file and apply that. Sometimes after that is asks to transfer the license (It’s the same computer, but updated) and I use the file.
Regards,
It should have saved them to the binary file. I definitely didn’t see any loss of changes. Once I re-saved the binary over the old project as text, everything was there and working. That’s really interesting and, obviously, unfortunate.
I’m going to have to watch that. This isn’t the first time it’s happened to me but the first since Big Sur. Can’t say I’ve used Xojo that much so haven’t be aware of this issue.
I caught this early because I use Fork for github. It wasn’t reading the project file detail and showed a warning in red saying something like “not LFS”. I knew something wasn’t right. Luckily I have a good backup system so I just restored the project.
Since several months (years?) now, when Xojo crashes, the ability of Xojo to recover unsaved changes is broken (in my experience, it now never works). I’d not be surprised to see unreliable behavior on saving.
This is turning into a horror show. What I did was I saved as binary into another folder. Opened that and converted to project file. Copied just the .xojo_project file back into the Git managed folder. Now it’s back to showing the project file as a single file.
