Google Workspace Marketplace SDK "Something went wrong" on App Configuration and Store Listing despite required IAM role

Google Cloud Cloud Foundations & Onboarding
1

I’m trying to publish a Google Sheets Editor add-on, but the Google Workspace Marketplace SDK pages in Cloud Console fail to load.

Project details:

  • GCP project: (PII Removed by Staff)
    • Account used in console: (PII Removed by Staff)
  • Issue:
  • Both of these pages show a generic “Something went wrong.” error and do not load:
    • App Configuration (googleapps_sdk)
      • Store Listing (googleapps_sdk_publish)
    • What I already did:
      1. Assigned IAM role roles/appmetadata.workspaceMarketplaceAppConfigurationAdmin to (PII Removed by Staff) (policy update succeeded).
        1. Confirmed I am using a standard GCP project linked from Apps Script (not the default Apps Script project).
          1. Enabled and configured the Google Workspace Marketplace SDK.
        3. Representative request IDs shown with the errors:
          • 510657321459852004
            • 12910267875819947012
              • 1099228782285252251
                • 16365367402726092826
              • Question:
              • Is there another required IAM role/API/org policy, or a known backend issue, that causes Marketplace SDK App Configuration / Store Listing pages to fail with this generic error?
2

Update (2026-03-02): additional troubleshooting done with all personal details redacted.

  • Reproduced the same issue across two different projects, including a newly enabled test project.
    • In both projects: appsmarket-component.googleapis.com enabled, billing linked, and role roles/appmetadata.workspaceMarketplaceAppConfigurationAdmin assigned.
      • googleapps_sdk and googleapps_sdk_publish still fail with generic “Something went wrong”.
    • Additional request IDs from latest repro:
      • 12001222324313172320
        • 12152636278773189759
      • Given this reproduces cross-project with required IAM role present, this looks like a backend/entitlement issue rather than project config. Could a Googler please escalate/check backend logs for these request IDs?
3

bump