Skip to content
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.

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

Getting this error "!!! CustomerError: It looks like you are attempting to deploy a Next.js SSR app, but your app's framework looks wrong. Please update your app's framework to 'Next.js - SSR' to ensure that your app is deployed correctly." any support appreciated. thanks #3877

Closed
4 tasks done
azhar-rayn opened this issue Dec 22, 2023 · 8 comments
Labels
archived This issue has been locked. question Further information is requested

Comments

@azhar-rayn
Copy link

Before opening, please confirm:

App Id

NEW_APP

AWS Region

ap-southeast-1

Amplify Hosting feature

Monorepo

Question

My main branch is configured and app is running fine, but the sub domain that I am trying to serve from dev branch is failing with error "!!! CustomerError: It looks like you are attempting to deploy a Next.js SSR app, but your app's framework looks wrong. Please update your app's framework to 'Next.js - SSR' to ensure that your app is deployed correctly."
Any feedback/support is really appreciated

@azhar-rayn azhar-rayn added the question Further information is requested label Dec 22, 2023
@yangtopia
Copy link

I resolved it with the following command.

aws amplify update-branch --app-id {APP_ID} --branch-name {BRANCH_NAME} --framework 'Next.js - SSR'

I hope this helps.

@tigercat1124
Copy link

tigercat1124 commented Mar 27, 2024

It worked for me too!!

I resolved it with the following command.

aws amplify update-branch --app-id {APP_ID} --branch-name {BRANCH_NAME} --framework 'Next.js - SSR'

In my case, the issue was caused when the framework changed to Web due to the content of the code when I switched from the develop branch to the main branch.

image

@panachainy
Copy link

I resolved it with the following command.

aws amplify update-branch --app-id {APP_ID} --branch-name {BRANCH_NAME} --framework 'Next.js - SSR'

I hope this helps.

+1

@PhilipWee
Copy link

PhilipWee commented Apr 30, 2024

I am facing this same issue but I am deploying a react app. Is there any way to resolve it?

Some of my apps are nextjs and some are normal react in a monorepo, which I believe is why I am facing the issue

My app id is d19rklw56d9o2k if that helps

@alexff91
Copy link

It worked for me too!!

I resolved it with the following command.
aws amplify update-branch --app-id {APP_ID} --branch-name {BRANCH_NAME} --framework 'Next.js - SSR'

In my case, the issue was caused when the framework changed to Web due to the content of the code when I switched from the develop branch to the main branch.

image

for me worked only when I added the region like
aws amplify update-branch --app-id d1rudbio41kj5x --branch-name main --framework 'Next.js - SSR' --region ap-southeast-1

@pvhuwung
Copy link
Contributor

You can use the AWS CLI to solve this, remember to create an IAM account with the correct provision rules to work with Amplifier

  1. Run the following AWS CLI commands
aws amplify update-app --app-id <APP_ID> --platform WEB --region <REGION>
aws amplify update-branch --app-id <APP_ID> --branch-name <BRANCH_NAME> --framework 'Next.js - SSR' --region <REGION>
  1. Update your build spec to point the baseDirectory to out. e.g.
version: 1
frontend:
  ...
  artifacts:
    baseDirectory: out
  ...
  1. Trigger rebuild through commit, or manually

  2. You ready to go

Copy link

This issue is now closed. Comments on closed issues are hard for our team to see.
If you need more assistance, please open a new issue that references this one.

Copy link

This issue has been automatically locked.

@github-actions github-actions bot added the archived This issue has been locked. label Jun 26, 2024
@github-actions github-actions bot locked and limited conversation to collaborators Jun 26, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
archived This issue has been locked. question Further information is requested
Projects
None yet
Development

No branches or pull requests

8 participants