Skip to content

fix(amplify-e2e-tests): handle InvalidClientTokenId in getAmplifyApps opt-in region cleanup #3512

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
svidgen merged 1 commit into from
Jul 9, 2026
Merged

fix(amplify-e2e-tests): handle InvalidClientTokenId in getAmplifyApps opt-in region cleanup #3512

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion packages/amplify-e2e-tests/src/cleanup-e2e-resources.ts
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -180,7 +180,7 @@ const getAmplifyApps = async (account: AWSAccountInfo, region: string): Promise<
try {
amplifyApps = await amplifyClient.send(new ListAppsCommand({ maxResults: 50 })); // keeping it to 50 as max supported is 50
} catch (e) {
if (e?.name === 'UnrecognizedClientException') {
if (e?.name === 'UnrecognizedClientException' || e?.name === 'InvalidClientTokenId') {
// Do not fail the cleanup and continue
console.log(`Listing apps for account ${account.accountId}-${region} failed with error with code ${e?.name}. Skipping.`);
return result;
Expand Down
Loading