iOS 4.2 breaks flight plan – FIXED 03Dec10!
EDIT: Everybody please update to version 1.8 available on App Store now
For all those having problems with the keyboard on NAIPS when filing a flight plan:
Symptoms
- keyboard does not appear when you try and edit a field in flight plans
Cause?
- iOS 4.2 update changed the way the keyboard works. Sorry I couldn’t anticipate this until a couple of weeks ago.
Solution
- You can avoid upgrading to iOS 4.2 for a couple of weeks
- I submitted a fix to Apple on 18 Nov 10, so it should be released any day now.
- Keep checking the App Store for NAIPS update, then install it.
Advertisement
6 Comments »
Leave a Reply
-
Recent
-
Links
-
Archives
- December 2011 (1)
- April 2011 (1)
- January 2011 (1)
- December 2010 (1)
- November 2010 (2)
- July 2010 (2)
- May 2010 (1)
- February 2010 (1)
- January 2010 (3)
- December 2009 (1)
- November 2009 (3)
- October 2009 (2)
-
Categories
-
RSS
Entries RSS
Comments RSS
I have been having another problem with the flight planning section. When I submit a plan it always come up with 15 errors, virtually every field that I put data into. The data is in the correct format, but it always saya the same errors. Is this a know problem?
And yes, I am using the IOS 4.2. I have the exact same problem with the iPad and the iPhone.
Yep you need to put something in the Route page – even “DCT YPPF DCT” will do if that’s all your doing.
I’ve put a little message about that in the latest version so it should be a bit more obvious now.
Rowan.
Hi
Iphone 4, brand new.
App downloaded from App store 8pm 3/12/10
worked fine initially.
this morning it had the issue above…. no qwerty keyboard visible (number pad ok) Then whole app froze. Now after restart of phone app wont launch….. pic of aircraft on start screen only.
Any thoughts?
Update to (new)phone software fixed problem.
Hello Shagpile,
Please advise if you know of a support forum, iPad app (NAIPS) crashes when going back from inputing SSR, though not always. I do have a possible SIM issue (hoping to fix tomorrow), frustrating only but still keen to fix (works fine on iPhone).
Graham