Fixed
Status Update
Comments
fa...@gmail.com <fa...@gmail.com> #2
Thanks for the report. I will route this to the appropriate internal team and update this when I hear back from them.
yb...@google.com <yb...@google.com> #3
One more detail, Data Layer event calls from the watch to the phone (running Android 13) do work on if the listener is in an Activity or Fragment.
yb...@google.com <yb...@google.com> #4
Also, I'm seeing this message in the Logcat:
"2022-06-12 18:47:15.156 1841-4562/? W/PackageManager: Intent does not match component's intent filter: Intent { act=com.google.android.gms.wearable.BIND_LISTENER"
"2022-06-12 18:47:15.156 1841-4562/? W/PackageManager: Intent does not match component's intent filter: Intent { act=com.google.android.gms.wearable.BIND_LISTENER"
yb...@google.com <yb...@google.com> #5
Experiencing the same issues, please see my other report for any useful logs:
https://issuetracker.google.com/issues/235673375
yb...@google.com <yb...@google.com>
sh...@google.com <sh...@google.com>
sh...@google.com <sh...@google.com>
sh...@gmail.com <sh...@gmail.com> #6
+1, can confirm it doesn't work on Android 13:=
2022-07-15 11:26:15.023 589-5347 PackageManager pid-589 W Intent does not match component's intent filter: Intent { act=com.google.android.gms.wearable.BIND_LISTENER cmp=xxx/xxx.WatchMessageReceiver }
2022-07-15 11:26:15.023 589-5347 PackageManager pid-589 W Access blocked: ComponentInfo{xxx/xxx.WatchMessageReceiver}
2022-07-15 11:26:15.023 589-5347 ActivityManager pid-589 W Unable to start service Intent { act=com.google.android.gms.wearable.BIND_LISTENER cmp=xxx/xxx.WatchMessageReceiver } U=0: not found
em...@gmail.com <em...@gmail.com> #7
Note that I've been able to make it work by:
- Adding
<action android:name="com.google.android.gms.wearable.BIND_LISTENER" />
in the intent filter - Removing
<data android:scheme="wear" android:host="*" />
But I feel like this is not something we should do
Description
Version used: 1.0.0-alpha2
Devices/Android versions reproduced on: Emulator 26
Room with LiveData throws exception on "WITH" clause. I think LiveData tries to register on the name of WITH clause as if it is a table. Same SQL query works with Room without LiveData.
SQL query:
WITH split(i,l,c,r) AS (
SELECT book.bookId, 1, author||'|', '' FROM book
UNION ALL
SELECT i,
instr(c,'|') AS vLen,
substr(c,instr(c,'|')+1) AS vRem,
substr(c,1,instr(c,'|')-1) AS vCSV
FROM split
WHERE vLen>0
)
SELECT DISTINCT split.r FROM book , split
WHERE book.bookId=split.i AND split.r<>''
ORDER BY split.r
Table example:
CREATE TABLE book (
bookId INTEGER PRIMARY KEY,
author TEXT
);
INSERT INTO book (author) VALUES
('|A||B||C|'),
('|A||D|'),
('|B||D|');
Exception:
FATAL EXCEPTION: pool-2-thread-1
Process: tr.name.fatihdogan.books.debug, PID: 15674
java.lang.IllegalArgumentException: There is no table with name split
at android.arch.persistence.room.InvalidationTracker.addObserver(InvalidationTracker.java:228)
at android.arch.persistence.room.InvalidationTracker.addWeakObserver(InvalidationTracker.java:255)
at tr.name.fatihdogan.books.repository.BookDao_Impl$7.compute(BookDao_Impl.java:621)
at tr.name.fatihdogan.books.repository.BookDao_Impl$7.compute(BookDao_Impl.java:609)
at android.arch.lifecycle.ComputableLiveData$2.run(ComputableLiveData.java:87)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1133)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:607)
at java.lang.Thread.run(Thread.java:761)