Bug in Version 3.21123.25 ?

[WarrenBelz]

Hi All,

This has just happened on a large production app - when saved in 3.21123.25, the banner below comes up in the opening screen as soon as the app is opened on an iPad.

A heap of testing done this morning by myself and @Anonymous (we work together) and concluding the following: -

• It only happens to one (very large and critical) app
• The app works perfectly under 3.21115.37
• Whether there are changes of not, resaving under 3.21123.25 triggers this error.
• PowerApps will not let me revert the authoring version - it only offers 3.21123.25 in the drop-down.
• We have two environments and it happens in both
• I have exported a package and re-imported - same result.
• There are only two Or() statements in App OnStart and commenting them out makes no difference

Other than a bug (which it might be), has anyone else seen this ?

[w1sd0m]

Latest updates have been unstable to say the least. I spent 18+ hours troubleshooting component bugs. What are symptoms of the internal error to the app?

[BCLS776 · Accepted solution]

Warren, I saw something similar with an app I was building around the time of that 3.21123.25 release. The error was similar - flagging a problem on an Or() statement - and was so vague I ran a monitor session to try to better understand the problem. I didn't save the monitor log, but if I remember right it was flagging a runtime error on a gallery that has a Filter() on the Items property. That Filter() needed some work anyway and once I made some edits to it the error vanished. Interestingly, the Filter() did not have Or functionality in it at all; only a couple of arguments linked by the default And logic. Datasource is a SharePoint List.

Sorry, no solution, but perhaps a monitor session will help you catch what's triggering the issue.

Bryan

[WarrenBelz]

Thanks Bryan,

Strangely a monitor session was a bit out of my thoughts as it was only erroring on the iPads (not on the PC in either play or edit mode). However, I now have run a session and the errors were there, just not displaying. To cut a very long (all afternoon) story short, it was all about the Visible properties of two buttons on the start screen and the DisplayMode of one of them. The formulas were a bit complex, but have worked perfectly for over two years. They were referencing some controls, but I ended up setting Variables for all the parameters as they changed and it now works without error. One button however had to be replaced with a new one to accept the code.

I would be interested to see if anyone else has experienced issues with the latest release.

@w1sd0m as per your question - see above

[virakones]

I had a similar issue and can confirm that a monitor session helped to identify the affected control and function.

I managed to resolve it by removing the function And (&&), and an older unused variable, but the formulas seemed to be syntactically correct - so not entirely sure what the issue was.

[AndrewCitera]

Was anyone able to isolate specifically what was breaking after the 3.21123 release and/or determine any fixes? Our team is facing similar challenges and have not been able to resolve.

[WarrenBelz]

Another one here

[james_hathaway]

Is there any news on when this bug is going to be fixed?

I just edited an App to fix a spelling mistake in a label, but now the published version is throwing this error all over the place - and actually preventing record saving in some instances!

Can we at least roll back to the last stable release?

This release is Buggy as Hell.

[AndrewCitera]

@james_hathaway agreed. What is even weirder is that we rolled back the published version to a prior studio version, but are still running into issues. Are there any reps from Microsoft on this forum who can provide any updates on if they're seeing these issues across the entire release? If they want Power Apps to be a production capable solution in the long term these problems can't happen. 

[WarrenBelz]

Has anyone lodged a support ticket and referred to this post? I cannot as my particular issue is solved for now.