2 Replies
      Latest reply: Feb 7, 2017 8:19 PM by MDISQ RSS
      MDISQ Level 1 Level 1 (0 points)

        Since the error "could not be started in 20.00 seconds" may occur, we have sequentially deleted the logic for analysis.
        However, even if "Hello" is displayed only, it will not resolve and an error will occur.
        Do you think there are some possible factors in this situation?

        The application is distributed under "Adhoc".
        We are connecting to the internal network with VPN.

        For reference, I will list Swift's code.
        ---------------------------------------------------------------------
        class AppDelegate: UIResponder, UIApplicationDelegate{
            var application: UIApplication?;
            var launchOptions: [NSObject: AnyObject]?
            var view:UIViewController?
           
            func application(application: UIApplication, didFinishLaunchingWithOptions launchOptions: [NSObject: AnyObject]?) -> Bool {
                self.application = application;
                self.launchOptions = launchOptions
                return true
            }
        }
        ---------------------------------------------------------------------
        class FirstView: UIViewController,UITableViewDelegate{
            var appDelegate:AppDelegate = UIApplication.sharedApplication().delegate as! AppDelegate
            var flag:Bool = false;
           
            override func viewDidLoad() {
                super.viewDidLoad()
                appDelegate.view = self;
                appDelegate.firstView = self;
               
            }
        }
        ---------------------------------------------------------------------

        • Re: Sometimes "could not be started in 20.00 seconds" occasionally occurs at the launch of an application that displays "Hello"
          eskimo Apple Staff Apple Staff (5,995 points)

          When your app crashes in this way you should get a [crash report][tn2151].  The backtrace of the main thread should give you some clues as to where your app is stuck.

          Share and Enjoy

          Quinn “The Eskimo!”
          Apple Developer Relations, Developer Technical Support, Core OS/Hardware
          let myEmail = "eskimo" + "1" + "@apple.com"

            • Re: Sometimes "could not be started in 20.00 seconds" occasionally occurs at the launch of an application that displays "Hello"
              MDISQ Level 1 Level 1 (0 points)
              Thank you for your reply.
              I was investigating with only ".crash" file.
              I got late, but I got a ".dSYM" file.
              According to the advice, I confirmed the result of "symboliccrash", but unfortunately useful information was not found.
              Do you have any advice from the following contents?
              ---------------------------------------------------------------------

              Application Specific Information:
              jp.co.mdis.AccidentInfoListView failed to launch after 20.00s (launchIntent: foreground-interactive)

              Elapsed total CPU time (seconds): 6.870 (user 6.870, system 0.000), 11% CPU
              Elapsed application CPU time (seconds): 0.005, 0% CPU

              Filtered syslog:
              None found

              Thread 0:
              0   dyld                           0x000000012003d370 0x120018000 + 152432
              1   dyld                           0x000000012003cd74 0x120018000 + 150900
              2   dyld                           0x000000012002b714 0x120018000 + 79636
              3   dyld                           0x000000012002e818 0x120018000 + 92184
              4   dyld                           0x000000012002a6d4 0x120018000 + 75476
              5   dyld                           0x000000012001b850 0x120018000 + 14416
              6   dyld                           0x000000012001ff90 0x120018000 + 32656
              7   dyld                           0x000000012001fe5c 0x120018000 + 32348
              8   dyld                           0x000000012001fb4c 0x120018000 + 31564
              9   dyld                           0x000000012001f604 0x120018000 + 30212
              10  dyld                           0x000000012001f100 0x120018000 + 28928
              11  dyld                           0x000000012001b364 0x120018000 + 13156
              12  dyld                           0x000000012001b02c 0x120018000 + 12332
              13  dyld                           0x00000001200200f0 0x120018000 + 33008
              14  dyld                           0x0000000120027ef4 0x120018000 + 65268
              15  dyld                           0x0000000120027398 0x120018000 + 62360
              16  dyld                           0x000000012001cc94 0x120018000 + 19604
              17  dyld                           0x000000012001dbb4 0x120018000 + 23476
              18  dyld                           0x0000000120019044 0x120018000 + 4164

              No thread state (register information) available

              Binary Images:
              0x100068000 - 0x100073fff MyAPP arm64  <3478065f6fc03c82b48e9e46eb305fd4> /var/mobile/Containers/Bundle/Application/A816A922-A88A-4832-9681-5ED49C346A05/MyAPP.app/MyAPP
              0x100094000 - 0x1001effff libswiftCore.dylib arm64  <aeda45db7c123ec1a85737365c8b533a> /var/mobile/Containers/Bundle/Application/A816A922-A88A-4832-9681-5ED49C346A05/MyAPP.app/Frameworks/libswiftCore.dylib
              0x10038c000 - 0x100397fff libswiftCoreGraphics.dylib arm64  <69f3e93e4a7032c1aa59ce567e457e54> /var/mobile/Containers/Bundle/Application/A816A922-A88A-4832-9681-5ED49C346A05/MyAPP.app/Frameworks/libswiftCoreGraphics.dylib
              0x120018000 - 0x120047fff dyld arm64  <9e98992ceed735e2ac4784cb28efe7c1> /usr/lib/dyld