CodeKit lost all projects and wont save new ones.

[JoshCarey]

Hi there. I just installed 2.8 yesterday (per the prompt I got). I went to add a new project today and when I did, it seemed to have deleted all my other projects. Then when I try to add one of my other projects back, it switches to that project as expected, but then there are still no other projects in the list.

Another curious thing... When I happened to look in my downloads folder, I saw the CodeKit app there, and not in its proper "Applications" folder location. I quite CodeKit, dragged it back into Applications... then I tried to add another project, but still the same result. This seems really strange.

[bdkjones]

Hit the "refresh all projects" menu item to get the list back. This affects only outdated versions of OS X. Update your Mac to 10.11 and you'll be all set.

Sent from my iPhone

On May 11, 2016, at 11:38, Josh Carey notifications@github.com wrote:

Hi there. I just installed 2.8 yesterday (per the prompt I got). I went to add a new project today and when I did, it seemed to have deleted all my other projects. Then when I try to add one of my other projects back, it switches to that project as expected, but then there are still no other projects in the list.

Another curious thing... When I happened to look in my downloads folder, I saw the CodeKit app there, and not in its proper "Applications" folder location. I quite CodeKit, dragged it back into Applications... then I tried to add another project, but still the same result. This seems really strange.

— You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub

[JoshCarey]

Man, the weird thing is - I did hit "refresh all projects" a couple different times, with no luck. Then all of a sudden, they're all back.

So what you're saying is that this might be an intermittent issue until I update OSX?

[bdkjones]

Yep. Gotta keep OS X up to date.

Sent from my iPhone

On May 11, 2016, at 11:58, Josh Carey notifications@github.com wrote:

Man, the weird thing is - I did hit "refresh all projects" a couple different times, with no luck. Then all of a sudden, they're all back.

So what you're saying is that this might be an intermittent issue until I update OSX?

— You are receiving this because you commented. Reply to this email directly or view it on GitHub

[chris-scheurle]

@bdkjones wrote: Hit the "refresh all projects" menu item to get the list back.

That doesn't work.

When the list is empty but there is still one project selected at start, hitting the "project settings" button seems to do the job of getting all projects back.

When there is no project selected, one can either try hitting "refresh all projects" and after that restarting CodeKit a couple of times (I just did that one 10 times in a row with zero effect) or re-add one project, then hit the "project settings" button.

@bdkjones wrote: Yep. Gotta keep OS X up to date.

Frankly: no, you don't. At least not while your system is actively maintained by it's vendor. And there are plenty of reasons why one either wouldn't want to or simply can't update to the most current release.

So, would it be that hard to find a way to fix this, either by just not using whatever 'fancy' OS X functionality is causing the issue, or by checking for an empty projects list on start and then automatically updating said list (the necessary information has to be somewhere, otherwise it couldn't "come back" after hitting this or that button)?

[bdkjones]

Hi Frank. You're welcome to continue running an outdated version of OS X. But if you do that, then you need to install and run CodeKit 2.7.1.

The bottom line is simply this: I have no idea why this issue is now happening on older releases of OS X. It has something to do with CodeKit 2.8 being built against newer versions of the Foundation and Cocoa frameworks that ship with 10.11 and Xcode 7.3. Apple obviously changed something that broke backwards compatibility. There is nothing 'fancy' that CodeKit is using. I'd have to track down what Apple broke and then hack a workaround for it.

I'm finishing up CodeKit 3 and I'm a one-man shop. The VAST majority of my users keep their Macs up-to-date. So investing hours of my time trying to figure out what Apple broke that causes this on ancient releases of Mac OS X is simply not worth it. CodeKit 3 will require OS 10.11+ anyway and El Capitan is vastly improved compared to Yosemite—animations are smoother, hundreds of things are fixed, etc.

So rather than waste time on this, I made the 2.8 update broadcast only to folks that are on the latest release of OS X.

[bdkjones]

I understand your frustration. But I have to make smart choices where I invest my very limited development time. This little issue isn't one of them, with CodeKit 3 right on the horizon.