screen navigation not working on published app

[aortiz-arroyo]

Hello- I have an app with multiple screens for a wizard-like behavior.  Currently the app works just fine while editing and playing it.  However, once I publish the app, the first time around navigation works fine, but when accessing again screen navigation stops working in certain screens.  

OnSelect function for the first button that doesn't work is:

Set(
    _newShoutoutStep,
    _newShoutoutStep + 1
);
Patch(
    collShoutout,
    First(collShoutout),
    {Division: {Value: _selectedDivision.Title}}
);
Navigate(
    scrNewShoutoutContent,
    ScreenTransition.Cover
)

 Both the Set and Patch functions are working as I can validate the values in it, but the Navigate does not.  I have tried adding an icon and label to test the Navigate and even that does not work.

[v-xida-msft]

Hi @aortiz-arroyo ,

Do you mean that the Navigate function could not work within your published app?

Which browser do you use to run your published app? Or you use PowerApps Mobile App to run your app?

Based on the issue that you mentioned, I have made a test on my side, and and don't have the issue that you mentioned. Please check if the first argument value you typed within the Navigate() function is a valid screen object.

If you use web browsers to run your published app, please consider take a try to run it using other different browsers, then check if the issue is solved.

If you use PowerApps Mobile App to run your published app, please check the version of your PowerApps Mobile App has been upgrade to the latest version, if not, please consider upgrade it to the latest version, then try your app again, check if the issue is fixed.

Have you taken a try to create a new Blank app, and then try the Navigate function in your new published app? Check if the issue still exists.

If the issue still exists, please consider submit an assisted support ticket through the following link:

https://powerapps.microsoft.com/en-us/support/pro

Best regards,

[aortiz-arroyo]

Hi @v-xida-msft, I apologize for my late response.

The issue occurs in any browser and even the PowerApps mobile app, but only with the published app.  I did opened a ticket and have been working with the support team.  Yesterday we had a troubleshooting session with engineers and seems the issue is related to the code not getting the current page name, and therefore making the navigate fail. 

This is something that started perhaps couple of weeks ago, so we were also able to go identify a version that works.  Perhaps something changed on PowerApps side.

[Soum]

I have been also facing similar issues from last 2-3 weeks. Once I publish the App the navigation is not working, however if I run it from App Studio then everything works. 

if there is any update on the PowerApps Core functionality side, please do update. 

[aortiz-arroyo]

Hi- from our ticket with Microsoft- the root cause is an unhandled exception when using the 'Delay Load' preview feature and the app has components.  Until the bug is fixed the workaround is to disable 'delay load' feature, or remove components from the app.

[BaseCamp]

Hi, 

I had the same problem. 

Sometimes it worked with one user but didn't with another.

I fixed it by switching of all the Preview and experimental functions of powerapps and published the app again.

[AlexandreAlves]

Thanks, after change delay load it works. I was having same issue with two specific buttons. 

BR/Alexandre

[nlp_kapacity]

Does anyone else still experience this issue? I am currently working on an app with 3 screens, 2 collections, 1 Power Automate flow and a patch to a SharePoint-list. 

Now, moving from screen 1 --> 2 with records in both collections is not an issue. Initiating the Power Automate flow and moving from screen 2 --> 3 is not an issue either. Patching some info and navigating from screen 3 --> 1 is an issue. I've tried separating the patch and the navigation and it seems like the navigation specifically is the issue. I've disabled Delay Load (and multiple other features) with no effect. 

Any updates from Microsoft?

Any help is appreciated, thank you.

[Guillaume_G]

I know this is an old thread but I just encountered this issue: i.e. Navigate() function works when playing the app in Edit mode whereas it does not work in the published app.

I spoke to MS support who advised to turn off the 'Delayed Load' Settting.

I did this, saved, published the app and the issue was gone.

They told me that in some cases, when this setting is turned on, some unhandled exceptions are generated and these prevent the Navigate() function from working correctly in a published app.