Unanswered

“This app isn't working. Refresh your browser or try again later.”

(0) Share

Report

Posted on by kanderson2

I am having an issue in Power Apps where literally only one user is having this error appear when trying to log in to an app.

For this user it does not matter which computer they use, the same error appears. Other users are able to log in to the same computer and use the app without issues. Using a different browser likewise makes no difference.

The only abnormal thing I have been able to find is that under the connections for an app, the Office 365 Outlook connection does not seem to be appearing under the app as it should. It can be seen under the users' connections, but does not show as being used by the app itself.

I have looked around, but cannot find any issues dealing with a connection not appearing for one specific user within an app. I have no idea what would have lead to this situation.

We have tried clearing the cache, deleting connections, removing and re-adding the user, trying past versions of the app, nothing seems to be working. Would like to emphasize that this only affects one out of a dozen users, everyone else is able to use the app with zero problems.

Any advice on ways to resolve this issue would be greatly appreciated.

Session ID: 81bd7ff6-03ad-4a2c-9e2b-2a9670f1e215

Categories:

Building Power Apps

I have the same question (0)

All responses (6)

Answers (0)

WarrenBelz 153,051 Most Valuable Professional on at

Like (0)

Report

Hi @kanderson2 ,

I know this might be an obvious question, but have you checked the user's permissions on both the app and the data source?

Was this reply helpful? Yes No
kanderson2 6 on at

Like (0)

Report

Yes, have even tried removing them from permissions and re-adding them but this did not seem to make any difference.

The data sources are just office 365 outlook (which they are using to login in the first place), and a google sheet which shows as being connected correctly.

The only abnormal thing I have been able to find has been that when looking at the app connections for just that user, the 'office 365 outlook' connection does not even appear when looking at the app details. It could be seen looking at connections in general, but it shows no connection to the app. There is no prompt to authenticate or anything, it just asks for office 365 login and then gives the error mentioned in the title for this one user.

Was this reply helpful? Yes No
WarrenBelz 153,051 Most Valuable Professional on at

Like (0)

Report

Hi @kanderson2 ,

Now you have mentioned something different - Google Sheets - do they have proper access to that?

Was this reply helpful? Yes No
kanderson2 6 on at

Like (0)

Report

Thank you for the response @WarrenBelz Yes, that was the only thing showing up correctly in the connections. This typically requires a one-time login which was done ages ago. Everything for this user worked fine up until yesterday.

To provide a little more detail, we published a new version of the app, with only minor changes in one input field. Nothing related to any of the connections.

New version worked fine for all other users, but now this one user in particular gets the error message from the title. I even tried reverting back to a previous version that worked, but still the same issues. It almost seems like somehow either this user managed to delete the office 365 connection to the app, but I have no idea how they would have even done this; they would only ever typically access the app through a direct link and did not go into any menus or settings that we are aware of.

I have seen other people post about this error in the past, but it seems like in those situations it was related to Microsoft outages in their area, which I wouldn't think to be the case here if only one user is being affected...

Was this reply helpful? Yes No
WarrenBelz 153,051 Most Valuable Professional on at

Like (0)

Report

Hi @kanderson2 ,

Sounds like a support call to Google - this is definitely a data source permissions issue.

Was this reply helpful? Yes No
kanderson2 6 on at

Like (0)

Report

@WarrenBelz For reference it turned out that this was a bug on Microsoft's side, they apparently fixed it last Thursday/Friday. Started working again without any changes being made.

Was this reply helpful? Yes No