Closed Bug 2082647 Opened 1 month ago Closed 1 month ago

Update android nightly application-services version bump to new version 4a8546f9b0477c34696429db16f8b441a4cd8d5c from 2026-10-15 18:22:31

Categories

(Firefox for Android :: General, enhancement)

All
Unspecified
enhancement

Tracking

()

RESOLVED DUPLICATE of bug 2082711
Tracking Status
firefox160 --- affected

People

(Reporter: update-bot, Assigned: update-bot)

References

Details

(Whiteboard: [3pl-filed][task_id: TIL5fgfeRuqeeycLTV8kOg])

Attachments

(1 obsolete file)

This update covers 9 commits, including 5 new upstream commits I've never filed a bug on before. (They're the top 5.). Here are the overall diff statistics, and then the commit information.


mobile/android/android-components/plugins/dependencies/src/main/java/ApplicationServices.kt | 2 +-
mobile/android/android-components/plugins/dependencies/src/main/java/moz.yaml | 4 ++--
2 files changed, 3 insertions(+), 3 deletions(-)


4a8546f9b0477c34696429db16f8b441a4cd8d5c by Beth Rennie <beth@brennie.ca>

https://github.com/mozilla/application-services/commit/4a8546f9b0477c34696429db16f8b441a4cd8d5c
Authored: 2026-10-15 17:59:01 +0000
Committed: 2026-10-15 17:59:01 +0000

Bug 2053517 - Remove more shared preferences gunk (#7660)

Files Modified:

  • components/support/nimbus-fml/src/backends/kotlin/templates/FeatureManifestTemplate.kt
  • components/support/nimbus-fml/src/backends/kotlin/templates/ImportedModuleInitializationTemplate.kt
  • components/support/nimbus-fml/src/backends/kotlin/templates/macros.kt

001271d538d66f8627ebcd8151c7b5fef8a023d3 by Mark Banner <standard8@mozilla.com>

https://github.com/mozilla/application-services/commit/001271d538d66f8627ebcd8151c7b5fef8a023d3
Authored: 2026-10-15 17:38:44 +0000
Committed: 2026-10-15 17:38:44 +0000

Bug 2082570 - Add dumps for search config v3 and update other search related dumps (#7659)

  • Bug 2082570 - Add search-config-v3 to the remote-settings dumps and ensure it is sorted.

  • Bug 2082570 - Update other search releated dumps as well.

Files Added:

  • components/remote_settings/dumps/main/search-config-v3.json
  • components/remote_settings/dumps/main/search-config-v3.timestamp

Files Modified:

  • components/remote_settings/dumps/main/search-config-v2.json
  • components/remote_settings/dumps/main/search-config-v2.timestamp
  • components/remote_settings/dumps/main/search-telemetry-v2.json
  • components/remote_settings/dumps/main/search-telemetry-v2.timestamp
  • components/remote_settings/src/client.rs
  • examples/remote-settings-cli/src/dump/client.rs

2e13f43757f42250a1674e191f91f6de4d70bdfc by bendk <bdk@mozilla.com>

https://github.com/mozilla/application-services/commit/2e13f43757f42250a1674e191f91f6de4d70bdfc
Authored: 2026-10-15 13:35:00 +0000
Committed: 2026-10-15 13:35:00 +0000

Upgrade rustls (#7655)

Update rustls from 0.23.45 -> 0.23.46.
This fixes several security bugs, e.g. https://rustsec.org/advisories/RUSTSEC-2026-0349

Files Modified:

  • Cargo.lock

03b5b85d867e948f8f929b75e7384d0c4aa71b96 by Mark Hammond <mhammond@skippinet.com.au>

https://github.com/mozilla/application-services/commit/03b5b85d867e948f8f929b75e7384d0c4aa71b96
Authored: 2026-10-15 12:52:14 +0000
Committed: 2026-10-15 12:52:14 +0000

Bug 2080694 - Make sync15 cope with meta/global records written by per-device-choice clients (#7651)

Clients that choose engines per device (initially Desktop) keep engine sync
IDs in meta/syncids rather than meta/global, and freshly-started accounts have
a meta/global with no engines and no declined engines. Make existing ("account"
model) mobile clients behave well with them, so these changes can be uplifted:

  • When fixing up a missing engine in meta/global, adopt a matching meta/syncids
    entry instead of minting a new sync ID, which would force every per-device
    client to reset that engine. Only 404 or an unparseable record means there's
    nothing to adopt; other errors fail the sync, before any local state changes.
    We only ever read meta/syncids. This matches desktop's behaviour in bug 2075022.
  • A meta/global with neither engines nor declined engines no longer turns
    every engine on: we keep our own declined list and publish it, as an old
    Desktop does.
  • new_global() no longer puts declined engines in engines, again matching desktop.
  • Track the meta collection timestamp separately from meta/global's, so a
    meta/syncids write doesn't defeat the cached-state fast path for good.

Files Modified:

  • CHANGELOG.md
  • components/sync15/src/client/coll_state.rs
  • components/sync15/src/client/state.rs
  • components/sync15/src/client/storage_client.rs
  • components/sync15/src/record_types.rs

9be28d24cbc806eea2d9af5258a28ae6ded5080b by tessaheidkamp <78563649+theidkamp@users.noreply.github.com>

https://github.com/mozilla/application-services/commit/9be28d24cbc806eea2d9af5258a28ae6ded5080b
Authored: 2026-10-15 11:03:20 +0000
Committed: 2026-10-15 11:03:20 +0000

Bug 2080209 - List credit cards without decrypting them (#7650)

Listing cards by name, last four digits and expiry needs neither the number
nor the CVV, but get_all_credit_cards decrypts both for every card. Where
the key is NSS's that can put a primary password prompt in front of a user
who only opened a list, and Desktop discards the numbers it prompted for:
its records carry a mask built from cc_number_last_4.

list_credit_card_candidates returns CreditCardCandidate, the card minus its
encrypted fields, with cc_number_last_4 and has_cvv in their place. Like
list_candidates in logins it never touches the key. The number and CVV of
the one card a user picks still come from get_credit_card.

has_cvv, read from the ciphertext being non-empty, is what Desktop's
payment methods dialog and the cc-csc autocomplete filter need from a
list: whether a code exists, never its value.

Files Modified:

  • CHANGELOG.md
  • components/autofill/src/autofill.udl
  • components/autofill/src/db/models/credit_card.rs
  • components/autofill/src/db/store.rs

d785f1dcb08b18f319ba8956b15cc7e79ee0aeb0 by Alexandre <Almaju@users.noreply.github.com>

https://github.com/mozilla/application-services/commit/d785f1dcb08b18f319ba8956b15cc7e79ee0aeb0
Authored: 2026-10-15 00:25:29 +0000
Committed: 2026-10-15 00:25:29 +0000

ads-client: make telemetry a singleton with the glean-sym API (#7653)

  • Make ads-client telemetry a singleton with the glean-sym API

Replace the T: Telemetry generic threaded through AdsClient, MARSClient,
MARSTransport, AdsStoreBuilder and AdResponse::parse with free
telemetry::record_* functions backed by a process-wide singleton. The
recording API matches the one glean-sym will use, so moving to glean-sym
later only swaps the backend.

For now the backend forwards to a core Telemetry trait, which the FFI
layer implements by wrapping the MozAdsTelemetry callback.
MozAdsClientBuilder::build() installs it and MozAdsClient::shutdown()
uninstalls it, unless another client has since replaced it.

  • Simplify ads-client telemetry install and centralize labels
  • Replace the installation handle with plain telemetry::install() and
    telemetry::uninstall(); telemetry is set up once per process, and
    AdsClient::shutdown() drops the callback.
  • Keep MozAdsTelemetryWrapper private to the FFI telemetry module.
  • Define every metric label in telemetry.rs, one enum per metric
    mirroring metrics.yaml.
  • Move NoopMozAdsTelemetry to test_utils.
  • Update relevance test for the ads-client telemetry singleton

Files Added:

  • components/ads-client/src/telemetry/backend.rs

Files Modified:

  • CHANGELOG.md
  • components/ads-client/docs/usage-javascript.md
  • components/ads-client/docs/usage-kotlin.md
  • components/ads-client/docs/usage-swift.md
  • components/ads-client/integration-tests/tests/ads_store.rs
  • components/ads-client/src/ads_store.rs
  • components/ads-client/src/ads_store/builder.rs
  • components/ads-client/src/client.rs
  • components/ads-client/src/client/config.rs
  • components/ads-client/src/ffi.rs
  • components/ads-client/src/ffi/telemetry.rs
  • components/ads-client/src/lib.rs
  • components/ads-client/src/mars.rs
  • components/ads-client/src/mars/ad_response.rs
  • components/ads-client/src/mars/transport.rs
  • components/ads-client/src/telemetry.rs
  • components/ads-client/src/test_utils.rs

d08654572909316a1ea1b4383ae7788c27dd25e1 by bendk <bdk@mozilla.com>

https://github.com/mozilla/application-services/commit/d08654572909316a1ea1b4383ae7788c27dd25e1
Authored: 2026-10-14 23:14:18 +0000
Committed: 2026-10-14 23:14:18 +0000

Fix breadcrumbs field in error support (#7658)

#7636 broke the app-services-error-reporter tracing event fields by
renaming breadcrumbs to breadcrumb_string. This caused crashes on
Android when errors were reported.

Rename it back to breadcrumbs and add a test so that this doesn't
happen again.

Files Modified:

  • Cargo.lock
  • components/support/error/Cargo.toml
  • components/support/error/src/error_tracing.rs

36f1b0ea4bcd28df6e43fea0054986f283faa518 by Beth Rennie <beth@brennie.ca>

https://github.com/mozilla/application-services/commit/36f1b0ea4bcd28df6e43fea0054986f283faa518
Authored: 2026-10-14 19:19:11 +0000
Committed: 2026-10-14 19:19:11 +0000

Bug 2053517 - Remove pref-key support (#7559)

This feature has not been used in a long time and leads to a lot of
confusion with gecko-prefs.

Files Deleted:

  • components/support/nimbus-fml/fixtures/fe/pref_overrides.fml.yaml
  • components/support/nimbus-fml/test/pref_overrides.kts
  • components/support/nimbus-fml/test/pref_overrides.swift

Files Modified:

  • CHANGELOG.md
  • components/nimbus/android/src/main/java/org/mozilla/experiments/nimbus/FeaturesInterface.kt
  • components/nimbus/android/src/main/java/org/mozilla/experiments/nimbus/Nimbus.kt
  • components/nimbus/android/src/main/java/org/mozilla/experiments/nimbus/NimbusBuilder.kt
  • components/nimbus/android/src/main/java/org/mozilla/experiments/nimbus/internal/FeatureHolder.kt
  • components/nimbus/android/src/test/java/org/mozilla/experiments/nimbus/util/TestNimbusBuilder.kt
  • components/support/nimbus-fml/fixtures/android/runtime/Context.kt
  • components/support/nimbus-fml/fixtures/fe/misc-features.yaml
  • components/support/nimbus-fml/src/backends/frontend_manifest.rs
  • components/support/nimbus-fml/src/backends/kotlin/gen_structs/bundled.rs
  • components/support/nimbus-fml/src/backends/kotlin/gen_structs/filters.rs
  • components/support/nimbus-fml/src/backends/kotlin/gen_structs/mod.rs
  • components/support/nimbus-fml/src/backends/kotlin/gen_structs/primitives.rs
  • components/support/nimbus-fml/src/backends/kotlin/templates/FeatureTemplate.kt
  • components/support/nimbus-fml/src/backends/kotlin/templates/ImportedModuleInitializationTemplate.kt
  • components/support/nimbus-fml/src/backends/kotlin/templates/macros.kt
  • components/support/nimbus-fml/src/backends/mod.rs
  • components/support/nimbus-fml/src/backends/swift/templates/FeatureTemplate.swift
  • components/support/nimbus-fml/src/backends/swift/templates/macros.swift
  • components/support/nimbus-fml/src/fixtures/mod.rs
  • components/support/nimbus-fml/src/frontend.rs
  • components/support/nimbus-fml/src/intermediate_representation.rs
  • detekt-baseline.xml

c0f2af40e5d6ef4f9fa673e48ba3218921a3ed32 by Glenda Leonard <75265513+gleonard-m@users.noreply.github.com>

https://github.com/mozilla/application-services/commit/c0f2af40e5d6ef4f9fa673e48ba3218921a3ed32
Authored: 2026-10-14 15:53:37 +0000
Committed: 2026-10-14 15:53:37 +0000

AC-206: include relevance scores in tile ad requests (#7647)

Files Modified:

  • CHANGELOG.md
  • components/ads-client/docs/usage-javascript.md
  • components/ads-client/docs/usage-kotlin.md
  • components/ads-client/docs/usage-swift.md
  • components/ads-client/src/client.rs
  • components/ads-client/src/ffi.rs
  • components/ads-client/src/lib.rs
  • components/ads-client/src/mars.rs
  • components/ads-client/src/mars/ad_request.rs

Duplicate of this bug: 2082405
Assignee: nobody → update-bot
Status: NEW → ASSIGNED
Depends on: 2082524
Blocks: 2082546

It looks like we experienced one or more build failures when trying to apply this
update. You will need to apply this update manually; you can replicate the patch
locally with ./mach vendor mobile/android/android-components/plugins/dependencies/src/main/java/moz.yaml. I'm going to abandon the Phabricator patch and
let you submit a new one.

If the build failure wasn't caused by a library change, and was instead caused by
something structural in the build system please let my maintainers know in
Slack:#secinf.

I do my best to automatically add new files to the build, but some moz.build files
are complicated and you may need to fix them manually.

Flags: needinfo?(dmeehan)
Attachment #9661662 - Attachment is obsolete: true

This bug is being closed because a newer revision of the library is available.
This bug will be marked as a duplicate of it (because although this bug is older, it is superseded by the newer one).

Status: ASSIGNED → RESOLVED
Closed: 1 month ago
Duplicate of bug: 2082711
Resolution: --- → DUPLICATE
No longer blocks: 2082546
No longer depends on: 2082524
Flags: needinfo?(dmeehan)
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: