23f620ee - platform/build/release

commit: 23f620ee4da254334b510156346bec13e4f651c1
[log]
author: boq-halyard-service-composite@system.gserviceaccount.com <boq-halyard-service-composite@system.gserviceaccount.com>
Thu Feb 13 01:21:37 2025 -0800
committer: boq-halyard-service-composite@system.gserviceaccount.com <boq-halyard-service-composite@system.gserviceaccount.com>
Thu Feb 13 01:21:42 2025 -0800
tree: b63715c30f2c476a13d2a6c8bd62731daa1df84e
parent: 9a205ec6b2bf5541d3541c2695a744eb29217af4 [diff]

Adding flag com.android.bluetooth.flags.empty_names_are_invalid to trunk_staging.

This change was automatically created by advancing the Gantry workflow at:
https://releasetracker.partner.android.com/changes/fgou79a000001?build_unique_id=ComAndroidBluetoothFlagsEmptyNamesAreInvalidLaunch-platform
Do not edit this file manually or revert this change - use the Gantry workflow to manage the state of this flag.

Bug: 395178934
Change-Id: I7a733d4d7ca009f737c66f160c82ced15601b156
Flag: com.android.bluetooth.flags.empty_names_are_invalid
Ignore-AOSP-First: AConfig change for future AOSP release

aconfig/trunk_staging/com.android.bluetooth.flags/empty_names_are_invalid_flag_values.textproto[Added - diff]

1 file changed

tree: b63715c30f2c476a13d2a6c8bd62731daa1df84e