Shopify app deploy fails with INTERNAL_SERVER_ERROR during app version creation

GraphQL Admin API Troubleshooting
1

I have reproduced the issue on the latest CLI version.

Yes, I am on the latest version

I have searched existing posts and this report is not a duplicate.

Yes, this isn’t a duplicate

In which of these areas are you experiencing a problem?

Function

Expected behavior

When running shopify app deploy --force, the deployment should complete successfully after:

  1. Building all extensions (Rust functions + UI extensions)
  2. Validating WASM files
  3. Uploading assets
  4. Creating/releasing the new app version

The app version should be created and available for use in the dev store.

Actual behavior

he deployment fails consistently during the “Releasing/Creating an app version” stage with an INTERNAL_SERVER_ERROR from the App Management GraphQL API.

All previous stages complete successfully:
I can Building extensions
Validating WASM files - OK
Uploading assets - OK
Creating/Releasing app version (fails here with error code: INTERNAL_SERVER_ERROR) - Fail

The error has occurred consistently across 4+ deployment attempts over 2+ hours, suggesting a backend API issue rather than a transient problem.

App Client ID: ed7070ba7814007b632b78c488b67a49

Reproduction steps

  1. Create a Shopify app with the following structure:
    • 2 Rust function extensions (type: product_discounts, targeting wasm32-wasip1)
    • 1 UI extension (admin discount settings)
  2. Ensure all extensions build and validate successfully locally
  3. Run: shopify app deploy --force
  4. Observe that build, validation, and upload stages complete successfully
  5. Deployment fails during “Releasing an app version” with INTERNAL_SERVER_ERROR

Note: Issue also occurs with shopify app deploy --no-release --force

Verbose output

shopify app deploy --force

╭─ info ───────────────────────────────────────────────────────────────────────╮
│ │
│ Using shopify.app.promo-validator.toml for default values: │
│ │
│ • Org: Soak&Sleep Limited │
│ • App: promo-validator │
│ │
╰──────────────────────────────────────────────────────────────────────────────╯

Releasing a new app version as part of promo-validator

promo-code-validator-ui │ promo-code-validator-ui successfully built
promo-discount │ Finished release profile [optimized] target(s) in 0.08s
promo-code-validator-func │ Finished release profile [optimized] target(s) in 0.08s

Running validation …
[✓ Validation passes]

Releasing an app version …
[Progress animation runs for ~40 seconds]

╭─ error ──────────────────────────────────────────────────────────────────────╮
│ │
│ The App Management GraphQL API responded unsuccessfully with errors: │
│ │
│ [ │
│ { │
│ “message”: “Internal error. Looks like something went wrong on our │
│ end.”, │
│ “extensions”: { │
│ “code”: “INTERNAL_SERVER_ERROR” │
│ } │
│ } │
│ ] │
│ │
│ Request ID: 756b234a-3508-4da9-b292-aad571c99d34-1761727321 │
│ │
╰──────────────────────────────────────────────────────────────────────────────╯

Additional Request IDs from multiple failed attempts:

  • 144d1064-1234-4537-bf13-5bb024ab9042-1761725464
  • 525d72be-2927-4f96-8639-03301cdb1dcf-1761725542
  • 513ffa7c-dbeb-4a83-a8b9-d8f51270e7c0-1761727514
  • a95afa5a-5b62-41c1-904a-4d452d91f8b9-1761728198

Operating system

Windows 11

CLI version

@shopify/cli/3.86.1

Shell

PowerShell

Nodejs version

v22.21.0

What language and version are you using in your application?

  • Rust (for function extensions, targeting wasm32-wasip1) ; JavaScript/Node.js v22.21.0 (for UI extensions) ; Cargo (Rust package manager) for building WASM modules
2

Hey @Alex_Law - thanks for sharing all of this info. I was able to pull some internal logs with the request IDs you shared, looking into this now. I’ll loop back with you once I have more info to share.

4

Hey @Alex_Law - would you be open to sharing your app.toml and extension toml files? I was able to work with some folks and we’re wondering if the issue is related to config. Let me know if you’d rather share those over a DM privately and I can set one up - hope to speak soon!

5

Hey @Alex_Law - just looping back on this. I was able to do a bit more digging and can confirm that this happens when there’s a corrupt target value in [[extensions.targeting]] (doc reference here).

We are working on a fix for this (can’t guarantee the turnaround time), but did just want to confirm this is on our radar. Passing a valid value should work though. Let me know if we can assist further on this.

6

I also have this issue

[
{
“message”: “Internal error. Looks like something went wrong on our end.”,
“extensions”: {
“code”: “INTERNAL_SERVER_ERROR”
}
}
]

Request ID: 1ca045e6-cbde-47a6-893f-90e23b4f544d-1762553782

I’m not sure how to proceed as i don’t have visibility of the issue