[The issue was detected by a customer who sent this email]
I just bought your course, installed it, but when it comes up it doesn’t show anything. I have a sneaking suspicion that this was written on a case insensitive file system. Therefore your file names that are opened in your program does not case match the files on the disk.
I have 6 macs in the house. 2x Mac Pros, 2x Mac Minis and 2x MacBook Pro Retinas. Unfortunately none of them have a case insensitive OS on it. Everytime we buy a Mac, the first thing we do is Erase the drive and convert to Mac OS X, Case Sensitive, Journaled, so the way your program is I’ll never be able to run it.
Being a Mac developer myself (and a software developer retiree from [company name] after 40 years) I can recommend that you have your development machine a case sensitive file system. Every system developed on a case sensitive file system will work on a case insensitive one. The reverse is not true. In all my purchases, which are considerable, I have run into exactly three instances where Mac software failed to work on a case sensitive system.
1) eMedia company tutorial software (I contacted them and unfortunately, they said, their framework is the same for all OSs, and it is not case sensitive safe.
2) PreSonus, I purchase FaderPort from them and it wouldn’t install. However since I only had to install faderport bundle I did it manually. Just for your edification, what they did wrong was, they created a directory called “MIDI Device Plug-Ins” where it should have been “MIDI Device Plug-ins”. Notice “Ins” vs “ins”. So it didn’t work on a case sensitive system.
3) XpressPads s/w. Now I could probably do a “strings” on the executable, find the names of the files and then rename them accordingly in the package contents, but I don’t feel like fighting that battle.