Cobra wrote:
Three were numerous posts on the forum here around the end of the year last year regarding this behavior. The explanation was that one of the tools used in building the software package had a license that expired, and as a result builds that were done with the tool using that older license stopped working after the expiration date (or something along those lines).
Current version 11 software was built using a renewed license and so the problem doesn't affect those versions (though, presumably, at some point in the future these versions will also stop working when the license expires).
It's a side effect of modern software licensing. You never "own" the software you "buy"...you only rent it for a while. In this case, it's an indirect effect--Adventure Pilot doesn't "own" all the software tools they use to create iFly, and so they can't guarantee that older versions of iFly will "work forever".
Cobra, I think this is the first time you've made a post (that I can remember) where I disagree with your conclusion. :) I could be thinking of different symptoms, so I could be wrong here.
The issues as end of last year had to do with our "build machine"... we swapped to a new machine, but forgot to transfer the license for one component - which made it build in 2-week-time "trial" mode. The issue was embedded as a warning inside 1000's of lines of text, and so we missed it. Once we figured out the cause, we just installed the license on that new build machine, and all was well again. This issue only impact iFly GPS version 11, for those initial production builds. Unless someone is installing a previous production build of version 11 (which isn't available on the PlayStore or anywhere), this shouldn't be the issue here.