The `amplify-category-xr` package, currently at version `3.4.4` as per the provided metadata, extends the AWS Amplify Command Line Interface (CLI) to allow developers to provision and manage cloud resources for Extended Reality (XR) applications. This typically included services for AR/VR/MR capabilities within Amplify-powered backends. As part of the broader AWS Amplify CLI monorepo, its release cadence historically aligned with frequent updates for bug fixes and minor features across the CLI. However, this plugin's core functionality is now deprecated as its underlying dependency, Amazon Sumerian, is no longer accepting new customers, and existing Sumerian scenes were slated to be unavailable after February 21, 2023. Therefore, while the CLI plugin exists, it no longer provisions functional resources. Its original key differentiator was abstracting complex AWS service configurations for XR, integrating with other Amplify categories like Auth and Storage.
npm install amplify-category-xrVerified import paths — ran on the pinned version, not inferred.
Demonstrates the CLI workflow for adding and deploying an XR resource, despite its functional deprecation.
Migrate away from Amplify XR features. AWS recommends exploring alternative solutions for AR/VR/MR applications, as Amplify no longer provides direct support for this category via Sumerian.
Always run `amplify push` after `amplify add`, `amplify update`, or `amplify remove` to synchronize your local backend definition with your AWS cloud resources.
Run `amplify configure` to set up or verify your AWS credentials and default region. Ensure the IAM user has appropriate permissions for all AWS services Amplify provisions.
Ensure `@aws-amplify/cli` is installed globally (`npm install -g @aws-amplify/cli`). If the issue persists, try reinstalling the CLI. Note that even if the command is found, it's deprecated.
Update the IAM policy attached to the AWS user configured with Amplify CLI to include permissions for Amazon Sumerian and any other related services (e.g., S3 for asset storage). However, consider the service's deprecation before investing in permission setup.
Verify that `amplify push` was run successfully. Given the deprecation of Amazon Sumerian, this error is now the expected behavior for any XR resource.