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

fix: Use latest value when checking release stage #412

Merged
merged 2 commits into from
Sep 18, 2019

Conversation

kattrali
Copy link
Contributor

A serialization bug in crash reports would erroneously allow or prevent
crash reports from being delivered when the value of release stage
or notify release stages were changed after start() was called, or in a
subsequent build of the same app.

Some values in config are serialized as nested values, while others are
at the "top" level of config when written to disk. This change checks
the expected position and fallback value for every config option.

Fixes #405

@kattrali kattrali force-pushed the kattrali/fix-release-stages-filtering branch from 445cffd to c0c5384 Compare September 17, 2019 17:29
A serialization bug in crash reports would erroneously allow or prevent
crash reports from being delivered when the value of release stage
or notify release stages were changed after start() was called, or in a
subsequent build of the same app.

Some values in config are serialized as nested values, while others are
at the "top" level of config when written to disk. This change checks
the expected position and fallback value for every config option.

Fixes #405
@kattrali kattrali force-pushed the kattrali/fix-release-stages-filtering branch from c0c5384 to c5bfccc Compare September 17, 2019 17:32
@bugsnag bugsnag deleted a comment from codecov bot Sep 18, 2019
The previous implementation reported the release stage when the report
is sent, rather than when the report was generated. This change
refactors the app state parser to use the correct stage value, either
current or from a file cache.
@kattrali kattrali force-pushed the kattrali/fix-release-stages-filtering branch from c5bfccc to ce91abb Compare September 18, 2019 07:47
@codecov
Copy link

codecov bot commented Sep 18, 2019

Codecov Report

Merging #412 into master will increase coverage by 0.09%.
The diff coverage is 100%.

Impacted file tree graph

@@            Coverage Diff             @@
##           master     #412      +/-   ##
==========================================
+ Coverage   51.83%   51.93%   +0.09%     
==========================================
  Files          66       66              
  Lines        7522     7527       +5     
==========================================
+ Hits         3899     3909      +10     
+ Misses       3623     3618       -5
Impacted Files Coverage Δ
Source/BugsnagCrashReport.m 82.53% <100%> (+0.17%) ⬆️
Source/BugsnagFileStore.m 66.19% <0%> (+2.38%) ⬆️

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update e1b5842...ce91abb. Read the comment docs.

@kattrali kattrali changed the title fix(config): Use latest value when checking release stage fix: Use latest value when checking release stage Sep 18, 2019
@kattrali kattrali merged commit b5f8d8d into master Sep 18, 2019
@kattrali kattrali deleted the kattrali/fix-release-stages-filtering branch September 18, 2019 09:27
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.

Bugsnag sends all reports in store regardless of releaseStage settings
1 participant