gatsby site will not start due to major error about gatsby-auth-starter-aws-amplify

[marksteven]

had another few added all dependancies again.
still no joy
getting these fatal errors
and boilerplate will not start.
ERROR

Missing onError handler for invocation 'building-schema', error was 'Error: Cannot create as TypeComposer the following value: Date.'. Stacktrace was 'Error: Cannot create as TypeComposer the following value: Date.

[nicolasheady]

I'm having same issues. Deleted package-lock.json and node_modules and reinstalled using npm, with no luck. I even installed all peer dependencies manually, no luck.

[marksteven]

I hear you.
Still trying to get any Gatsby project to work properly on AWS.
Fine locally and if I put it up on AWS via drag and drop also good
via Github continuous development it keeps failing
Fine until you add Auth to project.
Is yours working locally?
Lots of different theories on where the Auth files should go
Eg in Gatsby-browser or on the actual page only.
One thing that seems to be working better that you might want to try is
not use withAuthentication but rather AmplifyAuthenticator from @aws-amplify/ui-react
Ill post here if I finally work it out.

[nicolasheady]

I did get it to work locally, but it will not deploy. I got it working locally by switching to installing with yarn instead of npm. But now it errors out when building the backend when I try to deploy on the Amplify Console. I get an "AccessDenied" error. Still working on this one.

[marksteven]

OK so same as me.
Im am on a conference call to AWS tech in few hours.
Will let you know how I go as he seems to think it should be OK

[marksteven]

Can you please maybe send me the log of the errors
I will put that to him as well

[nicolasheady]

log.txt
I don't think there's any sensitive data in the log file? The only difference between the instructions for this starter Gatsby site and what I did, is I copied the repo into AWS code commit instead of using GitHub.

[marksteven]

Had a look. All good there but you have
The engine "node" is incompatible with this module. Expected version "^10.17.0 || ^12.0.0 || >= 13.7.0". Got "10.16.0"
2020-10-21T02:23:16.671Z [WARNING]: error Found incompatible module.

On your project
Go into amplify/backend/sometingsomethingcloudformation-template.yml
search node
If like me it says 10x
adjust that to read 12x
save
try again.

If not try in your build on AWS try
commands:
- yarn install --ignore-engines
Might as well let you know what I have learned so far.
Even though your system is probably up to date for some reason it loads an old NodeJS
that should correct it and the build is something else I had partial success with

[nicolasheady]

Oh that was in there? That error has been coming and going, but I will give your fix a try for that.

[marksteven]

Hi Nicolas Seems it is very much in the build sequence. Also seems the technicians are currently in the process of updating the Gatsby interface on amplify so there might be some weird experiences over the coming weeks as well so keep in mind.
Anyway actually got it working using these build commands so give them a try (If you are using Yarn)
Also found out you need to be very careful editing the YML file so make sure the dashes line up exactly above each other as white space is seemingly counted in these types of file on AWS.
so copy and past exactly below. Will put up screen shot as well.
Cheers and good luck
Mark

version: 1
backend:
phases:
build:
commands:
- '# Execute Amplify CLI with the helper script'
- amplifyPush --simple
frontend:
phases:
preBuild:
commands:
- yarn --v
- yarn install
build:
commands:
- yarn run build
artifacts:
baseDirectory: public
files:
- '/*'
cache:
paths:
- node_modules//*

[nicolasheady]

Using just those build settings, I get both of these errors/warnings in the backend build:

(node:1961) UnhandledPromiseRejectionWarning: AccessDenied: Access Denied

[email protected]: The engine "node" is incompatible with this module. Expected version "^10.17.0 || ^12.0.0 || >= 13.7.0". Got "10.16.0"

However, if I change the build settings to the below. I do not get the above errors, but I do get this error on the FRONTEND build:

error Generating JavaScript bundles failed
Can't resolve '../aws-exports' in '/codebuild/output/src256105377/src/ripcodes/src/pages'

I do have the aws-exports file locally. But it is part of git ignore, and should be generated when building on the console.

Build Settings, as discussed here: aws-amplify/amplify-hosting#1087

There are a lot of open and closed issues related to what I'm experiencing, I've been working through then trying the solutions and this is my most recent progress.

[marksteven]

try this for the engines

• yarn install--ignore-engines

[nicolasheady]

Well I cannot speak to what exactly solved my problem, but I pretty much recreated everything from scratch and now I've had minimal issues getting it running.