Answered

Navigate function suddenly stop working when publish new version

(2) Share

Report

Posted on by NhanVo

Hi everyone,

I had an app that work fine till April 15, 2025. Edit mode and Play mode are perfectly run and no problem. The environment is DEV and that app is in a solution package.

Until April 16, I went to Edit mode and change some minor code and published. When opened app in Play mode, Navigate() function on onStart not fired but the other codes in there still fine. I tried turn off "onStart navigate" feature and move to StartScreen.

I only enter a screen name to StartScreen ('Home Screen') but its still not working, and the app auto render the first screen in Edit Mode. So I moved 'Home Screen' to first and published again. App loading and say: "This app stopped working. try refreshing your browser". Well I tried open it in incognito mode and different browers but no luck.

I tried restore last 2-3 previous version and test published, all encountered the same error. Other apps in DEV environment still work fine when publish new version.

Last effort, I download the working version and create new app with it, published again without changing any code or setting, got the same error.

I wonder if this is temporary Server-side Microsoft or something broken in app. Does anyone get the same error? Hope I can get some answer. Thank you all!

Categories:

Building Power Apps

I have the same question (0)

All responses (6)

Answers (1)

Suggested answer

AmínAA 1,228 Moderator on at

Like (0)

Report
Copy link

Link copied!

Greetings @NhanVo!

Instead of using the "Navigate()" function, on the "OnStart" parameter from the app, you might want to use the "StartScreen" parameter, as the Navigate on the OnStart function is "deprecated".

You might still be able to use it, if you go into your app's configuration, and enable that function, although you would do good in using the "StartScreen" property instead.

If you like my response, please give it a Thumbs Up. Should this reply solve your question, please mark your post as Solved. Otherwise, feel free to reply to my answer for further help.
Connect with me if you feel like it!

Was this reply helpful? Yes No
NhanVo 11 on at

Like (0)

Report
Copy link

Link copied!

Thanks for commenting @AmínAA !
As I write in the post, I have tried to turn off onStart and move code to StartScreen, but it didn't work.
The app automatically render the first screen, not the screen I put in StartScreen (even though I only put 'Home Screen' in it, no logic or whatsoever).

Was this reply helpful? Yes No
AmínAA 1,228 Moderator on at

Like (0)

Report
Copy link

Link copied!

Hi there @NhanVo!

Have you edited your original post by any chance? I've got a notification on the post, but I don't see any reply, so I was wondering if you changed anything on the original question... In any way, if you've either already tried enabling the "Navigate" function on the "OnStart" property, and it doesn't work, and you changed that to the "StartScreen" property but still doesn't work, either as you said it might be a temporary server-side thing, or something in your solution must've gone really wrong...

If you want, I would be down to go into a call, to see exactly what is happening, so that we might figure out what is wrong, and how to fix it. And afterwards, I could just reply what was happening, so that you might mark it as an answer for others to know how you solved it.

If you like my response, please give it a Thumbs Up. Should this reply solve your question, please mark your post as Solved. Otherwise, feel free to reply to my answer for further help.
Connect with me if you feel like it!

Was this reply helpful? Yes No
ronaldwalcott 3,862 Moderator on at

Like (0)

Report
Copy link

Link copied!

What change did you make?

Show the code you changed and the code in the App OnStart

What is the error being shown?

Was this reply helpful? Yes No
Verified answer

NhanVo 11 on at

Like (0)

Report
Copy link

Link copied!

Hi everyone, thanks for supporting me!

After more experiments and debugging, I found why the navigation wasn't working.

So the answer is, some screens were broken, and their IDs got messed up, so Navigate couldn't find them. I suspect this happened when I saved and published the app on April 16—possibly a PowerApps server glitch caused some screens to lose their identity.

You can test it by place one by one screen in StartScreen, publish it and checkout if in Play mode your app automatically navigate to that. If the app shows the first screen instead of the one you set, that screen is broken.

To resolve this, simply duplicate all error screens, delete the old ones and replace new screen name on your code. That will make it.

Was this reply helpful? Yes No
stampcoin 5,146 Super User 2026 Season 1 on at

Like (0)

Report
Copy link

Link copied!

I have this ' Problem' for long time, I thought it was removed in the update....since when pulish it, it works for me...

Was this reply helpful? Yes No