Status Update
Comments
ru...@gmail.com <ru...@gmail.com> #2
Knp harus begini?
vi...@google.com <vi...@google.com>
bi...@gmail.com <bi...@gmail.com> #3
This is a blocker for me in upgrading a Playstore Wear OS app from API 28 to API 30.
bi...@gmail.com <bi...@gmail.com> #4
The warning from the NotificationService is wrong as the call to Toast in the code is a simple one, it is not using a custom toast.
It comes from the watch face code generated by the AS studio wizard:
Toast.makeText(getApplicationContext(), R.string.message, Toast.LENGTH_SHORT).show();
It comes from the watch face code generated by the AS studio wizard:
Toast.makeText(getApplicationContext(), R.string.message, Toast.LENGTH_SHORT).show();
bo...@google.com <bo...@google.com>
ms...@google.com <ms...@google.com>
bi...@gmail.com <bi...@gmail.com> #5
is...@google.com <is...@google.com>
rk...@google.com <rk...@google.com>
ys...@google.com <ys...@google.com> #6
From the other bug "I don't believe I should have to buy a physical API30 WearOS device to test with to meet new PlayStore version restrictions." and "API30 WearOS or the WearOS API30 emulator"
It's not clear it's an emulator bug, I'll test on a device and close if it's the same.
ys...@google.com <ys...@google.com> #7
Working on API 33 Emulator from a Watchface TapListener. But same issue ("Blocking custom toast") on Wear API 30 emulator.
ys...@google.com <ys...@google.com> #8
I think dupe of
bi...@gmail.com <bi...@gmail.com> #9
Any progress on this? It is still a blocker for updating my App.
On Wed, 4 Oct 2023, 10:46 , <buganizer-system@google.com> wrote:
On Wed, 4 Oct 2023, 10:46 , <buganizer-system@google.com> wrote:
ys...@google.com <ys...@google.com> #10
This is closed as a dupe, you should comment on
Description
1) Create a new Wear OS Project for API30 with an Interactive Watch face module in Java - min SDK 30 (using the new module wizard built into AS)
2) Build and run the Watch face in a WearOS API30 emulator.
3) Click/Tap on the watch face
4) Observe that no Toast is shown, rather
NotificationService system_process W Blocking custom toast from package com.example.wristface due to package not in the foreground
is seen in logcat
5) Drop minSDK to 28, rebuild and run in a WearOS API28 emulator.
6) Click/Tap on the watch face
7) Toast shown OK
8) Rerun on Wear OS API30 emulator
9) Click/Tap on the watch face
10) Result as at 4) above.
Showing a Toast from a watch face or complication is a quite reasonable thing to do on WearOS.
It's not clear if the bug lies in API30 WearOS or the WearOS API30 emulator.
See my earlier bug report on the same topic