Repository navigation
Update SDK to 4.0.0-10242-e3cdc1ad - #7539
bw-ghapp[bot] wants to merge 70 commits into
Conversation
Codecov Report❌ Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #7539 +/- ##
==========================================
+ Coverage 86.81% 86.85% +0.04%
==========================================
Files 896 898 +2
Lines 65782 65230 -552
Branches 9407 9383 -24
==========================================
- Hits 57108 56657 -451
+ Misses 5188 5098 -90
+ Partials 3486 3475 -11
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
|
Claude finished @bw-ghapp[bot]'s task in 6m 39s —— View job SDK bump evaluated
Method: Compile-time breaksNone outstanding — Two genuine breaks exist in the commit range; both were already absorbed by earlier commits on this branch:
I verified the Runtime considerationsNone are defects; all are notes for whoever picks up the matching feature.
Everything else in range — confirmed safe
CommitNo commit — nothing needed fixing. The branch already carries the fixes for both breaks in range, and the build is green. |
The SDK bump to 4.0.0-9829-bae4427e adds LoginView.httpAuthenticationEnabled (bitwarden/sdk-internal#1675). It defaults to null in the generated Kotlin, so the build stayed clean, but toLoginView rebuilds a fresh LoginView from UI state on every save and was dropping the field. On the blob path the SDK seals this with unwrap_or(false), so sending null is not "leave unchanged" — it writes false. Editing a blob-encrypted login on Android would have silently turned off an HTTP authentication setting enabled by another client. Android does not model the setting, so round-trip it from the original cipher, matching autofillOnPageLoad.
Updates the SDK version from
4.0.0-9737-d9119f7atocom.bitwarden:sdk-android 4.0.0-10242-e3cdc1adWarning
Breaking changes detected
What's Changed
Raw changelog