Change theme
Help
Press space for more information.
Show links for this issue (Shortcut: i, l)
Copy issue ID
Previous Issue (Shortcut: k)
Next Issue (Shortcut: j)
Sign in to use full features.
Vote: I am impacted
Notification menu
Refresh (Shortcut: Shift+r)
Go home (Shortcut: u)
Pending code changes (auto-populated)
View issue level access limits(Press Alt + Right arrow for more information)
Unintended behavior
View staffing
Description
I am testing with the following example.
After setting the watch face on API level 30 or higher and entering the WatchFaceConfigActivity by pressing on the screen, then exiting, the Renderer.onDestroy() is called. The hash code of the instance that was drawing the watch face before entering WatchFaceConfigActivity is @90310b0, but when returning to the watch face, Renderer.onDestroy() is called from an instance with the hash code @d083658. In other words, Renderer.onDestroy() is called from a different instance unrelated to the one that was previously rendering. I have confirmed that Renderer.onDestroy() does not occur in the same scenario on API level 28 or lower but does occur on API level 30 or higher.