Fixed
Status Update
Comments
cl...@google.com <cl...@google.com>
cl...@google.com <cl...@google.com> #2
Information redacted by Android Beta Feedback.
ap...@google.com <ap...@google.com> #4
The issue has been fixed and it will become available in a future Android release. Please keep an eye on the release notes(
jo...@gmail.com <jo...@gmail.com> #5
How long till this hit stable?
The issue is really annoying. Pixel 8 Pro + Pixel Buds A-Series + Pixel Watch. This should work without any issue and instead we have to manually disable Bluetooth on the watch whenever we use the buds. Don't you have quality controls on your products interactions?
pr...@google.com <pr...@google.com> #6
Have the same issue. Pixel buds disconnect constantly. Works without issue on Pixel 6 with Pixel Watch.
-Pixel 8, Pixel Buds A, Pixel Watch-
-Pixel 8, Pixel Buds A, Pixel Watch-
Description
Technical Details
This sample app showcases how there is no error propagation available when using default PagingSource in queries. The sample app has a text field that filters a list of animals. The MATCH statement is used to throw an Exception but there may be other ways to do this as well.
Steps to reproduce:
Under the covers, the default implementation of PagingSource in DAO queries is LimitOffsetPagingSource.
In this particular case, we have options to mitigate this:
In lieu of an actual fix, there should probably be documentation that acknowledges and warns about situations using the default PagingSource, particularly in instances where the MATCH statement is used with user input since this is a common use case with FTS4 entities that requires special care.
There are a few StackOverflow issues that mention this issue, both reported years ago, but I could not find any bug reports: