A bug has occurred since the last version of powerapps (3.19052.19)

[pr0g]

Hello,

A bug has occurred since the last version of powerapps (3.19052.19)

Since the last update, my entire application is no longer working.
The Fields displaying the information from the selected item in the gallery no longer display anything or display data from another item.
From now on, there is a problem with Gallery.selected and I do not know why ...
is there a way to fix it?

Thank you

[iSpeak]

I'm having the same problem with Gallery.Selected not working. It must have happened between PA release 3.19051.14 and 3.19052.19. All of the sudden my galleries are almost worthless because regardless of what item's selected, other objetcs don't change accordingly as they should. I created a quick dummy app and the gallery.selected worked fine to update the text in a label. Very that it's not working in my actual app.

[SynergyM]

Has Microsoft acknowledge this problem yet?  My apps look absolutely destroyed in the editor right now.  Values referenced from inside separate galleries aren't working(sometimes?).  I'm not sure what to do.

[Raynok1]

Yes On page 1, according to Corey the powerapps team have acknowledged the issue and is busy rolling out a fix. So far thats it. 

If we had the powerapps studio links of previous versions we could open our apps, continue editing and publish them in those versions. I've been looking, the only one I found is https://create.powerapps.com/v3.19045.16.112802239/studio/# . 

[SynergyM]

Thank you.  I suppose we'll wait for the fix.  I was able to find a link for v3.19052.17:

https://create.powerapps.com/v3.19052.17.114642643/studio/#

[Raynok1]

Really have been trying to find other studio's even going as far as trying to figure out how the website determines which version it decides to use. The rabit hole has been real. This give me hope, thank you.

[_Corey_]

Update: We are still working to deploy the hotfix. We encountered a technical issue which prevented us from deploying sooner.  We expect the deployment to complete shortly. I will update this thread again once hotfix deployment is complete.

[Raynok1]

@_Corey_  Thank for the update.

Please can you provide your recommend studio version to use in the interim in order for editing and publishing. 

So far these have come to light, one from one of your other threads and another from another community member

1.) https://create.powerapps.com/v3.19045.16.112802239/studio/# . from your other threads

2.)  https://create.powerapps.com/v3.19052.17.114642643/studio/# . from SynergyM 

3.) It would be great if there was a website with a list of valid studio versions, The latest down to what the powerapps team feel still okay for the community to use.

4.) More so, give the app makers the ability to select different studio version for those occasional situations 😉

[_Corey_]

@Raynok1, et. al.,

If you have not already upgraded your app(s) to 3.19051 or higher, I suggest that you use the Studio version https://preview.create.powerapps.com/v3.19045.16.112802239/studio/ 

If you have upgraded your app to 3.19051 or higher, you will have to hold on tight just a little longer.  The underlying issue affects all patch versions of 3.19051 and 3.19052.

*If* you have only made *minor* revisions in these latest versions, I would suggest restoring your app to a version previous to 3.19051 and then use Studio version https://preview.create.powerapps.com/v3.19045.16.112802239/studio/  to re-apply those changes.

[_Corey_ · Accepted solution]

Final update: A hotfix to address the issue has been successfully deployed. The updated Studio version is v3.19052.20.115177617. You will need to edit your app(s) in Studio and re-publish for the fix to take effect--please remember that it make take up to a few minutes for the newly published app(s) to be packaged and available to players (web or mobile). Please report any issues you experience with this update.

Once again, we are sorry for any inconvenience this has caused.

[v-xida-msft]

Hi @pr0g ,

Just an update -- Now, PowerApps has released a new version of PowerApps -- 3.19052.20. The issues that you mentioned has been fixed within this new version.

On your side, please consider run your PowerApps, check if it has been upgraded to the latest version (3.19052.20). Then re-create a new app using the latest version PowerApps, check if the issue is solved.

Best regards,