Failed to publish app

[Sang10]

I can update the app when I am re-publishing exsisting reports within the app, however when I try to add new content to the app I keep getting this error message, no detail, just this - any ideas what could be the issue?

[Shahid12523]

You can update existing reports, but adding new ones fails likely due to:
- Missing dataset permissions for app viewers
- Unassigned content in audience groups
- Broken visuals or ghosted metadata in the new report
- Unsupported content types or workspace limitations
- UI bugs or preview features causing silent failures
✅ Try adding one item at a time, check dataset access, and ensure the new report is assigned to an audience.

[Sang10]

The dataset being used for the report is one that is currently being used for numerous reports in the app. The report audience is set for the whole organisation, the only time access is restricted is for data sensitive reports. I am admin for the app and workspaces so unsure as to why I can't pubish new content.

[v-priyankata]

Hi @Sang10 

Thank you for reaching out to the Microsoft Fabric Forum Community.

@FarhanJeelani @Shahid12523 Thanks for the inputs. 

@Sang10  - As you mentioned, all permissions are set correctly and you are the admin. Could you please try a few more steps, as they might help you?

1. Even if the dataset is looks fine, the new report might have hidden references like renamed fields, deleted visuals, unused datasets. please try duplicating the report in Desktop and republish as a fresh report & add that to the app.

2. Sometimes unsupported items inside the report like some visuals, preview custom visuals, scorecards, DataMart's can break app publishing even if they work fine in the workspace. please check all the things.

If I misunderstand your needs or you still have problems on it, please feel free to let us know.  

Thanks.

[v-priyankata]

Hi @Sang10 

Thank you for reaching out to the Microsoft Fabric Forum Community.

I hope the information provided by users was helpful. If you still have questions, please don't hesitate to reach out to the community.

[v-priyankata · Accepted solution]

Hi @Sang10 

I wanted to check if you had the opportunity to review the information provided. Please feel free to contact us if you have any further questions.

[FarhanJeelani]

Hi @Sang10 ,

This is a common and frustrating issue, especially when the error message is vague. The generic "Failed to publish app" error is often a catch-all for a variety of underlying problems.

Most likely causes and their solutions, starting with the most common.

1. Data Source Permissions (The Most Likely Culprit)
Since the error occurs when you add new content, the issue is almost certainly with the data source for that new content.

The Problem: The new dataset or report you are trying to add has different permissions or is located in a different workspace than the original content in your app. The app's end users might not have permission to access this new data.
The Solution:
Go to your Power BI Service online.
For the new report you are trying to add, check its dataset settings.
Navigate to Settings > Datasets + dataflows.
Select the dataset for your new report.
Go to Permissions. Ensure that the security groups or individuals who need to use the app have at least Read permissions for this specific dataset. They must have access to both the app and every underlying dataset within it.

2. App Content List Configuration
Sometimes the app itself hasn't correctly registered the new content.

The Problem: The new report was added to the workspace but not properly selected for inclusion in the app.
The Solution:
In the Power BI Service, go to your Workspace.
Click on Update app (the same button you use to publish).
Go to the Content tab in the setup window.
Carefully review the list. Ensure the checkbox next to your new report is selected. Also, verify that any existing reports you still want are also checked. It's easy to accidentally deselect something.

3. Broken Data Sources or Refresh Credentials
If the new content has a live connection or Imported data, its credentials might be invalid.

The Problem: The dataset for the new report can't connect to its source (e.g., a SQL database, SharePoint list), or the credentials stored for the gateway have expired.
The Solution:
In the Workspace, find the dataset for your new report.
Click on the schedule refresh icon or go to Settings for that dataset.
Check the Data source credentials. Make sure they are valid and have not expired. You may need to re-enter a password.
If using an On-premises Data Gateway, ensure the gateway is online and running.

4. Naming or Metadata Conflicts
This is rarer but can happen.

The Problem: The new content has a name, parameter, or metadata property that conflicts with existing content in the app.
The Solution: Try publishing the app with only the new content selected (temporarily deselecting the old reports) to see if it works. If it does, the conflict is between the old and new items. You may need to rename the new report or its underlying dataset.

Please mark this post as solution if it helps you. Appreciate Kudos.