39233ff029c522d790008aa25cef8b295a141b4a
AbstractRemoteService was spun off from RemoteFillService, which only supports 1 pending request while not bound to the service - if a new request comes, it cancels the previous one. This behavior is fine for Autofill, but for Content Capture all requests must be queued. In fact, the upcoming CTS tests for Content Capture were failing because the 1st PendingOnContentCaptureEventsRequest would cancel the pending PendingSessionLifecycleRequest. So, this CL fix this problem by creating 2 subclasses: - AbstractSinglePendingRequestRemoteService - AbstractMultiplePendingRequestsRemoteService Test: atest CtsContentCaptureServiceTestCases CtsAutoFillServiceTestCases Bug: 111276913 Bug: 117779333 Change-Id: I43bb98be16f5def037f85a415e1f77799adf156e
Merge "Actually check for READ_PHONE_STATE permission for Voicemail query" am:
539f4f44c1 am: 5afc7541dd
…
…
…
…
Merge "[view_compiler] cleanup: Use format-specific bytecode encoding functions" am:
9d599fde8e am: 6eeb8bef8d
Merge "Actually check for READ_PHONE_STATE permission for Voicemail query" am:
539f4f44c1 am: 5afc7541dd
…
Description
No description provided
Languages
Java
73.7%
Kotlin
14%
PowerBuilder
5.8%
C++
5.2%
AIDL
1%