The application is rejected twice, but cannot reproduce the problem on iOS 9.2. I need help identifying him

Question

I can’t reproduce the problem on any iPhone and iPad, all of which are based on Debug, Release, and even on the ad-hoc build installed with iTunes, just fine. This is an update to an existing application. The only things added in the previous version are notifications using Azure notification concentrators and version checking. I am using the latest version of Xamarin iOS to create an application

Supported ARMv7 + ARM64 architectures

I tried:

• Running tool for zombies
• Minimize download on boot

Part of the crash log is here, but I can't do any of this.

Incident Identifier: 533700FF-EE1C-4DFC-AFAD-60FE3600B66D CrashReporter Key: 9cadde5ef1a33ebb1b6aeeaed6696a7ce8b4087d Hardware Model: xxx Process: TapNOrder [9390] Path: /private/var/mobile/Containers/Bundle/Application/45780C57-DBB0-465C-872F-8A3BE6723261/TapNOrder.app/TapNOrder Identifier: biz.innovative-ideas.tapnorder Version: 0.1.7.2 (0.1.7) Code Type: ARM-64 (Native) Parent Process: launchd [1] Date/Time: 2016-01-11 15:00:11.11 -0800 Launch Time: 2016-01-11 15:00:11.11 -0800 OS Version: iOS 9.2 (13C75) Report Version: 105 Exception Type: EXC_BAD_ACCESS (SIGSEGV) Exception Subtype: KERN_INVALID_ADDRESS at 0x0000000000000000 Triggered by Thread: 0 Filtered syslog: None found Thread 0 name: Dispatch queue: com.apple.main-thread Thread 0 Crashed: 0 ??? 000000000000000000 0 + 0 1 TapNOrder 0x0000000100f8984c 0x1000a8000 + 15603788 2 TapNOrder 0x0000000100f88c40 0x1000a8000 + 15600704 3 TapNOrder 0x0000000100f88c78 0x1000a8000 + 15600760 4 TapNOrder 0x0000000100d7e570 0x1000a8000 + 13460848 5 libobjc.A.dylib 0x00000001827fab54 0x1827f4000 + 27476 6 libobjc.A.dylib 0x0000000182806080 0x1827f4000 + 73856 7 libobjc.A.dylib 0x00000001828060e0 0x1827f4000 + 73952 8 UIKit 0x000000018822fefc 0x187e6c000 + 3948284 ... Thread 0 crashed with ARM Thread State (64-bit): x0: 0x0000000000000000 x1: 0x0000000000000000 x2: 0x00000001a0a82180 x3: 0x000000016fd55f08 x4: 0x000000013d88f680 x5: 0x0000000000000000 x6: 0x000000013d562090 x7: 0x0000000000000b20 x8: 0x0000000000000000 x9: 0x0000000000000000 x10: 0x0000000000000557 x11: 0x00000001a2f35929 x12: 0x00000001a2f35929 x13: 0x0000000000000001 x14: 0x000000008000001f x15: 0x0000000080000023 x16: 0x0000000182dfbaf4 x17: 0x00000001014082d8 x18: 0x0000000000000000 x19: 0x0000000101471870 x20: 0x000000013d562090 x21: 0x0000000182818fa6 x22: 0x0000000100d7e540 x23: 0x00000001a0a823e0 x24: 0x000000018280de80 x25: 0x000000019fb37616 x26: 0xf3002d81df52aec2 x27: 0x000000019feef000 x28: 0x000000019feef000 fp: 0x000000016fd55f20 lr: 0x0000000100f863b0 sp: 0x000000016fd55f10 pc: 0x0000000000000000 cpsr: 0xa0000000 

The complete crash log is here: Apple Crash Log

Any ideas?

Answer 1

Crash Re Symbolication is the process of finding the exact fault.

Just follow the steps to counter the failure problem. To get your symbolized logs from Crash logs, you need the following files:

• AppName.app - Application File (Executable file)
• File AppName-dsym.dSYM - dSYM generated by XCODE when executing the actual .app file
• AppName-Crash-log.crash

Carefully follow all the steps, and then check the crash logs, which you will find exactly where this will cause the application to crash.

Now follow these steps:

• Move all the above files (AppName.app, AppName-dSYM.dSYM and AppName-Crash-log.crash) to a folder with a convenient name, where you can easily use the terminal. Just create the MyCrashReport folder on your desktop and add all three files to it.

• Go to the following path that applies to your version of XCODE:

Xcode 6

/Applications/Xcode.app/Contents/SharedFrameworks/DTDeviceKitBase.framework/Versions/A/Resources/symbolicatecrash

Other then Xcode 6

Content / Developer / Platforms / iPhoneOS.platform / Developer / Library / PrivateFrameworks / DTDeviceKitBase.framework / Versions / A / Resources / symbolicatecrash

or

Content / Developer / Platforms / iPhoneOS.platform / Developer / Library / PrivateFrameworks / DTDeviceKit.framework / Versions / A / Resources / symbolicatecrash

Xcode 7.3

/Applications/Xcode.app/Contents/SharedFrameworks/DVTFoundation.framework/Versions/A/Resources/symbolicatecrash

3. Copy the file with the crash symbol from this place and paste it with the three files into the MyCrashReport folder.

4. Open the terminal and the CD in the MyCrashReport folder.

5. cd Desktop / MyCrashReport - press Enter

6. export DEVELOPER_DIR = "/Applications/XCode.app/Content/Developer" - Press Enter

7. ./symbolicatecrash -v AppName-Crash-log.crash AppName.dSYM - Press Enter

Done !!! Now symbolic logs are on your terminal and detect an error or failure in it.

See this link for a detailed description. https://medium.com/@Mrugraj/crash-re-symbolication-5c28d3a3a883#.4lvl4h625

Answer 2

I could not find the file in this directory. Contents / Developer / Platforms / iPhoneOS.platform / Developer / Library / PrivateFrameworks / DTDeviceKit.framework / Versions / A / Resources because for some reason I miss the /DTDeviceKit.framework folder and files dsym couldn't download either, so I followed this procedure and posted it here, if someone needs it, there is no need for a terminal:

If you have the correct .ipa and .dSYM files corresponding to the crash log:

• For simplicity, put them in one folder,
• Attach the device to your macbook,
• Uninstall the application from your device,
• Install the application through the .ipa device directly through itunes (this may work a little, but quite easily).

Once this is done, and you are sure that your application matches the one that caused the crash log, open Xcode.

In Xcode

• Launch the window | View devices
• Choose your device,
• Click View Device Logs
• Drag and drop your fault log into the log window (left pane under the headings: Process / Dev / etc ..

That's it, Xcode automatically symbolizes the crash log.