[Bug] Unable to fully rename Vibe-generated apps more than once

[samuel-mitchell-omf]

Describe the bug

A Vibe-generated Power Apps Code App was successfully renamed from "Audit Tool" to "Internal Review Tool". A subsequent rename from "Internal Review Tool" to "ChangeIQ" updated the project metadata and application branding, but did not update the Power Apps runtime title.
The application now displays inconsistent names:

App UI displays ChangeIQ
Project metadata displays ChangeIQ
Browser tab displays Internal Review Tool
Power Apps runtime header displays Internal Review Tool

Investigation of the workspace shows:

project.json { "projectName": "ChangeIQ" }

but

power.config.json { "appDisplayName": "Internal Review Tool" }

Steps to Reproduce

1. Create a new Code App in Power Apps Vibe.
2. Give the app an initial name (for example, "Audit Tool").
3. Rename the app to a second name (for example, "Internal Review Tool").
4. Publish and verify that the runtime title updates correctly.
5. Rename the app again (for example, "ChangeIQ").
6. Publish the updated version.
7. Launch the app.

Expected behavior

All application metadata should be updated consistently.
The following should display the current application name:

• Power Apps runtime header
• Browser title
• Project metadata
• Application branding

In this case, all locations should be updated to ChangeIQ.

Actual behavior

Application branding and project metadata display ChangeIQ, but the Power Apps runtime title remains Internal Review Tool.
Examples:

Browser tab title shows: Internal Review Tool - Power Apps
Power Apps shell header shows: Power Apps | Internal Review Tool
Application UI shows: ChangeIQ

The application appears to contain inconsistent metadata after the second rename.

Screenshots or Error Messages

Environment information

• Framework, build tool or relevant package used: Vibe-generated Power Apps Code App (appears to use React/Vite internally)
• Any connection/components: Microsoft Dataverse, multiple custom tables, Power Apps Vibe (preview)

Additional context

The app is classified as a Code App in Power Apps.
Standard Power Apps editing capabilities are disabled.
The Vibe workspace indicates that:

power.config.json is platform-managed and protected from edits.
appDisplayName is treated as immutable.
Power Apps runtime titles are resolved from package/service metadata.
No self-service mechanism appears available to update appDisplayName after the package has been created.

As a result, there does not appear to be a supported way for a maker to reconcile the metadata inconsistency once it occurs.
Question: Is there a supported process to update the package metadata for an existing Code App, or is this a known bug in the Vibe rename workflow?

[eschavez]

Thank you for the detailed report! This is a confirmed bug in the rename workflow for Vibe-generated Code Apps. When an app is renamed more than once, power.config.json's appDisplayName is not updated to match the new name — so subsequent pushes send the stale name to the Power Apps runtime, leaving the browser tab and shell header stuck on the previous title.

We're working on a fix. In the meantime, as a workaround you can pass the correct name explicitly at push time using the --display-name flag once it ships:

pac code push --display-name "ChangeIQ"

This will override the stale value in power.config.json, send the correct name to the Power Apps API, and update the config file so future pushes also use the new name. We'll update this issue once the fix is available in a PAC CLI release.

[samuel-mitchell-omf]

The problem is that, since I'm using Vibe, I don't have access to the code directly via export or otherwise, so I cannot push the code using PAC.