[Dev docs] Debugging documentation #1328
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
bolsinga
approved these changes
Apr 30, 2019
nguyenhuy
approved these changes
Jun 4, 2019
| ## Crashes | ||
|
|
||
| Sometimes, the environment can get into a state where a fatal interrupt signal occurs inside UIKit. The exception could be from an invalid memory address, unrecognized selector, or a typical out of bounds to name a few. Since Texture is fairly robust due to the awesome designers, it is the case sometimes that UIKit is more fragile. It is also likely that crashes will be occurring for a small percentage of your users, visible to you only through Crashlytics. |
There was a problem hiding this comment.
Suggested change
| Sometimes, the environment can get into a state where a fatal interrupt signal occurs inside UIKit. The exception could be from an invalid memory address, unrecognized selector, or a typical out of bounds to name a few. Since Texture is fairly robust due to the awesome designers, it is the case sometimes that UIKit is more fragile. It is also likely that crashes will be occurring for a small percentage of your users, visible to you only through Crashlytics. | |
| Sometimes, the environment can get into a state where a fatal interrupt signal occurs inside UIKit. The exception could be from an invalid memory address, unrecognized selector, or a typical out of bounds to name a few. Since Texture is fairly robust, it is the case sometimes that UIKit is more fragile. It is also likely that crashes will be occurring for a small percentage of your users, visible to you only through your crash reporting service. |
There was a problem hiding this comment.
Let's keep a neutral tone in documentations :)
| Sometimes, the environment can get into a state where a fatal interrupt signal occurs inside UIKit. The exception could be from an invalid memory address, unrecognized selector, or a typical out of bounds to name a few. Since Texture is fairly robust due to the awesome designers, it is the case sometimes that UIKit is more fragile. It is also likely that crashes will be occurring for a small percentage of your users, visible to you only through Crashlytics. | ||
|
|
||
| Let's go through an example where @maicki and @hnugyen solved a mysterious and non-deterministic crash. |
There was a problem hiding this comment.
Suggested change
| Let's go through an example where @maicki and @hnugyen solved a mysterious and non-deterministic crash. | |
| Let's go through an example where @maicki and @nguyenhuy solved a mysterious and non-deterministic crash. |
| Using `if (ASActivateExperimentalFeature(ASExperimentalSkipClearData)) {` you can safely gate your new logic to a universal experiment that consumers of Texture can opt into. | ||
|
|
||
| @maicki and @hnugyen were then able to confirm that preventing the clearData in the data source change prevented this crash from occurring in the wild. |
There was a problem hiding this comment.
Suggested change
| @maicki and @hnugyen were then able to confirm that preventing the clearData in the data source change prevented this crash from occurring in the wild. | |
| @maicki and @nguyenhuy were then able to confirm that preventing the clearData in the data source change prevented this crash from occurring in the wild. |
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.
Only filling in what I can here. Two different parts so far, one about the
clearDatacrash and how it was understood, tested, and closed. The second part is about using Hopper to get more understanding of crashing environments.