After updating the SDK to version 0.22.6150 we noticed that ScrollViews reset their scroll offset once another navigation stack is placed over it. This occurs most of the time but not always.
It also affects ScrollViews that have been hidden with `display: none` and then re-added to the view.
This applies to all Scrollviews, horizontal and vertical.
App Name: ARTE App Link on Amazon Appstore (found through Developer Console → Actions column in App List → View on Amazon.com): ARTE - App on Amazon Appstore
Bug Severity
Select one that applies
Impacts operation of app
Blocks current development
Improvement suggestion
Issue with documentation (If selected, please share the doc link and describe the issue)
Other
2. Steps to Reproduce
Mail me for APK built with the current SDK
Launch app
Navigate to Main Screen
Scroll down → press enter on Title → scroll down → press enter → … repeat
Repeatedly press back to navigate to the Main Screen while observing the animations
3. Observed Behavior
Explain what actually happened, noting any discrepancies or malfunctions.
Sometimes the screen jumps from the top to the previously pressed title on the screen.
4. Expected Behavior
Describe what you expected the SDK to do under normal operation.
The screen is the same as the user left it previously, with no additional scroll animations
4.a Possible Root Cause & Temporary Workaround
Fill out anything you have tried. If you don’t know, N/A is acceptable
ScrollViews that are rendered off screen have their offset reset when re-rendered back on to the view
5. Logs or crash report
No logs are relevant
6. Environment
Please fill out the fields related to your bug below:
SDK Version: 0.22.6150
App State:Foreground
OS Information: Please ssh into the device via vega exec vda shell (or kepler exec vda shell for v0.21 and earlier) and copy the output from cat /etc/os-release into the answer section below. Note, if you don’t have a simulator running or device attached, the command will respond with vda: no devices/emulators found
Apr 07 14:35:11.570580 amazon-48589a0370c45b99 local0.info tv.arte.plus7[4157]: 2 I Volta: 547925757984 [ScrollableRenderObject] Not scrolling as scrollable already at requested position
Apr 07 14:35:11.579993 amazon-48589a0370c45b99 local0.info tv.arte.plus7[4157]: 2 I Volta: 547925757984 [ScrollableRenderObject] Not scrolling as scrollable already at requested position
Apr 07 14:35:11.580024 amazon-48589a0370c45b99 local0.info tv.arte.plus7[4157]: 2 I Volta: 547925757984 [ScrollableRenderObject] Not scrolling as scrollable already at requested position
Your colleague asked me to refine the report.
Here’s a full log produced by vega exec vda shell loggingctl log --follow --since now | tee Full_logs.txt | grep -i arte
We were able to diagnose the cause of the issue, and it wasn’t ScrollView resetting its offset.
The reason for these focus jumps was that pages that are deeper than -1 levels in the page stack would receive a phantom-focus when the current page was popped.