bug report: AppStudioPlugin.iIr

[towhidmds]

Unable to make API call to Developer Portal: API failed, BadRequest, API name: update-published-app, X-Correlation-ID: 2cbbe076-6f01-4b8c-bb13-ac3cd7cdd150. Status code: 200. This may be due to a temporary service error. Try again after a few minutes. data: {"resultType":0,"result":null,"errorMessage":"BadRequest"}

stack:
iIr: Unable to make API call to Developer Portal: API failed, BadRequest, API name: update-published-app, X-Correlation-ID: 2cbbe076-6f01-4b8c-bb13-ac3cd7cdd150. Status code: 200. This may be due to a temporary service error. Try again after a few minutes. data: {"resultType":0,"result":null,"errorMessage":"BadRequest"}
at ux.wrapException (<REDACTED: user-file-path>/extension.js:213:49353)
at ux.publishTeamsAppUpdate (<REDACTED: user-file-path>/extension.js:213:38075)
at process.processTicksAndRejections (node:internal/process/task_queues:105:5)
at async ux. (<REDACTED: user-file-path>/extension.js:14:721527)
at async Mir.publish (<REDACTED: user-file-path>/extension.js:971:442089)
at async Mir. (<REDACTED: user-file-path>/extension.js:711:26184)
at async Mir.execute (<REDACTED: user-file-path>/extension.js:971:440369)
at async e.executeImpl (<REDACTED: user-file-path>/extension.js:745:4903)
at async e.execute (<REDACTED: user-file-path>/extension.js:745:2625)
at async Jue.publish (<REDACTED: user-file-path>/extension.js:916:18679)
at async Jue. (<REDACTED: user-file-path>/extension.js:14:721527)
at async yd.publishApplication (<REDACTED: user-file-path>/extension.js:1034:29504)
at async yd.Gku (<REDACTED: user-file-path>/extension.js:997:27092)
at async yd.cOu (<REDACTED: user-file-path>/extension.js:997:31383)
at async yd.oOu (<REDACTED: user-file-path>/extension.js:997:30432)
at async Hku (<REDACTED: user-file-path>/extension.js:997:27064)
at async yd. (<REDACTED: user-file-path>/extension.js:997:26229)
at async yd.oRu (<REDACTED: user-file-path>/extension.js:1032:6512)
at async yd.lOu (<REDACTED: user-file-path>/extension.js:997:31682)
at async yd. (<REDACTED: user-file-path>/extension.js:14:721527)
at async k_ (<REDACTED: user-file-path>/extension.js:2607:24779)
at async Object.Fos [as callback] (<REDACTED: user-file-path>/extension.js:2651:1126)
at async e.runCommand (<REDACTED: user-file-path>/extension.js:2607:21447)
at async cA.h (file:///c:/Users/N.Towhid.MIDISGLOBAL/AppData/Local/Programs/Microsoft VS Code/resources/app/out/vs/workbench/api/node/extensionHostProcess.js:116:41740)
at async cA.h (file:///c:/Users/N.Towhid.MIDISGLOBAL/AppData/Local/Programs/Microsoft VS Code/resources/app/out/vs/workbench/api/node/extensionHostProcess.js:116:41740)

[m365-agent-toolkit-assistant]

👋 Hi @towhidmds,

Thank you for reporting this issue! We want to let you know that:

⏱️ Our team will personally review your issue
🎯 You can expect a response within 2 business days

✨ This is an AI-generated initial response
🤖 AI-Generated Preliminary Analysis:

This is a known issue when publishing or updating a Teams app via the toolkit:
The "API failed, BadRequest, API name: update-published-app..." error is often temporary, but can also be caused by validation problems in your app package.

Actionable Steps:

1. Wait and Retry: The backend may be temporarily unavailable—try again after a few minutes.
2. Check Your Manifest:
   • In staticTabs.context, only use personalTab or channelTab.
     (Other values are unsupported and cause BadRequest.)
   • See the GitHub solution.
3. Validate your app package: Use the App Package Validator.
4. Check Length of instructions.txt: If present, make sure it's under 8,000 characters (see fix).
5. If none help, follow/track this GitHub issue for updates.

If problem persists after verifying the above, share your manifest and package in the issue tracker for deeper help.

✨We'd love your feedback! Please take a moment to fill out our survey.

---

Note: This is an automated first response generated by AI. A human team member will review your issue and provide a more detailed response soon. We appreciate your patience!

[github-actions]

Based on the status code and API name in error message, this issue is duplicated with #14690. You can refer to it for more information.