Status Update
No update yet.
Comments
vi...@google.com
Android 5.0, 5.1: it shows context menu at top of screen, not as popup. See screenshots.
Android framework doesn't support floating toolbar before 23. So this is intended behavior.
The crash information suggests that this is an error from Snapshot. chuckj@ can you please take a look? I don't know what exactly caused the readError in Snapshot, any suggestions? Thanks a lot!
hu...@gmail.com
This looks like another instance of 193006595 which I am looking at now.
vi...@google.com
Branch: androidx-main
commit beeb84e7be604088ad40e080a8d0adb1bacbf695
Author: Chuck Jazdzewski <chuckj@google.com>
Date: Thu Jul 08 10:04:28 2021
Remove updating the transparent snapshot
A transparent snapshot is create for the block exeucted by
`Snapshot.observe()` which registers read and write observers
but without creating a snapshot. The code to advance the
global snapshot, however, created a new transparent snapshot in
an attempt to update it to the new global snapshot it just
created. This is not necessary, however, as the transparent
snapshot will retrieve the current global snapshot from
`currentGlobalSnapshot` instead of `previousSnapshot` if
`previousSnapshot` is `null`. With the previous code, if the
global snapshot is advanced by applying a new snapshot the
"updated" transparent snapshot will be left referring to an
older snapshot instead of the most recent global snapshot.
Any snapshot object created in the newly applied snapshot
will throw an exception when it is accessed, as reported in
the bugs. The solution is to remove the apparent vetiagal code.
Test: ./gradlew :compose:r:r:tDUT
Fixes:
Change-Id: I2c0d0b8f57bf70e5a98ea36ed141d97142a5e53e
M compose/runtime/runtime/src/commonMain/kotlin/androidx/compose/runtime/snapshots/Snapshot.kt
M compose/runtime/runtime/src/test/kotlin/androidx/compose/runtime/snapshots/SnapshotTests.kt
hu...@gmail.com
Any update? This is resulting in me sleeping without the watch.
si...@gmail.com
hu...@gmail.com
This is still the case. An answer would be appreciated.
hu...@gmail.com
The last updates (phone and watch) still did not fix this.
hu...@gmail.com
Another update, issue is still ongoing.
vi...@google.com
id...@gmail.com
hu...@gmail.com
hu...@gmail.com
Making this obsolete without even having looked at by a real person tells a lot about the Google of today.
For the record, this is still happening, was never fixed, and was never acknowledged. Good riddance
lu...@gmail.com
I got a Pixel watch 3 just over a week ago and hit this problem very quickly. My watch is listed as up to date (Android version:14, last updated Sept 5, 2024). My phone is also listed as up to date (Android version:14, last updated Sept 5, 2024).
I have exactly the same problem as the report originally outlined, so I don't believe this is obsolete.
Is it possible to have the status re-reviewed?
Thanks!
id...@gmail.com
"We have shared this with our product and engineering team and will update this issue with more information as it becomes available"
But no update given..
hu...@gmail.com
Original reporter of the issue here.
FWIW, this is no longer an issue for me. It turned out that the "Watch" app on the phone did not update, ever. I had to manually enable updates on Google Play, even though this is a preinstalled app, so I have expected it to work correctly, but it did not...
What I did: open the Watch app on Google Play (I did: long press Watch on the launcher > App info > App details > Play Store opens), update it. Hopefully this will fix the issue for anyone else affected, but I would not expect an answer from Google, other than the random, useless bot replies.
id...@gmail.com
hu...@gmail.com
You can verify if its fixed manually as well:
- enable the sync in the watch app
- manually enable dnd on phone
- watch should enable dnd as well
- manually enable bedtime mode on phone
- watch should enable bedtime mode as well
- manually disable bedtime mode on phone
- watch should disable bedtime mode
- if dnd remains enabled on phone, the issue is fixed
id...@gmail.com
Tested and confirmed working for me 👍🏽
Description
Enabling "Sync across watch and phone" will change the behaviour when Bedtime Mode ends, either manually or automatically. This is messing up schedules, where Bedtime Mode is meant to end earlier then Do Not Disturb.
This is happening on a Pixel 8 Pro and a Pixel Watch 2, both on the latest available OS and app versions.
Issue description - automatic schedules
Expected behaviour
Actual behaviour
(Change emphasised by bold text)
Simplified reproduction steps - manual
Expected behaviour
Actual behaviour
(Change emphasised by bold text)