-- Start simulator log -------------------------------------------------------
[INFO] Application started
[DEBUG] Reading stylesheet from: /Users/egomez/Library/Developer/CoreSimulator/Devices/D2DD3F81-EDBF-4C3B-A975-A41501FF3702/data/Containers/Bundle/Application/AE4C1686-4155-44A9-A3F5-AF463281A0F4/TableViewRepro.app/stylesheet.plist
[DEBUG] 2015-03-23 16:01:38.614 TableViewRepro[10909:330239] You've implemented -[<UIApplicationDelegate> application:performFetchWithCompletionHandler:], but you still need to add "fetch" to the list of your supported UIBackgroundModes in your Info.plist.
[DEBUG] 2015-03-23 16:01:38.615 TableViewRepro[10909:330239] You've implemented -[<UIApplicationDelegate> application:didReceiveRemoteNotification:fetchCompletionHandler:], but you still need to add "remote-notification" to the list of your supported UIBackgroundModes in your Info.plist.
[INFO] TableViewRepro/1.0 (4.0.0.944c821)
[DEBUG] Loading: /Users/egomez/Library/Developer/CoreSimulator/Devices/D2DD3F81-EDBF-4C3B-A975-A41501FF3702/data/Containers/Bundle/Application/AE4C1686-4155-44A9-A3F5-AF463281A0F4/TableViewRepro.app/app.js, Resource: app_js
[DEBUG] Application booted in 415.318012 ms
[DEBUG] 2015-03-23 16:01:40.414 TableViewRepro[10909:330239] Unbalanced calls to begin/end appearance transitions for <QLRemotePreviewContentController: 0x7fe105059000>.
I'm geting this error too on iPhone 6 with 8.3 and SDK 3.5.1.GA Opening a PDF works random. And sometimes it crashes with this error. Hope, this will be fixed soon.
This might very much be an Apple bug. Essentially the View controller that is presenting the Document Viewer is in the process of disappearing while the preview is coming up. This is root cause of the warning about Unbalanced calls to begin/end appearance transitions. Not much we can do about it. Unrelated to this there are a couple of bugs in the Document Viewer. Test case here
Pulls pending master - https://github.com/appcelerator/titanium_mobile/pull/6839 4_0_X - https://github.com/appcelerator/titanium_mobile/pull/6840
I solved it with a timeout of 300 ms
Closing ticket as the issue has been fixed.