Skip to content
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

[PLAT-5450] Add missing app and device data to OOM events #908

Merged
merged 5 commits into from
Nov 26, 2020

Conversation

nickdowell
Copy link
Contributor

Goal

Out Of Memory errors have been missing some of the information present in other types of errors reported by Bugsnag.

The aim of this PR is to add the following data:

  • batteryLevel
  • charging
  • dsymUUIDs
  • manufacturer
  • orientation
  • runtimeVersions
  • totalMemory

Design

The additional information is captured in BugnagSystemState as this information is already being used to generate the OOM error payload.

Changeset

BugnagSystemState has been amended to capture additional information.

BugsnagAppWithState, BugsnagDeviceWithState and BugsnagEvent have been updated to read this new information.

Testing

Manually tested and verified by examining the payloads sent to the notify endpoint.

@nickdowell nickdowell changed the title Add missing app and device data to OOM events [PLAT-5450] Add missing app and device data to OOM events Nov 25, 2020
Capturing the battery and orientation values in the initial creation of the
BugsnagSystemState object ensures they will be there when the app is terminated
to simulate an OOM.

The test was sometimes failing because BugsnagSystemState queues up
asynchronous writes in the background and these do not always have time
to complete when running the test scenario.
@nickdowell nickdowell force-pushed the nickdowell/app-and-device-data-for-ooms branch from 175a443 to 007e2fa Compare November 25, 2020 14:06
@nickdowell nickdowell merged commit b3a497a into next Nov 26, 2020
@nickdowell nickdowell deleted the nickdowell/app-and-device-data-for-ooms branch November 26, 2020 08:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants