App crashes in run-mode, works fine in design mode

(0) Share

Report

Posted on by R3dKap

1,594

Hi @Mr-Dang-MSFT,

As suggested, here is a thread about the issue I am facing at the moment on my application which has several screens and several custom components. When I navigate from one screen to another, the destination screen does not render in run-mode (works fine in design-mode).

The only thing that I can think of is that all components that work fine were created prior to PowerApps core version 3.19043.16 which was pushed on 23d of April. Components created after from the 24th of April (with version 3.19043.16) make my screen crash.

Since my application is a bit complex, would it be possible that you contact me through a private message so you could have a look at it through a Teams screen share ? This problem might hide an important issue related to version 3.19043.16.

Thanks for you help,

Emmanuel

Categories:

Building Power Apps

All responses (4)

Answers (1)

Sort by

Verified answer

R3dKap 1,594 on at

Like
a
(1)

Report
Copy link

Link copied!
Ok, solved my problem...
What I was doing:
created many components which returned each a action code (like a MainMenu which would return the selected menu item)
linked those components to combo boxes so that on the OnChange event I would do the necessary actions (like navigate to another screen)
complex system to "reset" the component so it can trigger the combo box OnChange event everytime it's clicked (like a Confirmation dialog box)
Didn't work because combo box OnChange events are triggered everytime you change screen (seems like a mess).
Solution:
replace all combo boxes with toggles
used a output property on each component to trigger the toggles
put the code in the OnCheck event of the toggles
Emmanuel
yfw Microsoft Employee on at

Like
a
(0)

Report
Copy link

Link copied!

Hi, OnReset of component is something we are looking forward to ship next. Toggle hack would be a work-around for now. Thanks for sharing your issue and workaround with us! Looking forward to ship reset property sooner!
R3dKap 1,594 on at

Like
a
(0)

Report
Copy link

Link copied!

Hi @yfw,
Thanks for sharing this with us... Indeed, an OnReset event would be much appreciated.
Furthermore, I would say that adding real events management to components would just change radically the way we use them. May be if we could have a new type of component property called "Event" which could be triggered through a "Trigger(<event>)" function would be really great.
For instance, if we put buttons or toggles or combo boxes in components, in their respective event we could use the Trigger() function to propagate the event of the control to the component's custom events...
Is this something planned in the future of PowerApps ?
Emmanuel
yfw Microsoft Employee on at

Like
a
(0)

Report
Copy link

Link copied!

OnReset will requires a trigger of reseting the component. To make it more native, my exploration is similar to your suggestion. With OnReset, I can also define a default input property (maybe choosing one of the custom property to be the default). OnReset triggers if the default input property value changes, which is similar to how default value and OnChange work of the toggle button. How will this option fullfill your scenario? Thanks for sharing your thought with us!