How to Use Xcode's Built In Crash Reporter | Learn iOS App Development
Вставка
- Опубліковано 17 січ 2020
- In this tutorial we go through the two main places Apple stores your app's crash reports. First, through App Store Connect and second natively in Xcode which lets you jump to the exact line of code and call stack.
COMPANION VIDEOS
Wireless Debugging: • Xcode Remote Wireless ...
Project Catalyst: • Run iPad Apps on Mac? ...
MBP for Developers: • MacBook Pro 2019 for D...
Vega 16 vs 555X: • MacBook Pro Vega 16 | ...
BEST DEALS
MacBook Pro: vtudio.com/a/?a=macbook+pro
Mac Pro: vtudio.com/a/?e=mac+pro
SPECIAL THANKS
Thanks for your support and if you have any suggestions or would like to help us produce more videos, please visit: vtudio.com/a/?support
FILMING TOOLS
Sony A6400: vtudio.com/a/?e=sony+a6400
vtudio.com/tools
Links to products often include an affiliate tracking code which allow us to earn fees on purchases you make through them. - Наука та технологія
OMG - you are amazing! Lovely short video that has saved me!!
I loved your presentation myyyan.
Thanks for taking the time to make this.
Glad you found it useful mate.
Thanks for this video, this will be very helpful once I need to analyze a crash of one of my users. Do you happen to know how I can do the same with crashes on my own device for the app I'm developing? I see the crash in question when I click on "View Device Logs" (in "Devices and Simulators") but I haven't found a way to link the stack trace back to my source code, I only see "Appname + hex number" instead of symbol names. Note: the crash only happens in the field (it's a GPS+Bluetooth app), never when I'm tethered to my Mac, so I can't reproduce all issues while the debugger is attached... Thanks!
Very useful, many thanks for sharing your experience and advice 👏👏
Thanks mate, keep up the amazing work on your channel too 👏👏
good video
Any suggestions on how to easily trigger a sample crash, to ensure that crash report submissions are working correctly from a TestFlight-installed version? Thanks for doing this for us!
Swift Optional chaining. If you do force unwrapping print (a!. p) without initialize then the app will crash.
I got one question, Is there any way to check that I can confirm myself that crash is now fixed?
Hey mate, if you're able to reproduce the crash from the report, once you code in the fix, you can test it locally to see if it still occurs. However, if you can't reproduce it and you're just putting in a best guess, then what I do is just wait until the next report. If you have a test base of users you can always push it out via TestFlight.
Hello! Are these crash reports available for all Apple developers, just that’s not recommended to use that before app release, or only those who already released an app?
It's available for your apps on the store and in testflight.
Xcreate Okay, thanks
What do you think about Xamarin? Is it worth it?
If you're already native to C# then it might be something worth checking out to get up and running. However, native iOS is the way to go to get hired or learn from scratch.
@@xcreate So there is no job i see! As always thank you very much.