add doc: How to catch crash on ios use xcode #17278
Merged
Conversation
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
qfrank
requested review from
ilmotta,
cammellos,
Samyoul,
flexsurfer,
yqrashawn,
Parveshdhull,
ajayesivan,
J-Son89,
jo-mut,
ibrkhalil,
BalogunofAfrica,
siddarthkay and
mohsen-ghafouri
Jenkins BuildsClick to see older builds (4)
|
flexsurfer
approved these changes
Sep 13, 2023
BalogunofAfrica
approved these changes
Sep 13, 2023
ilmotta
approved these changes
Sep 13, 2023
There was a problem hiding this comment.
I can't test the instructions, but thank you anyway @qfrank.
As a suggestion, I did a pass on gpt only to fix the grammar and broke the first paragraph into a few different ones.
Sometimes, we can't reproduce a crash with a local dev build, probably because
your built version differs from the one the QA team used. The QA team mostly
used the PR build version. In this guide, we will try to make a build as close
as possible to the PR build for iOS.
You may notice various configuration files starting with .env (such as .env,
.env.e2e, .env.jenkins) in the project. The usage of these files and environment
variables injected at build time on CI will not be covered in this guide.
This guide covers how to configure Xcode to capture a crash stack trace with a
physical iOS device. This allows debugging crashes by inspecting the stack
trace.
We will use [issue
#17255](https://github.com/status-im/status-mobile/issues/17255) as an example
to reproduce and analyze a crash.
siddarthkay
approved these changes
Sep 13, 2023
There was a problem hiding this comment.
Other than a few tiny suggestions this document looks good!
Thanks for sharing this knowledge @qfrank !
qfrank
force-pushed
the
doc/catch-crash-on-ios
branch
from
559c381 to
1b1e095
Compare
jo-mut
approved these changes
Sep 14, 2023
|
its a good one |
ajayesivan
approved these changes
Sep 14, 2023
qfrank
force-pushed
the
doc/catch-crash-on-ios
branch
from
1b1e095 to
16225b8
Compare
|
Sorry team, i've made a bad example that merged PR without e2e test although no code changes in this PR! I should also notice QA team in this case. 🙂 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
link to view the doc
status: ready