I have experienced sync problems between my iPad and my iPhone after completing my last few trips. I was hoping the issues would have been resolved in the most recent release, 7.0.8. Unfortunately, I just completed a trip and the sync problems still occurred. After reading pcohens issues here is what I did to hopefully eliminate the possibility of a sync problem. I entered all of my actual trip data (OUT, OFF, ON, IN, position, instrument, etc) on my wifi only iPad after each leg. I made sure to save the data for each leg. When I got home, connected to wifi, I synced my data. At this point I launched APDL on my iPhone. APDL was not launched on my iPhone at all during my trip and was not even running in the background. Obviously, when I opened APDL, it automatically synced my data. Unfortunately, I received alerts that I had open flights. I looked at the trip data for the trip I just completed and sure enough the actual OUT and IN times were blank, the instrument time was zero and the release time was reset to the original scheduled release. The odd thing is that the OFF and ON times and my position had synced correctly. I went back to my iPad, opened APDL which started an automatic sync and sure enough, the exact same thing happened to the trip data on my iPad.
Has anyone else experienced this issue? Neil or any of the software engineers, are you aware of this issue or are you able to replicate? If so, is there a work around or do you have any suggestions?
As much as I want APDL to work (I have been anxiously waiting for a long time), it seems to be extremely buggy. I feel like I am back in my engineering days, alpha and beta testing software and firmware. Except for the fact that in this situation I do not have access to the software or the software engineers. I have to admit, at this point I am kind of disappointed and unless some of these major sync and legality issues are fixed, I feel like I will be forced to continue using APDL on my Palm Treo and look for an alternative for tracking my 117 legality.
Eric
Has anyone else experienced this issue? Neil or any of the software engineers, are you aware of this issue or are you able to replicate? If so, is there a work around or do you have any suggestions?
As much as I want APDL to work (I have been anxiously waiting for a long time), it seems to be extremely buggy. I feel like I am back in my engineering days, alpha and beta testing software and firmware. Except for the fact that in this situation I do not have access to the software or the software engineers. I have to admit, at this point I am kind of disappointed and unless some of these major sync and legality issues are fixed, I feel like I will be forced to continue using APDL on my Palm Treo and look for an alternative for tracking my 117 legality.
Eric
Last edited by a moderator: