2 Replies
      Latest reply on Nov 11, 2019 1:49 AM by eskimo
      berkbaba Level 1 Level 1 (0 points)

        I have development device for iOS 13 (iPhone X). Before the macOS 10.15 Catalina, iTunes was still live and when I sync iPhone to my Mac with cable via iTunes, all diagnostic log files were going to this folder:

        ~/Library/Logs/CrashReporter/MobileDevice

        and removed from iPhone after copied here. However, after upgrading to the Catalina, iTunes was dead. synicing iPhone via Finder could not copy diagnostic log files from iPhone to to Mac now. Reports no longer come to the specified folder and are not automatically deleted from the iPhone.

        Are there any people who have had this problem before? Thank you.

        • Re: Where MobileDevice CrashReporter Files Going in macOS 11.15?
          KMT Level 9 Level 9 (15,115 points)

          I'd start by confirming that diagnostics are enabled on that device, then use Xcode/Devices and Simulators/<name>/View Device Logs/This Device ...to confirm there are diagnostic log files present on the device.

           

          You may want to be patient if Xcode indicates it is preparing that device for debugging...

          • Re: Where MobileDevice CrashReporter Files Going in macOS 11.15?
            eskimo Apple Staff Apple Staff (12,305 points)

            However, after upgrading to the Catalina, iTunes was dead.

            Indeed.

            [syncing] iPhone via Finder could not copy diagnostic log files from iPhone to to Mac now.

            That’s not my experience.  Here’s what I did:

            1. I created a small test project that, on tapping a button, calls abort.

            2. I ran that on my device using Xcode.

            3. I stopped the app.

            4. I disconnected my device from my Mac.

            5. I ran the app from the Home screen.

            6. I tapped the button and thus crashed the app.

            7. I connected it to my Mac running 10.15.

            8. In Finder, I selected my device on the left.

            9. I clicked Sync.

            10. After the sync was done I found the crash repor at the path ~/Library/Logs/CrashReporter/MobileDevice/Scout in a Can /CrashMe-2019-11-11-094201.crash.  There’s a snippet below, just FYI.

            Share and Enjoy

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


            Incident Identifier: 9F88DF5F-D421-4CBE-B4FD-9CBB00857E2F
            CrashReporter Key:   dc6d7aa326dffab6fc564be7278a9ad639485ad0
            Hardware Model:      iPhone12,1
            Process:             CrashMe [4278]
            Path:                /private/var/containers/Bundle/Application/222714E9-C319-41A7-92E4-EF34DA296E8B/CrashMe.app/CrashMe
            Identifier:          com.example.apple-samplecode.CrashMe
            Version:             1.0 (1.0)
            Code Type:           ARM-64 (Native)
            Role:                Foreground
            Parent Process:      launchd [1]
            Coalition:           com.example.apple-samplecode.CrashMe [594]
            
            
            Date/Time:           2019-11-11 09:42:00.8454 +0000
            Launch Time:         2019-11-11 09:41:59.5589 +0000
            OS Version:          iPhone OS 13.2 (17B84)
            Release Type:        User
            Baseband Version:    1.02.14
            Report Version:      104
            
            Exception Type:  EXC_CRASH (SIGABRT)
            Exception Codes: 0x0000000000000000, 0x0000000000000000
            Exception Note:  EXC_CORPSE_NOTIFY
            Triggered by Thread:  0
            
            Thread 0 name:  Dispatch queue: com.apple.main-thread
            Thread 0 Crashed:
            …