-
Notifications
You must be signed in to change notification settings - Fork 35
Attachment support #68
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
…just iOS integration code - code should now compile on iOS
rqbacktrace
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me, thank you!
vlussenburg
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The .so files look empty (0 bytes) in the diff - is that right?
vlussenburg
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Although 'boring getter setter logic' this should be unit tested.
…s/backtrace-unity into feature/attachment-support
Dautery91
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@konraddysput - looks great overall. The only feedback is to change that tooltip (see my comment). Thanks!
| [Tooltip("If the database is unable to send its record, this setting specifies the maximum number of retries before the system gives up")] | ||
| public int RetryLimit = 3; | ||
|
|
||
| [Tooltip("If the database is unable to send its record, this setting specifies the maximum number of retries before the system gives up")] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think you copy / pasted the tool tip from the above. Make sure you update it to reflect the real use of the AttachmentPaths field @konraddysput
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ah good catch. Thanks
| #if UNITY_ANDROID || UNITY_IOS | ||
| EditorGUILayout.PropertyField( | ||
| serializedObject.FindProperty("AttachmentPaths"), | ||
| new GUIContent(BacktraceConfigurationLabels.LABEL_REPORT_ATTACHMENTS)); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@konraddysput does this end up exposing the array as we discussed in the editor? (The default foldout arrow thing?) If so, this is good for now! Side note - as a part of the work I am doing, I am going to try to come up with some custom property drawers to make these easier to use
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes it does - I hope we can make it prettier soon!
Dautery91
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good, thanks for making the change!
…se-positive anrs (#69) * Background thread support (#67) * Background thread support * Fixed exception flow * Removed renamed file * Detect false-positive ANRs report and prevent ANR watchdog from sending them (#66) * Detect false-positive ANRs report and prevent ANR watchdog from sending them + anr thread improvements * Fixed typos + better documentation - added Samy's advices * Attachment support (#68) * Attachment support on Android - iOS shouldn't compile * Updated the latest version of backtrace-android libraries and also adjust iOS integration code - code should now compile on iOS * Native attachment support * Attachment improvements * Updated label * Native client updates * Android libraries * Version update * 3.4.0-rc1 * Prevents from reading empty attachments * Arabic language support (#70) * Fixed invalid date in log manager when calendar is unsupported * Use single method to generate UTC timestamps + move it from extension code to static class to avoid unnecessary allocation * Fixed line endings * Updated native library * Removed debug logs from native library * Updated library version * Added invariant culture to rest of the code * native library update * Fixed issue in the readme file * Correct attachment name (#73) * Correct attachment name * Moved constants to const variables * Prepare for final release * Fixed typo in function name * Changelog change
Why
As a user I would like to upload attachments when:
happened. With attachment support, we can have more insights about a game state when the specific situation in my game occurred.
This pull request allows our users to set up attachment support for managed and native reports. To achieve that users can initialize Backtrace Client integration with the list of paths to attachments that they would like to send to us. Attachments will be included in every Backtrace report. In addition to that on iOS when OOM, Crash occurred, we're generating crash/oom attributes but also we store attachments. In the next session when we want to send attachments to Backtrace, old attachments and new attachments will be available in the OOM/Crash report.
Limitations
Updates:
This diff updates the backtrace-android native library available in unity and the backtrace-cocoa (objective-c) library.
Testing strategy
In all my tests I used:
Native test
iOS
Attachments are available on app crash
OOM reports contain attachment paths
ANR reports contain attachment paths
Android
Generate android Crash
ANR reports contain attachment paths
Managed tests
Send exception/unhandled exception/message and see if attachments are available