Scroll Issues When Upgraded to 3.18062.26

[keathley]

Hi, I have a PowerApp that is behaving undesirably after the recent update.  Some notes about this app:

Prior to Update

1. App was on version 3.18061.15
2. App uses Sharepoint lists for data (including some that are used to drive cascaded dropdown fields)
3. Edit form screen scrolling is smooth and very fluid
4. Several Yes/No toggle switches drive the visibility of other text fields (if yes, no comment is necessary type of behavior).  This is done by setting the textbox's datacard's visibility formula to the .Value of the toggle switch.
5. When toggle switches are changed, the screen does not scroll, even though new fields are added / removed.

If I open the application in the designer and save it (making no change other than the text of a label, so that I have the save and publish option) a few things occur:

After Update

1. App is updated to version 3.18062.26
2. Edit form screen scrolling is now very choppy, sometimes it takes 2-3 swipes to get it to scroll on an iOS device
3. Changing toggle fields that change the visibility of other fields now causes the form to scroll back to the top of the screen.
4. These new behaviors go away if I switch the app to Classic render mode (File -> App Settings -> Advanced Settings -> Render in classic mode) or if I use version control to roll the prior version back.

My Questions

1. Is there a way I can avoid the "Scroll to top" and choppy screen scrolling without using classic mode?  
2. How long will classic mode be available?  Is this expected to go away in the future?
3. Are there release notes specifically for the 3.18062.26 release?  I have only been able to find these which do not seem to include the recent changes.

Thanks in advance,

Joey

[v-monli-msft]

Hi @keathley,

I cannot reproduce your issue. Even when the classic mode is off, in PowerApps mobile app on iOS, the scrolling works just fine. 

Also, please describe in detail about what did you mean by "Changing toggle fields that change the visibility of other fields". Please share the related formulas and controls. Is this happening inside a Edit Form?

So far there is no such offical statement about cancelling the classic mode option.

Regards,

Mona

[keathley]

@v-monli-msft

I have created everything brand new this morning (new sharepoint list, and new powerapp) to recreate the issue myself.  Below are the steps I followed.

• In SharePoint O365 Online create a new list

• Create Yes/No (toggle) columns on the list (do this x10).  Select Default value of "No"

• Create "single line of text" comment boxes (x10 as well).  Default options ok for these.

• I turned off the "required" flag for the "title" field.  I also ordered the columns such that each toggle is next to its comment (Toggle1, Comment1, Toggle2, Comment2, etc).

• Use the PowerApps -> Create an app menu to create a new app.

• Name the app

• From within PowerApps select "EditForm1" from the screens list

• Open the Data panel

• Turn on all of the toggles and comments, and then reorder fields such that comments follow each of their toggles (as done previously on the SharePoint side)

• Click on each toggle switch to identify its name in the "Screen" panel.  In this example I am clicking on the toggle for "Toggle1" and see that its name is "DataCardValue10"

• Select the Comment Datacard and set its "Visible" property to the formula below (filling in the appropriate toggle name for each comment box's forumla).  Note that Comment1 will be hidden when Toggle1 is set to "Yes."  This logic follows for each comment box (Comment2 is hidden when Toggle2 is Yes, Comment3 is hidden when Toggle3 is Yes, etc.)

Not(DataCardValue10.Value)

• Save the app

• Publish the app

• Open the App on an iOS device (I have not tested on any other devices).  I used an iPhone 7 running 11.3, although I do not believe this matters.
• Click the + (new record button) in the top right corner of the screen
• Try to scroll to the bottom of the app.  You will note the choppiness of the scrolling.  
• Change Toggle 10 from "No" to "Yes"  You will note that the form scrolls back to the top of the screen.

At this point if you:

• Turn on classic Mode:

• Save & Publish again
• Close and re-open the app on the phone at least 2 times (to ensure the latest version is downloaded)
• Click the + (new record button) again

The issues are now gone when you use the app on your phone again.

Appologies to everyone for the lenght of the post, and thanks in advance for any assistance you can provide.

Joey

[AKotb]

Thanks so much for reporting the issue,

we identified the source of the problem and we will be working on a fix.

as soon the fix is deployed you can switch the classic rendering mode off

[keathley]

Thanks @AKotb was the fix included in the recent 3.18063.33 release?  If not, do you know which release it is slated for?  Thanks so much for addressing this.

Joey

[daviddraper2]

Yes, I have this same issue!

Thank you for reporting it, too.

[AKotb]

if everything goes according to plan the fixes should be part of the 3.18071 release which is hopefully going to be deployed in 2 weeks.

meanwhile you can use the classic mode.

Thanks again for reporting this and for the detaled steps 🙂

[AKotb · Accepted solution]

1807.3 should be deployed everywhere, can you try to disable render in classic mode and republish the app ?

Thanks

[keathley]

@AKotb I can confirm that the issue appears to be resoved with the 3.18073.28 release.  Thanks for the quick turn around on this issue.

Joey

[daviddraper2]

Can you explain what benefits / performance enhancements the non-classic mode offers me in the Studio as well as end-users on their apps?

---

@AKotb wrote:

1807.3 should be deployed everywhere, can you try to disable render in classic mode and republish the app ?

Thanks

---