APDL and Logbook Pro for Android are now in public beta. Click here to join the public beta and install the latest versions today.

Reply to thread

Message: [QUOTE="Neal Culiner, post: 20655, member: 1"] Eric, I apologize for the delay in investigating this issue for you. The schedule importer can pickup A/C Type and Ident data if it's provided by your trip provider. Our parser was picking up "N/A" for the N-Number in your particular case. I updated the schedule importer to check for N/A and remove it so the app, when it receives the trip data, will continue to process your defaults or recent recall settings, as specified. This issue is NOT an issue with the app but instead just something peculiar with your trip data. Most likely if you have trip data stored in your cloud account you'll need to clear those trips and reprocess the trip data again. You can then delete the prior trips in your app and reimport them. Let me know if this resolves your issue. Thank you for using the forums so others can learn from your situation. [/QUOTE]