Power App for Teams Publishing Issue

(0) Share

Report

Posted on by CU12021753-0

We are experiencing an issue across multiple Power Apps for Teams environments.

Within the last two weeks, all environments began returning HTTP 500 errors when attempting to:

Publish new apps to Microsoft Teams
Publish updates to existing apps

This issue is occurring across several Teams environments, including:

Environments that use SharePoint as the only data source
Environments that use Dataverse for Teams

In addition, when attempting to create a new Dataverse for Teams table, we receive an error (screenshot attached).

We have verified the following:

Dataverse for Teams capacity is well within the 2GB limit
The issue is not isolated to a single environment
The issue occurs for multiple users

A support ticket has been opened with Microsoft, but we are posting here to determine whether others are experiencing similar behavior or are aware of any recent platform changes that could be causing this.

Any insight would be appreciated.

Categories:

Building Power Apps

Microsoft Dataverse with Power Apps

I have the same question (0)

All responses (3)

Answers (1)

Sort by

Verified answer

JamzMo 9 on at

Like
a
(0)

Report
Copy link

Link copied!
Instead of publishing directly to the channel, share the app from within Power Apps for Teams:

Open Microsoft Teams

Open the Power Apps app (left rail)

Go to Build → find your app

Click the … (ellipsis) next to the app name

Click Add to Teams, add to teams again, Open and then choose the channel you want to publish the App to.

This worked for me following similar problems.

Was this reply helpful? Yes No
CU12021753-0 4 on at

Like
a
(0)

Report
Copy link

Link copied!

JamzMo - This worked. Thank you so much. I'm curious if you have any idea why the other way of publishing stopped working? I'm curious if it ever started working for you again?

Was this reply helpful? Yes No
JM-02031020-0 2 on at

Like
a
(0)

Report
Copy link

Link copied!

We are suffering from the same problem. In the meantime, the "Http 500" errors have turned into "Http 400".

The five steps above looked promising, but the last step only yields a popup labelled "Something didn't work" with no further information.

It also affects newly created Canvas Apps with no connectors. At the moment, we are unable to update _any_ app or publish new ones.

Was this reply helpful? Yes No