You’re offline. This is a read only version of the page.
iOS version = 14.6
iPhone model = 7
My team member and I have started using the "Buttons" functionality in the Power Automate app, which has been great. This past week, my Power Automate app started crashing immediately upon opening (<1 second). This error message (see below) quickly flashes and then the app crashes and brings me back to the home screen. My other team member doesn't have any problems opening their app, so I don't think it's a corporate policy change (ex: app being blocked).
The only thing I can think that changed is my corporate/Microsoft password on Monday (same day this started). However, I don't know how to be prompted to put in my new password before the app crashes. I've deleted the app entirely from my phone (hoping that would wipe the login data), but re-installing/launching the app results in the same behavior.
Any advice on how to fix this? Thank you!
Hello,
for me is working fine like this:
Same problem here. One account on my authenticator. Anyone fix this?
Following up to my own post on this workaround, I managed to figure out the root cause. The "Microsoft Authenticator" app on my iPhone had two different Microsoft accounts associated to it. I believe when Power Automate app launched, it was getting confused on which MS account to log in as and then crashed. I think I first tried "reseting" my entire iPhone and then removed the unneeded MS account from Microsoft Authenticator for Power Automate to start working again. I could not tell you confidently that the iPhone "reset" was a necessary step though. I'd first check if you have multiple accounts in your Microsoft Authenticator app and remove one of them.
Yes, I post the comment of Jim that worked for me:
My device was unregistered to the MDM policy of my ex-employer. But there was one day I deleted an entry on MS Authenticator, this issue happened ....
I believe this is a bug.
I am using the same way. It's a workaround, not a fix. Team MS, please get it fixed.
I managed a workaround for this, but not able to resolve the root issue:
At a glance, this seems like an app bug, but any additional thoughts would be helpful (or recommendations to properly report it as a bug).
#1
WarrenBelz
146,645
Most Valuable Professional
#2
RandyHayes
76,287
Super User 2024 Season 1
#3
Pstork1
65,997
Most Valuable Professional
Share
Report
All responses (
Answers (
