Skip to content

Navigation Menu

Explore
By company size
By use case
By industry
View all solutions
Topics
- AI
- DevOps
- Security
- Software Development
- View all
Explore
- GitHub Sponsors
  Fund open source developers
- The ReadME Project
  GitHub community articles
Repositories
- Enterprise platform
  AI-powered developer platform
Available add-ons
Pricing

Search code, repositories, users, issues, pull requests...

Search

Clear

Search syntax tips

Provide feedback

We read every piece of feedback, and take your input very seriously.

Include my email address so I can be contacted

Saved searches

Use saved searches to filter your results more quickly

Name

Query

To see all available qualifiers, see our documentation.

You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session. You switched accounts on another tab or window. Reload to refresh your session.

Dismiss alert

aws-amplify / amplify-backend Public

Notifications You must be signed in to change notification settings
Fork 74
Star 202

Code
Issues 185
Pull requests 32
Actions
Projects
Security
Insights

Additional navigation options

Code
Issues
Pull requests
Actions
Projects
Security
Insights

Add error mapping for Amplify app not found in specified region#2313

Open

vigy02 wants to merge 15 commits intoaws-amplify:mainaws-amplify/amplify-backend:mainfrom vigy02:fix/AppNotFoundvigy02/amplify-backend:fix/AppNotFoundCopy head branch name to clipboard

+188-32

Conversation Commits15 (15)Checks Files changed

Commits

Commits on Dec 9, 2024

Added error mapping for app name not found fault
vigy02
committed
Updated the test case for this fault
vigy02
committed
Updated the mapper and the test case to catch the AppNotFound Error
vigy02
committed

Commits on Dec 10, 2024

Updated the code to catch the error app name not available in the region
vigy02
committed
Merge branch 'aws-amplify:main' into fix/AppNotFound
vigy02
authored
Updated backend identifier resolver
vigy02
committed
Updated to handle the No apps found error
vigy02
committed
Updated generate-graphql command as well to catch the error
vigy02
committed
reset the backend resolver
vigy02
committed

Commits on Dec 13, 2024

Updated the error code and added test cases to test the error handling
vigy02
committed
chore: Updated the API
vigy02
committed
chore: updated API
vigy02
committed
Updated error handling to show the full error details
vigy02
committed
added the unit test cases to the existing test suite
vigy02
committed
fixed lint errors
vigy02
committed

Footer

© 2025 GitHub, Inc.

Footer navigation

Terms
Privacy
Security
Status
Docs
Contact

You can’t perform that action at this time.