Empty API Mock editor #1269

dan-hook · 2023-02-04T16:38:52Z

How did you install the Amplify CLI?

npm

If applicable, what version of Node.js are you using?

v18.14.0

Amplify CLI Version

10.7.0

What operating system are you using?

Ubuntu 22.04 on WSL2 on Windows 10

Did you make any manual changes to the cloud resources managed by Amplify? Please describe the changes made.

Yes, the changes are extensive.

Describe the bug

I ran apt-get install java-11-amazon-corretto-jdk to install Java.

Running amplify mock api launches Amplify GraphiQL Explore on localhost:20002, but it's empty saying "No Schema Available".
The CLI output is:
vscode ➜ .../panel-api/project/amplify/backend (features/VCD-504-ecv-api ✗) $ amplify mock api
GraphQL schema compiled successfully.

Edit your schema at /workspaces/gene-panel-api/project/amplify/backend/api/genepanelapi/schema.graphql or place .graphql files in a directory at /workspaces/gene-panel-api/project/amplify/backend/api/genepanelapi/schema
Mock does not handle CloudFormation resource of type AWS::IAM::ManagedPolicy. Skipping processing resource AuthRolePolicy01.
Mock does not handle CloudFormation resource of type AWS::IAM::ManagedPolicy. Skipping processing resource AuthRolePolicy02.
Mock does not handle CloudFormation resource of type AWS::IAM::ManagedPolicy. Skipping processing resource AuthRolePolicy03.
Data source of type RELATIONAL_DATABASE is not supported by local mocking. A NONE data source will be used.
Data source of type HTTP is not supported by local mocking. A NONE data source will be used.
Data source of type HTTP is not supported by local mocking. A NONE data source will be used.
Data source of type HTTP is not supported by local mocking. A NONE data source will be used.
Could not find ref for "RdsPanelDbName". Using unsubstituted value.
Could not find ref for "RdsPanelDbName". Using unsubstituted value.
Running GraphQL codegen
✔ Generated GraphQL operations successfully and saved at ../../src/graphql
AppSync Mock endpoint is running at http://172.17.0.2:20002
Re-Trying with a new shard
Re-Trying with a new shard
Re-Trying with a new shard
Re-Trying with a new shard
Re-Trying with a new shard
Re-Trying with a new shard
Re-Trying with a new shard
Re-Trying with a new shard
Re-Trying with a new shard
Re-Trying with a new shard
Re-Trying with a new shard
Re-Trying with a new shard
Re-Trying with a new shard
Re-Trying with a new shard
Re-Trying with a new shard
Re-Trying with a new shard
Re-Trying with a new shard
Re-Trying with a new shard
Re-Trying with a new shard
Re-Trying with a new shard
Re-Trying with a new shard
Re-Trying with a new shard
Re-Trying with a new shard
Re-Trying with a new shard
Re-Trying with a new shard
Re-Trying with a new shard
Re-Trying with a new shard
Mock DB deletion detected. Clearing the OpenSearch indices...
Re-Trying with a new shard
Re-Trying with a new shard
Failed to start API Mocking. Running cleanup tasks.
MockProcessFault: Failed to start API Mocking.. Reason: null
at APITest.start (/snapshot/repo/build/node_modules/amplify-util-mock/lib/api/api.js:151:13)
at runMicrotasks ()
at processTicksAndRejections (internal/process/task_queues.js:95:5)
at async start (/snapshot/repo/build/node_modules/amplify-util-mock/lib/api/index.js:18:5)
at async Object.run (/snapshot/repo/build/node_modules/amplify-util-mock/lib/commands/mock/api.js:21:5)
at async Object.executeAmplifyCommand (/snapshot/repo/build/node_modules/amplify-util-mock/lib/amplify-plugin-index.js:47:3)
at async executePluginModuleCommand (/snapshot/repo/build/node_modules/@aws-amplify/cli-internal/lib/execution-manager.js:142:5)
at async executeCommand (/snapshot/repo/build/node_modules/@aws-amplify/cli-internal/lib/execution-manager.js:40:9)
at async Object.run (/snapshot/repo/build/node_modules/@aws-amplify/cli-internal/lib/index.js:117:5) {
classification: 'FAULT',
options: {
message: 'Failed to start API Mocking.. Reason: null',
link: 'https://docs.amplify.aws/cli/graphql/troubleshooting/'
},
downstreamException: undefined,
toObject: [Function (anonymous)],
details: undefined,
resolution: undefined,
code: undefined,
link: 'https://docs.amplify.aws/cli/graphql/troubleshooting/'
}

Expected behavior

I expected to see the API in the explorer.

Reproduction steps

Run 'amplify mock api'

Project Identifier

9c19ea5526c1afd0a3e1987ea44f96af

Log output

# Put your logs below this line

Additional information

No response

Before submitting, please confirm:

I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.
I have removed any sensitive information from my code snippets and submission.

The text was updated successfully, but these errors were encountered:

raphipaffi · 2023-02-05T22:09:27Z

I have the same issue. Also using amplify 10.7.0. I am on a Mac M1. Looks very similar to this issue that already got resolved in 9.0.0 couple months ago: aws-amplify/amplify-cli#10578

issakr · 2023-02-06T17:26:24Z

Same issue on amplify 10.7.1. I am also on a Mac M1.

josefaidt · 2023-02-06T17:29:23Z

Hey @dan-hook 👋 thanks for raising this! Was the amplify/mock-data directory deleted before mock finished initializing? Looking at this log item:

Mock DB deletion detected. Clearing the OpenSearch indices...

@raphipaffi @issakr on M1 macs you will need to install the 64-bit version of Java

For example, this is the Java version I am running locally on my M1 mac

➜  java -version
openjdk version "18.0.1.1" 2022-04-22
OpenJDK Runtime Environment (build 18.0.1.1+2-6)
OpenJDK 64-Bit Server VM (build 18.0.1.1+2-6, mixed mode, sharing)

issakr · 2023-02-06T18:06:42Z

I already use openjdk
`➜ java -version

openjdk version "17.0.4.1" 2022-08-12
OpenJDK Runtime Environment Temurin-17.0.4.1+1 (build 17.0.4.1+1)
OpenJDK 64-Bit Server VM Temurin-17.0.4.1+1 (build 17.0.4.1+1, mixed mode)`

dan-hook · 2023-02-06T21:24:32Z

Hey @dan-hook 👋 thanks for raising this! Was the amplify/mock-data directory deleted before mock finished initializing? Looking at this log item:
Mock DB deletion detected. Clearing the OpenSearch indices...

I think that log item is spurious and may have even been caused by my computer going to sleep. There was 5-10 minutes between each "Re-Trying with a new shard". I stopped checking the Explorer after about six of them.

This is a complicated Amplify project and this is the first time I've tried running aws mock api on it. There were a number of issues such as VTL parsing errors that I needed to fix before I got this far, and I'm not surprised that there are still more issues. I'm not surprised it doesn't work, I just wish there was a better error message.

raphipaffi · 2023-02-10T19:22:22Z

I already have Java 64bit installed

➜ route-planner git:(master) ✗ java -version
openjdk version "19.0.2" 2023-01-17
OpenJDK Runtime Environment Homebrew (build 19.0.2)
OpenJDK 64-Bit Server VM Homebrew (build 19.0.2, mixed mode, sharing)

Let me know if there is anything else I can try.

josefaidt · 2023-02-14T16:52:22Z

Hey @raphipaffi @issakr given the M1 issue is different than what this issue is describing, would y'all mind filing a separate bug report to track your issue separately? We want to be sure this is addressed and documentation is updated if necessary. Do you experience the same issue using the official distribution from the OpenJDK downloads page?

@dan-hook

This is a complicated Amplify project and this is the first time I've tried running aws mock api on it.

Would you be open to sharing your schema.graphql? Do you have any overridden, slotted resolvers or custom resolvers that are causing the VTL parsing errors?

Upon further review of the error messaging I see the following error, are you using a Relational Database with your GraphQL API?

Data source of type RELATIONAL_DATABASE is not supported by local mocking. A NONE data source will be used.

NicholasAllen · 2023-02-17T14:11:44Z

I also started suffering this issue. I was trying on the 10.7.3 and 10.7.2 client builds. The following comment helped me resolve it for now: aws-amplify/amplify-cli#10488 (comment) - downgrade to 10.6.2 and it's working again.

raphipaffi · 2023-02-17T22:52:53Z

@NicholasAllen thank you so much for that tip! That downgrade also "fixed" it for me.

josefaidt · 2023-02-18T00:38:27Z

Hey folks I'm able to reproduce this issue using the Todo schema. Marking as a bug

kmy90 · 2023-04-04T15:29:35Z

Hi, there is an ETA for the resolution of this bug?

dwamianm · 2023-04-17T14:39:27Z

@josefaidt. We are still experiencing this issue in 11.0.5. Any update on the fix?

FYI. Clearing mock files does not help. . I have @searchable annotations so I am unable to go back to 10.x.x

espenbye · 2023-04-24T12:30:50Z

We are experiencing the same issue on 11.0.5.

dwamianm · 2023-04-27T20:20:00Z

@josefaidt @phani-srikar This issue still exists in 11.1.0.

I would love to have this addressed if possible. I cannot downgrade to 10.6.2 because I am using OpenSearch mocking, which is only available in 11.x.x. I realize this may not seem like a priority but as a longtime Amplify. user it's a huge disadvantage to not have this feature in API mocking.

Any updates?

dwamianm · 2023-06-05T14:21:13Z

@josefaidt @phani-srikar ... any updates on this bug? It has really slowed development to not be able to use the tools to test locally. I am commenting here because It has been so long and I would really love to get this bug addressed so I can be on an updated amplify version. I am still stuck on 10.6.2 just to be able to get this to work :(

dwamianm · 2023-06-15T17:50:24Z

Checking for any updates on this bug. Still exists in 12.1.0

remotehpc · 2023-07-04T22:31:17Z

Hey folks I'm able to reproduce this issue using the Todo schema. Marking as a bug

Hi Josef, are you able to resolve the bug or provide a walkaround? My team has been stuck here for too long, any help would be greatly appreciated!

Best regards!

aoi · 2023-07-06T00:50:13Z

@josefaidt Hi josefaidt.

Thank you for your response.

You have transfered this issue from amplify-cli repository to here.
But the code has probrem is not in this repository. It is in amplify-cli repository.
Please see my PR in amplify-cli repository.

amplify mock is very useful and important function for developers. A lot of developers are stuck in this bug for months.
I would appreciate it if you could respond promptly.

Best regards,

pridapablo · 2023-07-27T01:25:30Z

I found that the error directly comes from adding Cognito User Pool auth to the api, no matter if API or IAM is also enabled. Working with amplify -v 12.0.0 since amplify mocks fail completely on m2 Mac using the latest version of the cli.

jmelendev · 2023-07-27T01:36:38Z

Im using -v 12.2.0 and seeing the same issues. I am seeing the following error in the console:

"Error: Error when generating OIDC token: Right-hand side of 'instanceof' is not an object"

This was working fine earlier today, not sure what changed recently.

araymond11 · 2023-08-27T20:49:42Z

Any updates ? Same issue with Amplify CLI version 12.3.0.

kita3222 · 2023-09-27T04:26:49Z

I have confirmed that it also occurs in v12.4.0.

araymond11 · 2023-10-18T22:53:21Z

Still occurs in v12.7.0.

afnx · 2023-11-20T07:31:46Z

It's been months and still not able to see anything on Amplify GraphiQL Explorer.

There is this Uncaught (in promise) Error: Error when generating OIDC token: invalid 'instanceof' operand g error that everybody mentioned on my browser console.

Also, when I try to execute a query, I always get the unauthorized error:

{
  "errors": [
    {
      "errorType": "UnauthorizedException",
      "message": "UnauthorizedException: Missing authorization"
    }
  ]
}

zakton5 · 2023-11-21T19:07:04Z

As mentioned by others developing and testing locally is very important and without it the development process is far slower. @josefaidt Are there any updates?

kmy90 · 2023-12-18T21:52:59Z

Hi everyone, this issue was opened almost 1 year ago. It is NOT a MINOR bug. There are teams around the world that are not able to use the latest version of Amplify just because of this problem. Could you help us, @josefaidt, @alharris-at ?

rafadpedrosa · 2024-01-21T14:44:33Z

I would like to share my experience, maybe will help someone.

Yes, I'm having the same issue as everyone. But, given that I use nvm to control my node versions, I "manage" to deal with this problem installing different amplify-cli version on different node version as mentioned here.

nvm use 20 
npm install npm install -g @aws-amplify

nvm use 18 
npm install -g @aws-amplify/[email protected] // working version

Also, I do agree with @kmy90. It should not be treated as a minor thing.

afnx · 2024-01-31T09:57:55Z

Hey folks, this is a serious issue here impacting everyone and disrupting the development process. Using workarounds, like downgrading the Amplify version, isn't the most convenient solution. Personally, I struggled with testing my projects locally using the explorer, and it really bothered me that such an important issue had been left unattended for a year.

I fixed it by creating a PR (aws-amplify/amplify-cli#13555). Can you please support it? We need the Amplify team to review and approve the fix. Thanks!

zepelega · 2024-03-17T22:46:39Z

Still occurs in v12.10.1.

afnx · 2024-04-25T01:25:30Z

Fixed in version 12.11.0

github-actions · 2024-10-16T13:53:14Z

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.

dan-hook added the pending-triage label Feb 4, 2023

josefaidt added pending-response mock labels Feb 6, 2023

github-actions bot removed the pending-response label Feb 6, 2023

josefaidt added the pending-response label Feb 14, 2023

josefaidt transferred this issue from aws-amplify/amplify-cli Feb 18, 2023

josefaidt added bug Something isn't working p1 p2 and removed pending-triage pending-response p1 labels Feb 18, 2023

josefaidt mentioned this issue Feb 22, 2023

No Schema Available in GraphQL local mock #1287

Closed

2 tasks

josefaidt mentioned this issue Apr 18, 2023

Amplify mock doesn't work with Cognito User Pool #1369

Open

2 tasks

michaelrios mentioned this issue Apr 28, 2023

Amplify Mock is not working again #1427

Closed

2 tasks

josefaidt mentioned this issue Jul 5, 2023

Amplify mock doesn't work with Cognito User Pool #1646

Closed

2 tasks

alharris-at added the theme:mock label Aug 21, 2023

josefaidt mentioned this issue Sep 18, 2023

Unable to see my schema using amplify mock #1866

Closed

2 tasks

afnx mentioned this issue Jan 25, 2024

fix: resolve issues with graphiql explorer aws-amplify/amplify-cli#13555

Closed

6 tasks

dpilch mentioned this issue Apr 3, 2024

fix: resolve issues with graphiql explorer aws-amplify/amplify-cli#13691

Merged

3 tasks

chrisbonifacio closed this as completed Oct 16, 2024

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Empty API Mock editor #1269

Empty API Mock editor #1269

dan-hook commented Feb 4, 2023 •

edited

Loading

raphipaffi commented Feb 5, 2023

issakr commented Feb 6, 2023

josefaidt commented Feb 6, 2023

issakr commented Feb 6, 2023 •

edited

Loading

dan-hook commented Feb 6, 2023

raphipaffi commented Feb 10, 2023 •

edited

Loading

josefaidt commented Feb 14, 2023 •

edited

Loading

NicholasAllen commented Feb 17, 2023

raphipaffi commented Feb 17, 2023

josefaidt commented Feb 18, 2023 •

edited

Loading

kmy90 commented Apr 4, 2023

dwamianm commented Apr 17, 2023 •

edited

Loading

espenbye commented Apr 24, 2023

dwamianm commented Apr 27, 2023

dwamianm commented Jun 5, 2023

dwamianm commented Jun 15, 2023

remotehpc commented Jul 4, 2023

aoi commented Jul 6, 2023 •

edited

Loading

pridapablo commented Jul 27, 2023

jmelendev commented Jul 27, 2023

araymond11 commented Aug 27, 2023

kita3222 commented Sep 27, 2023 •

edited

Loading

araymond11 commented Oct 18, 2023

afnx commented Nov 20, 2023

zakton5 commented Nov 21, 2023 •

edited

Loading

kmy90 commented Dec 18, 2023

rafadpedrosa commented Jan 21, 2024

afnx commented Jan 31, 2024

zepelega commented Mar 17, 2024

afnx commented Apr 25, 2024

github-actions bot commented Oct 16, 2024

Empty API Mock editor #1269

Empty API Mock editor #1269

Comments

dan-hook commented Feb 4, 2023 • edited Loading

How did you install the Amplify CLI?

If applicable, what version of Node.js are you using?

Amplify CLI Version

What operating system are you using?

Did you make any manual changes to the cloud resources managed by Amplify? Please describe the changes made.

Describe the bug

Expected behavior

Reproduction steps

Project Identifier

Log output

Additional information

Before submitting, please confirm:

raphipaffi commented Feb 5, 2023

issakr commented Feb 6, 2023

josefaidt commented Feb 6, 2023

issakr commented Feb 6, 2023 • edited Loading

dan-hook commented Feb 6, 2023

raphipaffi commented Feb 10, 2023 • edited Loading

josefaidt commented Feb 14, 2023 • edited Loading

NicholasAllen commented Feb 17, 2023

raphipaffi commented Feb 17, 2023

josefaidt commented Feb 18, 2023 • edited Loading

kmy90 commented Apr 4, 2023

dwamianm commented Apr 17, 2023 • edited Loading

espenbye commented Apr 24, 2023

dwamianm commented Apr 27, 2023

dwamianm commented Jun 5, 2023

dwamianm commented Jun 15, 2023

remotehpc commented Jul 4, 2023

aoi commented Jul 6, 2023 • edited Loading

pridapablo commented Jul 27, 2023

jmelendev commented Jul 27, 2023

araymond11 commented Aug 27, 2023

kita3222 commented Sep 27, 2023 • edited Loading

araymond11 commented Oct 18, 2023

afnx commented Nov 20, 2023

zakton5 commented Nov 21, 2023 • edited Loading

kmy90 commented Dec 18, 2023

rafadpedrosa commented Jan 21, 2024

afnx commented Jan 31, 2024

zepelega commented Mar 17, 2024

afnx commented Apr 25, 2024

github-actions bot commented Oct 16, 2024

dan-hook commented Feb 4, 2023 •

edited

Loading

issakr commented Feb 6, 2023 •

edited

Loading

raphipaffi commented Feb 10, 2023 •

edited

Loading

josefaidt commented Feb 14, 2023 •

edited

Loading

josefaidt commented Feb 18, 2023 •

edited

Loading

dwamianm commented Apr 17, 2023 •

edited

Loading

aoi commented Jul 6, 2023 •

edited

Loading

kita3222 commented Sep 27, 2023 •

edited

Loading

zakton5 commented Nov 21, 2023 •

edited

Loading