LLDB crash

Mine crashes too - need fix asap. 🙂

Yup, so the crash log isn't really useful on its own.I recommend you put breakpoints into your code, run it and step over line by line and see exactly the lines where it crashes. We can't do that for you, you have to do it. Have a look in the Apple debugger documentation if you don't know how to do it. In my experience, crashes in my code on arm64 have been regular bugs in the code that caused memory access issues that didn't crash on armv7 but do crash on arm64. But they were still bugs. In some situations they didn't crash on the simulators but do crash on real devices. Run using the debugger on real devices if you can.

Hi,seeing the same thing here. Also tried to delete all podcasts by removing them from the sync in iTunes. I haven't tried to reinnstalling, but attached is the crash-log.Incident Identifier: B5F20F2E-F1DF-469D-B710-8DEE3DC9104BCrashReporter Key: fb29f236715284e01c3ca12533f80c13bbf8eb99Hardware Model: iPhone7,2Process: Podcasts [425]Path: /Applications/Podcasts.app/PodcastsIdentifier: com.apple.podcastsVersion: 967.2 (2.3)Code Type: ARM-64 (Native)Parent Process: launchd [1]Date/Time: 2015-06-10 13:18:56.56 +0200Launch Time: 2015-06-10 13:18:55.55 +0200OS Version: iOS 9.0 (13A4254v)Report Version: 105Exception Type: EXC_CRASH (SIGABRT)Exception Codes: 0x0000000000000000, 0x0000000000000000Exception Note: EXC_CORPSE_NOTIFYTriggered by Thread: 7Filtered syslog:None foundLast Exception Backtrace:0 CoreFoundation 0x182f93f44 0x182e6c000 + 12122281 libobjc.A.dylib 0x197faff2c 0x197fa8000 + 325562 CoreFoundation 0x182f93e8c 0x182e6c000 + 12120443 Foundation 0x183e10f0c 0x183e04000 + 530044 Podcasts 0x10017

When I try that the settings app keeps crashing. I might need to restore my phone too.Thanks for the suggestion.

Hi, thanks for the crash report and logs. We're looking into the issues here at AirWatch and will be posting more information in a KB article on myAirWatch.

The crash log is useful if it's symbolicated. It's not particularly useful in that format. (Incidentally you don't normally need to post the long list of binaries at the end, or the irrelevant threads - usually just the header and the thread that crashed is sufficient. More info is better than less though.)These two lines1 OIDAR 0x0000000100095020 0x100038000 + 3809602 OIDAR 0x0000000100093d0c 0x100038000 + 376076will point to the specific source file and line of code that caused the crash once you have that log symbolicated. (Drag into Xcode in the device logs window)

Hi Rajeev,sorry, did not work. What I found out:I deleted the folder user name/Library/mail completelyThen mail started again - with some crashes - but I got some time because the crashes are not seconds after start.Then I checked the accounts and saw that they are mostly (not all) double (Mail / Settings / Accounts)Then I started to delete the double accounts (with some crashes) and it seem to work now.I am already chronising my Exchange accounts at the moment, but it works.What I am wondering about:Every time with a new BETA release the Mail ******** starts - I had the same at Yosemite until Beta 4.Apple - please!!!!! It is really not needed that you have the most instable Mail beta in the IT. :-)My Windows 10 beta in Parallels works much better than every Beta I saw before. GreetingsHartmut

It works for me, my friend says it causes his phone to crash

Same here. Crashes El Capitan completely.