Answered

Some users getting authentication token errors

(1) Share

Report

Posted on by dpana

I have built a canvas app that connects to a couple of different office 365 products - sharepoint, groups, etc. Most people are using the app just fine. A couple of users have reported an odd error, though. When they load the app, they get the following error:

Office365Groups.ListGroupMembers failed: {"error": {"code": "InvalidAuthenticationToken", "message":"Access token is empty.", "innerError": {"request-id":"{guid}", "date":"{date}"}}}

This error occurred the first time they loaded the app and hasn't resolved yet. Can somebody please help me understand what is going on here? I'm unable to find anything useful by googling the error message.

Categories:

Building Power Apps

I have the same question (0)

All responses (6)

Answers (1)

poweractivate 11,078 Most Valuable Professional on at

Like (0)

Report
@dpana

Try having the users that are getting this error to go to make.powerapps.com -> Data -> Connections -> Find the O365 or relevant Connection -> Press Ellipses -> From Dropdown, select "Delete" to delete the connection. Then relaunch the app. They should be prompted for the permission to allow again as if they are first time users of the app - maybe this could help.
Try having the users that are getting this error to attempt from another browser, other than the one tried at first (Edge, Firefox, Chrome etc.) and have user clear all cache and cookies as well and retry, perhaps in combination with #1 as well (i.e. try this and then #1).
Try remove data source, save and publish the app, then re-add data source and then again re-save then re-publish the app, then after that, have users try #2, then #1, and see if it helps.
Try to have the users attempt from different device that was not used before, especially a device using the PowerApps app if possible. If they have mobile device not used before, try to have them use that - and if possible, using the PowerApps App (although the Chrome mobile browser may be fine too). Also, if they have mobile device and did not try it there, ask them to download PowerApps app from app store then sign in through there - do they still get the error through there?
If any of the above did not help, you can try opening ticket from https://admin.powerplatform.microsoft.com/ to get help from Microsoft on this.

Was this reply helpful? Yes No
v-xida-msft on at

Like (0)

Report

Hi @dpana ,

Do these users have created a proper connection to Office 365 Groups connector when they load the app first time?

Do these users have proper Office 365 license to access Office 365 Groups connector?

Please consider ask your end users (who have this issue) re-create a new connection to Office 365 Groups connector with their proper credentials when they run your app, then check if the issue is solved.

In addition, also please consider turn on the "Formula-level error management" option within Advanced settings of App settings of your app, then re-publish your app, then check if the issue is solved.

Best regards,

Was this reply helpful? Yes No
Verified answer

dpana 95 on at

Like (2)

Report

The affected user was able to log in using a different browser, so the immediate issue is resolved.

To be frank, I'm incredibly frustrated with the app publishing experience. It seems ridiculous to me that every single end user of an app that I make has to make their own Office 365 connector, when the entire point of an app is to do things in the background on their behalf. Other than the people in the IT department who are making and maintaining these apps, none of the other users even know that the make.powerapps.com website exists, and would need specific instruction on how to remove and recreate a connection. This isn't a sustainable method of fixing problems.

Is there a way to allow all connections to certain backend tools to go through a shared service account?

Was this reply helpful? Yes No
poweractivate 11,078 Most Valuable Professional on at

Like (0)

Report

@dpana

The Power Platform is very powerful and is enabling you to things with low to no custom code that otherwise may need a lot of it - that includes for integrating the services with the Connector.

Recreating a connection is a workaround and small price to pay, and usually it should not be needed to recreate the connector.

First, we recommend Chrome - also if the Chrome version is older than 78, there is more likely to be problems because some features need the newest version of Chrome, especially in the editor.

Second, if there are imperfections, Microsoft may be working on ironing them out so that even this small price to pay doesn't exist anymore - currently it does not often exist and it could be due to some system configuration difference - we encounter this as well regularly but we prefer to use the Microsoft platforms over potential others that may have even much more errors, much higher price, and much more work to maintain.

We do concur with your thinking that it would be nice if there could be zero work of any kind, and perhaps Microsoft Power Platform and other Microsoft products are already the closest and getting closer by the minute.

Was this reply helpful? Yes No
Ihabkhiri1 26 on at

Like (0)

Report

I have a question about. I was having the same issue, invalid a token. After a while I figured out that it was due to expired Portal invitation redemption email. It would easy/user friendly if that error would be actually mentioning what is going on. Does anyone know if there is a way to change the message in the pop up?

Was this reply helpful? Yes No
geraldversluis 4 on at

Like (1)

Report

"Recreating a connection is a workaround and small price to pay" Sorry, but that is total and utter b***s***. It goes against every single use case for the Power Platform anyone can think of.

Was this reply helpful? Yes No