- Removes banned_data_types_, PUBLIC identity advertisements will never have
any corresponding credentials anyways, so decryption will always be skipped
and this is now guarenteed by asserts in UpdatePublicCredentials
- Filtering adv based on identity is moved into advertisement Filter which
already contains the requested identity info from scan_request
- LegacyPresenceScanFilter is no longer used by AdvertisementDecoder since
this is not being used anywhere at the moment
- Cleanup miscellaneous clang-tidy lints about missing or unused includes
PiperOrigin-RevId: 620086399
Nearby Presence scanning sessions may be very long. We need a way to notify the scanner that new credentials were added during scanning.
`SubscribeForPublicCredentials()` allows us to subscribe for such updates.
PiperOrigin-RevId: 502699345
1. Update the API to accept the credentials on input instead of credential manager.
2. Update the test with values using the LDT encryption.
These changes allow us to have a more asynchronous implementaion.
When broadcasting we can:
1. Fetch the private credentials asynchronously.
2. Create the advertisement and start broadcasting when the credentials have been fetched.
When scanning we can:
1. Fetch public credentials asynchronously.
2. Start scanning for advertisements.
3. Update the decoder when new credentials are fetched.
PiperOrigin-RevId: 493998041
Add StopScan and refactor StartScan to return a sesssion id.
Move handling of StartScan, StopScan and NotifyFoundBle to the same thread to avoid race conditions.
Implement start advertising in service controller.
PiperOrigin-RevId: 492016697
Define and use an NP private AdvertisementData structure instead of the low level BleAdvertisementData,
The APIs look cleaner this way.
PiperOrigin-RevId: 486224840
Francis Tsui