Upgraded my app to 36.2 and it doesnāt look like my schemas are being loaded. Itās happening both on my app thatās taking full-advantage of what RW has to offer and on a small test-app, explained below.
I created the test-app (after hawking over my SDLs to make sure it wasnāt a typo), hooked it up to my local Postgres container, and added a simple model (AccountConfirmation) with an autogenerated ID. Then I used the RW CLI to generate an SDL, service, cell and page. The same error I was getting on my app I got again: Cannot query field "accountConfirmations" on type "Query". (When trying to use a mutation, itās: Schema is not configured for mutations.)
Taking a look at .redwood/schema.graphql, the query is being generated:
type Query {
accountConfirmations: [AccountConfirmation!]!
redwood: Redwood
}
On the playground, the accountConfirmations query is missing, however:
This is happening both with Apollo and in my app, which uses Envelope+Helix.
Traveling back to a commit I made right before updating, everything works as expected. The only changes I made in-between were to upgrade and a few inconsequential, QoL improvements.
I removed all comments from my SDL, no joy. Deleting and re-generating/installing node_modules, .redwood, and yarn.lock with all dependencies updated similarly, brought very little joy.
We are having the same error here at SportOffice, but maybe we can add different infos.
I upgraded main to v0.36.2, I had to do a lot of fixes on the web side due to our code using non RW components for forms, but eventually this did pass.
My coworker then created his branch and initiated his work, but he was still in v0.35.x. We then updated his branch with main and it crashed on that bug, which manifests as:
we can find a .redwood/schema.graphql properly built
web side is not using it, as in the front app crashes with queries not found in graphql type Query, and Apolloās playground would not load a properly populated schema but instead an empty one - with RW defaults.
We attempted the following without success:
cloning a new repo, building types from main and switching to the working branch
deleting .redwood and node_modules, running yarn install then yarn rw dev
On my machine we could reproduce the bug, but it got resolved after running yarn installwithout removing the aforementioned directories.
The only difference we could find so far is that itās running on linux machines but not on windows. Our production and preproduction environments, both on netlify, didnāt have the issue.
We didnāt touch our sdl to see if it could fix the problem, and we have a couple of comments in them.
Just upgraded the Open Sauced Admin Dashboard from v0.24 to v0.36.2, with the exception of some PgBouncer issues it seemed to work without any other major errors.
FYI: After upgrading I ran into a useRegister error that crashed a page that had form fields in it (e.g. <EmailField /> in my case, though I think the issue was more wide-spread than that specific field) and it seemed to get resolved by removing my explicit installation of react-hook-form from my project. No biggie at all, but this is something to look into if anyone else runs into a similar error while upgrading.