Odissey - Lift-off V - Deploying Apollo Client - 503 on Client Application

Help
,
1

Hi,

I had Apollo production client working a second ago, but as I advanced to the “Field Deprecation” section, I added deprecation fields, pushed changes and re-deployed server and client, but now I get an error page on client, although server seems to be running fine (please check URLs at the end of this message). I noticed that I get this error on client application console:

2022-10-22_20h26_04
2022-10-22_20h26_041094×69 4.39 KB

These are the logs:

2022-10-22T23:17:41.447662+00:00 app[web.1]: 4: 0xd48137 v8::internal::V8::FatalProcessOutOfMemory(v8::internal::Isolate*, char const*, bool) [/app/.heroku/node/bin/node]
2022-10-22T23:17:41.449467+00:00 app[web.1]: 5: 0xf254f5 [/app/.heroku/node/bin/node]
2022-10-22T23:17:41.450266+00:00 app[web.1]: 6: 0xf379dd v8::internal::Heap::CollectGarbage(v8::internal::AllocationSpace, v8::internal::GarbageCollectionReason, v8::GCCallbackFlags) [/app/.heroku/node/bin/node]
2022-10-22T23:17:41.451161+00:00 app[web.1]: 7: 0xf120de v8::internal::HeapAllocator::AllocateRawWithLightRetrySlowPath(int, v8::internal::AllocationType, v8::internal::AllocationOrigin, v8::internal::AllocationAlignment) [/app/.heroku/node/bin/node]
2022-10-22T23:17:41.451986+00:00 app[web.1]: 8: 0xf134a7 v8::internal::HeapAllocator::AllocateRawWithRetryOrFailSlowPath(int, v8::internal::AllocationType, v8::internal::AllocationOrigin, v8::internal::AllocationAlignment) [/app/.heroku/node/bin/node]
2022-10-22T23:17:41.452782+00:00 app[web.1]: 9: 0xef467a v8::internal::Factory::NewFillerObject(int, v8::internal::AllocationAlignment, v8::internal::AllocationType, v8::internal::AllocationOrigin) [/app/.heroku/node/bin/node]
2022-10-22T23:17:41.453683+00:00 app[web.1]: 10: 0x12b7c1f v8::internal::Runtime_AllocateInYoungGeneration(int, unsigned long*, v8::internal::Isolate*) [/app/.heroku/node/bin/node]
2022-10-22T23:17:41.455931+00:00 app[web.1]: 11: 0x16e9879 [/app/.heroku/node/bin/node]
2022-10-22T23:17:41.663494+00:00 heroku[web.1]: Process exited with status 1
2022-10-22T23:17:41.726744+00:00 heroku[web.1]: State changed from up to crashed

When I run the client locally, everything works fine. On Apollo Studio, when I try to see the changelog, I get this page, although as I mentioned I’ve re-deployed both applications:

Your published schema has not changed since it was initially registered. Once changes are published, return here to see what’s changed. Learn more about schema registration by schema reporting by visiting our docs.

Can someone help me on this?

Thanks!!

2

The repos are:

3

I’m not sure if it’s related, but when I access https://studio.apollographql.com/ and click “Connect your GraphQL API” button, I get this:

2022-10-22_20h45_24
2022-10-22_20h45_241321×723 69 KB

4

Hey @fabioquixadaosf ! Thanks for all the info! We’ve had some product updates that aren’t reflected in Odyssey yet.

When creating your graph in Studio, could you follow these instructions? Understanding graphs - Apollo GraphQL Docs

You’ll want to read the section “To create a non-cloud graph” and expand the “Serverless plans” section (unless you have enterprise/legacy plans!).

Please let me know if that helps! We are working on updating the course contents.