docs(android): bound the v6 install snippet to the 6.x line - #50
Merged
Conversation
The 6.x installation page told readers to declare `com.bugsee:bugsee-android:+`. Gradle resolves a bare `+` to the newest version at the coordinate, which is now 7.1.4 — so following the v6 install guide pulls a 7.x SDK with a near-total API redesign, against 6.x instructions for every other step on the page. Use `6.+` and explain why the prefix matters. The sibling Maven page already pins an explicit 6.x version, so this brings Gradle in line. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Change-Id: I5e86eb40cb043f80422c2816d6951364bf3a7ad7
1 task
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
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.
Summary
docs/sdk/android/v6/installation.mdxtells readers to declare:implementation 'com.bugsee:bugsee-android:+'Gradle resolves a bare
+to the newest version at the coordinate.com.bugsee:bugsee-androidis the same coordinate for both lines, and its newest release is now 7.1.4 — so following the 6.x install guide silently pulls a 7.x SDK, against 6.x instructions for initialization, configuration, and every other step on the page. SDK 7.0 is a near-total public-API redesign, so this is a compile failure at best.Surfaced while reviewing #49, which fixes the
compileSdkcontradiction on the same page. Independent hunk, no conflict.Changes
+→6.+, so the snippet stays on the line the page documents.:::infoadmonition to explain why the prefix matters, and to point readers at the 6.x → 7.x migration guide if they'd rather move to the current line.The sibling Maven installation page already pins an explicit
6.0.4, so this brings the Gradle path in line with it.Test plan
npx cspell "docs/**/*.md" "docs/**/*.mdx" --no-cache -c cspell.json— 288 files, 0 issuescom.bugsee:bugsee-android7.x publishes to the same coordinate (tagsv7.0.0…v7.1.4in the Android SDK repo; the Gradle plugin requirements page names the same artifact for the 7.x line)🤖 Generated with Claude Code