google-ar
ViewRenderable doesn't update on Android 10
Description Once the ViewRenderable has been attached to a node and rendered, it is not updated anymore on Android 10. I could observe the correct behavior on a device with Android 9.
Reproducibility This bug is reproducible by compiling and launching the solar system demo app on a Pixel 3 with the latest version of Android 10 (QP1A.191995.007) with the latest version of Google Play for AR (1.12.190826106)
Observed behavior When the sliders are touched and moved, we can see the planets going faster or slower, but the thumbs of the sliders are not moving.
Expected behavior The views are updated to reflect their respective states (the sliders are moving with the touches)
I am experiencing this issue as well. I have 2 emulators side-by-side, both Pixel 2, and both with identical versions of Google Play Services For AR (for emulator). The only difference between the two is that one is API 28 and the other is API 29. This issue appears for API 29, but works correctly for API 28.
As @bmonjoie described, the ViewRenderable appears to render properly, but any updates are not shown. In my app, I am attempting to animate the alpha of a View from 0 to 1. Each tick of the animation, I am logging the alpha of the view, and according to the logs, the alpha is in fact increasing from 0 to 1. However, after the first tick (when the alpha is ~0.1 or so), the subsequent alpha updates do not appear. So, even though view.getAlpha() returns 1.0 by the end of the animation, the view remains at ~10% opacity. Once again, this only happens on API 29; the animations work fine on API 28.
Same thing for me. ViewRenderable's view's scale is being updated with a ValueAnimator. On Android Pie, the view's scale is animation. (Galaxy S10) On Android 10, the view's scale is changed, but ViewRenderable's appears to be stuck at a single value (Pixel 3)
Thanks for the report. Apologies for the delay on responding. There is indeed a bug with view renderables updating after the first frame on Android 10. We have a fix for this internally which will be rolling out in the next version of Sceneform.
