forked from beeware/briefcase
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request beeware#126 from mcscope/patch-2
Add how-to guide for how to see errors on iOS.
- Loading branch information
Showing
3 changed files
with
13 additions
and
0 deletions.
There are no files selected for viewing
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,12 @@ | ||
See Errors on iOS | ||
========================= | ||
|
||
If you have a beeware iOS project that has a crash, it can be difficult to see the stacktrace. Here's how to do it - | ||
|
||
1. Build your iOS project. You don't have to start it. | ||
|
||
2. Open that iOS project in Xcode. Click the Run button (looks like an arrow) and wait for the simulator to open. Cause the app to crash. | ||
|
||
3. Your stack trace ought to appear in the 'debugger area' at the bottom of the screen. If you can't see that area, you may have to activate it with ``View`` > ``Debug Area`` > ``Show Debug Area`` | ||
|
||
.. image:: PyStackTraceOnXCode.png |