This morning I opened an app in the studio and it is behaving strange. It works normally in the player (web).
Galleries are not responding; the hover effect is there but its not possible to select anything. When I navigate back and forth in the app suddenly the screen just goes grey. When I exit to the studio the screen and all screens look something like this:
Anyone else experiencing issues???
Solved! Go to Solution.
Hi I have same problem since last week. The gallery.selected do not change when i use diffrent row. See my post about my fault and my try to to have a workaround.
Kind regards Olle
@OllekThanks for replying! I created a ticket with high severity - MS called me up after 5 minutes and did some research/debugging. He would take it up directly with the PowerApps team as it's definitely something going on with the studio player. I will update this thread when they get back to me.
Hi @JohnP ,
Have you solved your problem?
Based on the issue that you mentioned, I have made a test, and don't have the issue that you mentioned.
Please consider turn off the "Improved app rendering (final validation)" option within Advanced settings of App settings of your app, re-load your app, check if the issue is solved.
Also please consider take a try to re-store your app to previous version, then re-publish it again, check if the issue has been fixed.
More details about restoring app to previous version, please check the following article:
as I have simuler problem I did what you was suggesting but it didn't work for me. I have still the problem. It started the at 9 may at the same time as powerapp-version went from 184.108.40.206 to 220.127.116.11. I have gone back to the version from 6 may with powerapp-version 18.104.22.168 though I have still the problem.
It seems that the galleri.selected values do not change when I select i other row.
Just to clarify - the app works perfectly fine when running in the web player. It behaves differently when running in the editor. Galleries are not responsive and after a while the editor crashes (see description/screenshot in my first post). This app has been extensively edited for the last year and this problem just recently appeared.
I tried your suggestions:
1. Restoring the app to a previoous version does not help. Running an older version in the editor exhibits the same behaviour (I tried going back several weeks).
2. I turned off "Improved app rendering" and the gallery behavior returned to normal (I had to delete some groupings for test purposes). But classic mode is going away soon so this isn't really a solution.
This sudden change in behaviour is extremely frustrating. To me it seems that "older" apps is somehow not compatible with the improved app rendering as I cannot reproduce this behaviour in newly created apps (and the player in the editor is somehow different than the standalone player).
Update: Our apps published with version 3.19043.16 works normally in the web player - apps published with 3.19051.20 do not. No version works with the studio player.
I post here again the test I did some day ago. It seems that the fault has a connection beteen the galleri and edit/new to you want to go to when you choose from the gallerit.
What I have tested is to copy code (screens) to a new app and I done this screen for screen. When I started with the screen with galleri it work fine, Then I copy the screen were I show the column från SharePoint and it still work fine. The I copy the update screen and the error is back. If I then delete the update screen the error is still there. I can only make disappear if I goes back to an earlier version.
So it seems to be something in the connection between the galleri (SharePoint List) I choose from and the update screen where I want to update column from SharePoint.
I feel your pain ... something definitely happened in the last release that trashed our apps. It's simply not acceptable! Can you try to disable "Improved app rendering" in the app settings and see if it resolves your problem? It did for me, but it's not a solution since "Classic rendering" is going away soon.
My guess is that "older apps" have some legacy code that don't translate/parse well into newer versions of the player since I cannot reproduce this behaviour if I create a new app and try to create a similar scenario.
@JohnP, can you please provide a session id so that I can take a look?