IssueTracker

We have an application which read characteristics for BLE peripherals which advertise a specific service ID. This service ID changes often. Scanning, connection, service discovery, and characteristic reading all work fine when the peripheral and central are not bonded. However, the list of BLE services seems to be cached/stale once bonded even after initiating service discovery and reading the latest services.

Once bonded, the sequence of events is:

• Peripheral advertises gatt service with ID <newServiceUuid>
• Scan for BLE peripheral with scanFilter for <newServiceUuid>
• Device found with bondState BOND_BONDED
• onConnectionStateChange called with success
• call BluetoothGatt::discoverServices called
• onServicesDiscovered called
• calling getService(UUID.fromString(newServiceId) returns null
• The list of services on the gatt object are services which are no longer advertised / were discovered during the first discovery attempt after bonding.

It appears the onServiceChanged callback is not called either.

The stales service list seems to persist indefinitely until the devices are un-bonded, or we manually call BluetoothGatt::refresh via reflection. App/device restarts don't make any difference.

• The issue is present on Android 12, 13, 14, and 15.
• Reproduced on Pixel 6a, Pixel 8a, Pixel 9 Pro XL, Samsung z fold 3

Since the refresh() method on BluetoothGatt resolves our issue, we're requesting that this method be made public so our application can call it without using reflection. Or please provide guidance as to how we should achieve this behavior otherwise.

I found another filed issue that seems similar, but not exactly identical - https://issuetracker.google.com/issues/242755161. We're able to find the BluetoothDevice in our case, just not fetch the service after service discovery (even though we searched for the device using a ScanFilter with the same service id).