docs(android): release notes for SDK 7.1.4 and Gradle plugin 4.0.6 - #21
Merged
Conversation
SDK 7.1.4 — the headline is that injected Bugsee calls no longer break local unit test runs. AGP feeds ASM-rewritten bytecode to testDebugUnitTest as well as to the device, and off-device the injected code hit stubbed framework APIs, surfacing as a failure inside an ordinary method of the consumer's own. Also covers the log-call containment and three crashes reachable in a host app: the report screen reopening after process death, a theme change with a notification-triggered report open, and the blank notification icon on the Huawei/API<=23 fallback path. Plus the snapshot de-duplication fallback on filesystems that refuse symlinks. Gradle plugin 4.0.6 — leads with the variant-scoping fix: a `debugImplementation` SDK dependency previously instrumented release bytecode too, which either failed the build under R8 or, with the -dontwarn rule R8 itself suggests, shipped an app that died at launch before any consumer code ran. Also the Compose null-Modifier launch crash (paired with the 7.1.4 runtime change, noted as a version requirement), the thread VerifyError, and the operation-End-on-throw fix. Also backfills 7.1.3, which shipped without notes. Its single change is documented from the release's actual contents rather than left as a gap in the version history. Verified with a full `npm run build`; the two SSG warnings it reports are pre-existing on the dotnet and xamarin network pages. Change-Id: I36773b69043f27bcfa53d2e9d47f5e9a945f5ae9
…nters Drops build-tool internals (ASM/AGP/R8, bytecode, VerifyError, dontwarn, missing_rules.txt, symlinks) in favour of what the reader actually observes and what they should do about it. Keeps the parts that are decision-relevant: which dependency setup is affected, which instrumentation flags can be re-enabled, and the SDK 7.1.4 requirement for the Compose fix. 7.1.3 gains a proper entry with a lead line, matching the surrounding format. Change-Id: Id40d8c334196fb1b503c5631037cf02c66d2846b
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Release notes for two shipped releases — Bugsee Android SDK 7.1.4 and Gradle plugin 4.0.6 —
plus a backfill of 7.1.3, which shipped without notes.
Written for someone deciding whether to upgrade: what they would observe, whether it affects them,
and what to do about it. No build-tool internals.
SDK 7.1.4 —
docs/sdk/android/release-notes.mdLeads with the customer-reported issue: Bugsee could fail ordinary JVM unit tests, in the
consumer's own code, on lines unrelated to Bugsee. The note tells anyone who disabled
mainThreadMisuse,log,threadoroperationDispatchto work around it that they canre-enable them.
Then the three crashes reachable in a host app — the report screen reopening after the app was
dropped from memory, a theme change with a notification-opened report on screen, and the missing
notification icon on Huawei / Android 6.0 and older — plus screenshots being lost on some storage
configurations.
7.1.3
Backfilled. It shipped without notes, leaving a hole between 7.1.2 and 7.1.4. Its single change —
notification-opened reports being attributed as code-triggered — is documented from the release's
actual contents.
Gradle plugin 4.0.6 —
docs/sdk/android/gradle-plugin/releases.mdxLeads with the variant fix, framed by the setup that triggers it: if you add Bugsee for some
variants only (say
debugImplementation), release builds were being wired up to call an SDK thatwas not present — either failing the release build or producing an app that crashed as soon as it
was opened. States plainly that flavors are handled the same way, and that plain
implementationusers are unaffected.
The Compose fix carries its SDK 7.1.4 requirement, matching how 4.0.3 flagged its 7.1.0
dependency — an omission there breaks people.
Verification
npm run buildpasses. The two SSG warnings it emits are pre-existing, on the dotnet andxamarin network pages, unrelated to these changes.
🤖 Generated with Claude Code