PowerApps – Could not resolve jwt token. Could not resolve issuer token

Today I had decided to start a new blog series centred around Microsoft PowerApps.   I decided I wanted to build out a quick little training request app on a SharePoint list.  While starting out I ran into a bit of a snag while creating the first part of the PowerApp.  But I will summarise how things occurred.  I created the metadata I wanted to have in my list.  The list contained about 9 different fields including a User\Group field and a couple of look-ups.  When I attempted to create a Power App directly from the list I received the following error:

“Invalid JWT token. Could not resolve issuer token.”

The full error was:

 

{
  "status": 401,
  "message": "{\"error_description\":\"Invalid JWT token. Could not resolve issuer token.\"}\r\nclientRequestId: 40b4d09c-ecaf-f6b3-a769-d06ca9f93ab5",
  "source": "https://drevsponline.sharepoint.com/pwrapp/_api/SP.APIHubConnector.GetTableMetadata(listName='e9607768-a4f9-457d-92a6-b5839319048c')",
  "errors": []
}
Stack: Core.ApplicationError: {
  "status": 401,
  "message": "{\"error_description\":\"Invalid JWT token. Could not resolve issuer token.\"}\r\nclientRequestId: 40b4d09c-ecaf-f6b3-a769-d06ca9f93ab5",
  "source": "https://drevsponline.sharepoint.com/pwrapp/_api/SP.APIHubConnector.GetTableMetadata(listName='e9607768-a4f9-457d-92a6-b5839319048c')",
  "errors": []
}
    at ServiceError.ErrorBase [as constructor] (https://paaeuscdn.azureedge.net/v2.0.661.0/studio/js/Core.js?v=39e032536722:34:36)
    at ServiceError.ApplicationError [as constructor] (https://paaeuscdn.azureedge.net/v2.0.661.0/studio/js/Core.js?v=39e032536722:51:31)
    at new ServiceError (https://paaeuscdn.azureedge.net/v2.0.661.0/studio/js/Core.Services.js?v=39e032536722:3118:40)
    at Function.ServiceError.createServiceError (https://paaeuscdn.azureedge.net/v2.0.661.0/studio/js/Core.Services.js?v=39e032536722:3145:76)
    at https://paaeuscdn.azureedge.net/v2.0.661.0/studio/js/AppMagic.Runtime.Client.js?v=39e032536722:910:74
    at Object.q [as _notify] (https://paaeuscdn.azureedge.net/v2.0.661.0/studio/openSource/modified/winjs/js/base.js?v=39e032536722:3:6021)
    at Object.enter (https://paaeuscdn.azureedge.net/v2.0.661.0/studio/openSource/modified/winjs/js/base.js?v=39e032536722:3:9526)
    at c.Class.derive._creator._run (https://paaeuscdn.azureedge.net/v2.0.661.0/studio/openSource/modified/winjs/js/base.js?v=39e032536722:3:10847)
    at c.Class.derive._creator._chainedError (https://paaeuscdn.azureedge.net/v2.0.661.0/studio/openSource/modified/winjs/js/base.js?v=39e032536722:3:10206)
    at c (https://paaeuscdn.azureedge.net/v2.0.661.0/studio/openSource/modified/winjs/js/base.js?v=39e032536722:3:8029)

Session ID: e1bc3838-3ed9-cc57-8d8a-741a7720fbec

Going back to the list didn’t help any.  Even though I didn’t have a PowerApp created, the list thought it existed.

Clicking “Remove this view” removes the PowerApp view from the list and doesn’t harm the metadata.

I thought at first I had a badly configured field, but nothing seemed out of place.  All of the fields were populating data as expected and the data saved successfully with the list forms.  Reviewing the error a bit closer it looked a lot like an access issue.  Problem is this is my tenant and currently I have only 3 accounts.  The one I was using was the global admin, so it shouldn’t have been that.

I then took a look at my PowerApps Admin console and noticed an exclamation point on the Connections menu.  Clicking on it, the newly created connection indicated the password needed to be updated.

Clicking on the “Update Password” option opens a dialog to the Microsoft portal.  I was then able to update my portal.  Next time I attempted to create my app it worked like a charm. I’ll talk about that next week. Hope this helps someone with a similar issue.

Thanks for reading!