BUG: New apps on the Developer Portal generate ids that fail parsing

Since you can save manifest changes but consistently fail on Update in the App Package Editor, this points to a pre-update parsing issue in that specific update path (likely service-side/tenant-scoped), not a generic GUID formatting mistake in your manifest authoring.

Recommended next steps:

1. Keep a minimal repro package (new app, single small manifest edit, then Update) and share it with Support.
2. Capture diagnostics from browser DevTools during the failed Update (request URL, status, response body, correlation/request IDs, UTC timestamp).
3. Open a support ticket and include tenant ID, app ID, exact edit made, and the exported before/after manifest.
4. As a temporary workaround, avoid Portal “Update” for this app and publish via external package workflow (Teams Toolkit/CLI/App manifest package) until engineering confirms a fix.

Given your latest repro, this should be treated as a product issue in the Developer Portal update pipeline unless Support finds a tenant-specific policy issue.

Hi @Scott Josephson

Thank you for reaching out. 

I attempted to reproduce the issue by creating a brand-new app in the Teams Developer Portal and running App Validation. In my testing, the validation process completed successfully and reported only metadata-related issues ( such as invalid or unreachable Website URL, Privacy URL, Terms of Use URL, and description content warnings).  

However, I was unable to reproduce the error reported in your environment: "The manifest product ID could not be parsed. The ID must be a plain GUID". As far as I know, this error may occur before App Validation begins, during the manifest pre-validation stage.

For troubleshooting step, you could try creating a brand-new app directly in Teams Developer Portal and populating all required manifest properties before running validation, please verify that the app is validated before importing or copying content from an existing manifest. If possible, export the current app package and compare it with a newly generated app package to identify any differences in the manifest structure. 

If a newly created app validates successfully while the affected app continues to show the Product ID error, this may indicate that the issue is related to to the specific app package, manifest content, tenant environment, or a service-side condition, rather than being a general issue affecting all newly created apps. 

Please note that these findings are based on my own testing and may not fully explain the behavior you're experiencing. To investigate further, engagement from Microsoft's support team will be required. A Support Engineer can conduct a remote troubleshooting session, review backend configurations, and run any necessary synchronization or diagnostic tools. If needed, they can also escalate the case to the appropriate engineering team for deeper analysis. 

You can report this issue by following steps: Team developer portal > Feedback icon > Report a problem 

Apologies for referring you to the development support team. As community moderator, I do not have access to your specific tenant configuration or the internal backend tools required to verify and diagnose issues at that level. As a result, the guidance I provide is based on publicly available Microsoft documentation, product behavior, and community resources. 

If you have any additional concerns, feel free to comment below. I would be more than happy to assist.       

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.