So FinishedLaunching shouldn't do any long running tasks, just setup the views and do the rest in background.
Also need to test in release modes on devices. Thanks *Michael Ridland | Technical Director | Xamarin MVP* XAM Consulting - Mobile Technology Specialists www.xam-consulting.com Blog: www.michaelridland.com On Fri, Oct 30, 2015 at 11:58 AM, Grant Molloy <[email protected]> wrote: > We have tested the apps on devices while debugging with VS and using Test > Flight. > Everything worked fine, and seemed to start pretty quickly. The loading > image was only visible for a few seconds before the first view was visible. > > There were some database update and Service resolution processes happening > in the Main method, but that's now been moved to the > AppDelegate.FinishedLaunching method. > > Service stack is being used to make network calls, and that was having > it's Startup method called in Main in the latest build rejected by Apple.. > > > On Fri, Oct 30, 2015 at 10:52 AM, Michael Ridland <[email protected]> > wrote: > >> >> Are you doing any long running tasks during the finishedlaunching / >> network calls? >> >> Have you tested on a device? In release mode? Have you tested in >> testflight? >> >> It might be the NSAppTransportSecurity if you're accessing a web server. >> >> Add this to your info.plist. >> >> <key>NSAppTransportSecurity</key> >> <dict> >> <key>NSAllowsArbitraryLoads</key> >> <true/> >> <key>NSExceptionDomains</key> >> </dict> >> >> >> Thanks >> >> *Michael Ridland | Technical Director | Xamarin MVP* >> >> XAM Consulting - Mobile Technology Specialists >> >> www.xam-consulting.com >> >> Blog: www.michaelridland.com >> >> >> >> On Fri, Oct 30, 2015 at 11:42 AM, Grant Molloy <[email protected]> >> wrote: >> >>> Hi all, >>> >>> I've been tasked with submitting updates for an IOS app that the company >>> I work for has built. >>> The person who was doing this has recently departed and has left some >>> notes, but not massive amounts. So this is a call out to the Apple IOS >>> guru's out there for some assistance, as I'm not an Apple person! >>> >>> App is Xamarin based, with IOS and Droid UI's. Both utilise a Portable >>> Code Library(PCL). We're developing in VS2015 on Win10, and have a MacMini >>> for IOS build and deploy machine (Xamarin Studio v5.9.7 b9), XCode v7.0.1). >>> >>> I've received the following rejection from Apple.. >>> >>> From Apple >>> >>> >>>> - 2.2 - Apps that exhibit bugs will be rejected >>>> >>>> 2.2 Details >>> >>> Thank you for your resubmission. During review, your app still failed to >>>> launch on iPad running iOS 9.1 and iPhone running iOS 9.1 on both Wi-Fi and >>>> cellular networks. Specifically, when we selected the application on the >>>> Home screen, the app displayed a launch image then quit unexpectedly. This >>>> may be because iOS 9 uses a watchdog timer for applications; if an >>>> application takes too long to complete its initial startup, the operating >>>> system terminates the application. >>> >>> Next Steps >>> >>> Please run your app on a device to identify the launch issue(s), then >>>> revise and resubmit your app for review. >>> >>> For new apps, uninstall all previous versions of your app from a >>>> device, then install and follow the steps to reproduce the issue(s). For >>>> updates, install the new version as an update to the previous version, >>>> then follow the steps to reproduce the issue(s). >>> >>> Resources >>> >>> For information about the watchdog timer, please see Technical Q&A: >>>> Application does not crash when launched from debugger but crashes when >>>> launched by user. >>>> <http://t.sidekickopen23.com/e1t/c/5/f18dQhb0S7lC8dDMPbW2n0x6l2B9nMJW7t5XYg63BmqzW8r4PxK7dKKwRW64k9XR56dJ_lf6gFvvd02?t=http%3A%2F%2Fdeveloper.apple.com%2Flibrary%2Fios%2Fqa%2Fqa2009%2Fqa1592.html&si=6506175823085568&pi=c5612196-c1cc-4cb3-f645-31484c1cef4e> >>>> . >>> >>> If you have difficulty reproducing a reported issue, please try testing >>>> the workflow described in Technical Q&A QA1764: How to reproduce bugs >>>> reported against App Store submissions >>>> <http://t.sidekickopen23.com/e1t/c/5/f18dQhb0S7lC8dDMPbW2n0x6l2B9nMJW7t5XYg63BmqzW8r4PxK7dKKwRW64k9XR56dJ_lf6gFvvd02?t=https%3A%2F%2Fdeveloper.apple.com%2Flibrary%2Fios%2Fqa%2Fqa1764%2F&si=6506175823085568&pi=c5612196-c1cc-4cb3-f645-31484c1cef4e> >>>> . >>> >>> If you have code-level questions after utilizing the above resources, >>>> you may wish to consult with Apple Developer Technical Support >>>> <http://t.sidekickopen23.com/e1t/c/5/f18dQhb0S7lC8dDMPbW2n0x6l2B9nMJW7t5XYg63BmqzW8r4PxK7dKKwRW64k9XR56dJ_lf6gFvvd02?t=https%3A%2F%2Fdeveloper.apple.com%2Fsupport%2Ftechnical%2Fsubmit%2F&si=6506175823085568&pi=c5612196-c1cc-4cb3-f645-31484c1cef4e>. >>>> When the DTS engineer follows up with you, please be ready to provide: >>> >>> - complete details of your rejection issue(s) >>> >>> - screenshots >>> >>> - steps to reproduce the issue(s) >>> >>> - symbolicated crash logs >>>> <http://t.sidekickopen23.com/e1t/c/5/f18dQhb0S7lC8dDMPbW2n0x6l2B9nMJW7t5XYg63BmqzW8r4PxK7dKKwRW64k9XR56dJ_lf6gFvvd02?t=https%3A%2F%2Fdeveloper.apple.com%2Flibrary%2Fios%2F%23technotes%2Ftn2008%2Ftn2151.html&si=6506175823085568&pi=c5612196-c1cc-4cb3-f645-31484c1cef4e> >>>> - >>>> if your issue results in a crash log >>> >>> >>> I've been unable to reproduce the bug they mention on an IPad Air v1, >>> and Apple doesn't provide any crash reports or logs. >>> >>> So I'm at a bit of a loss as to where to concentrate my efforts. >>> From what I can deduce, the errors mey be occurring within the Main or >>> FinishedLaunching methods. >>> { App Starts -> Application.Main() -> AppDelegate.FinishedLaunching()} >>> However, my last submission to the AppStore had these methods utilising >>> Try..Catch blocks which showed an alert with a specific error code which we >>> would be able to track down upon notification of failure. We didn't >>> receive any information stating that an error code was displayed (as can be >>> seen from above response). >>> >>> Do any of the IOS guru's on here have any suggestions? >>> >>> thanks >>> Grant >>> >>> >>> >>> >> >
