Persistent access control modal on amplify app builds

[prabhg]

Environment information

Package.json content from backend app:

"devDependencies": {
    "@aws-amplify/backend": "^1.3.0",
    "@aws-amplify/backend-cli": "^1.2.5",
    "@types/uuid": "^10.0.0",
    "aws-cdk": "^2.154.1",
    "aws-cdk-lib": "^2.154.1",
    "constructs": "^10.3.0",
    "esbuild": "^0.23.1",
    "tsx": "^4.18.0",
    "typescript": "^5.7.2"
  },
  "dependencies": {
    "@aws-amplify/data-schema": "^1.6.1",
    "@aws-amplify/datastore": "^5.0.49",
    "@aws-amplify/predictions": "^6.1.22",
    "@aws-appsync/utils": "^1.9.0",
    "@aws-lambda-powertools/logger": "^2.8.0",
    "@aws-sdk/client-dynamodb": "^3.656.0",
    "@aws-sdk/client-lambda": "^3.656.0",
    "@aws-sdk/lib-dynamodb": "^3.656.0",
    "@aws-sdk/util-dynamodb": "^3.656.0",
    "@clerk/clerk-js": "^5.18.0",
    "@clerk/clerk-sdk-node": "^5.0.44",
    "@types/aws-lambda": "^8.10.145",
    "@types/jsonwebtoken": "^9.0.6",
    "aws-amplify": "^6.5.2",
    "aws-sdk": "^2.1691.0",
    "axios": "^1.7.2",
    "install": "^0.13.0",
    "jsonwebtoken": "^9.0.2",
    "multipart-parser": "^0.0.2",
    "nanoid": "^5.0.8",
    "node-fetch": "^3.3.2",
    "pg": "^8.13.1",
    "svix": "^1.31.0",
    "uuid": "^10.0.0",
    "zod": "^3.23.8"
  }

Describe the bug

We consistently get a persistent access control modal on our amplify frontend app. Once the username/password is entered, it pops up again after few seconds, and it keeps happening again.

Reproduction steps

Enable the access control on the branch thru amplify console. Visit the url of the app. Notice the AC modal. Enter credentials. Notice that it pops up again after few seconds and process repeats.

[Jay2113]

Hi @prabhg 👋 , thanks for reaching out. I wasn't able to reproduce the behavior you outlined with the access control feature. Can you try clearing your browser cache? Also, if you have set custom headers on your app, I recommend redeploying the app.

Additionally, if the issue persists can you capture a HAR file and share it with us? Steps to capture the HAR file are outlined here: https://repost.aws/knowledge-center/support-case-browser-har-file.