-
Notifications
You must be signed in to change notification settings - Fork 2
Unable to query any data from TinaCloud #293
Comments
This comment has been minimized.
This comment has been minimized.
@ACoolTurtle We just deployed a fix, it should be good now. |
This issue still remains, however rather than a 500 error, I get a 404 with |
Could you share a bit more information, what actions did you take? What is the GraphQL query? |
Just the standard request
It works on the LocalClient just fine with the local version being |
@ACoolTurtle Do you by any chance have a public repository to share so that we can reproduce the issue? |
@ACoolTurtle Thanks for submitting this issue! if your unable to share your code that is more then ok! the only thing we would need to reproduce this error is your schema.ts file and any other files that are imported from it. Since its working on your local environment and not on Tina Cloud I have a feeling it could be one of the following issues.
|
It's currently using |
@logan-anderson Sure, here is my schema, and the constants that are used. Thanks for your help |
@ACoolTurtle Thanks! for the files. I am not 100% sure but it seems that it is most likely the latter (point 2) I have a feeling that https://github.com/tinacms/tina-graphql-gateway/pull/304/files will fix it when it is merged and when Tina cloud bumps its version of "tina-graphql": "0.1.18". We apologize for the inconvenience and will update you when it's working. It's great to see such advanced usage of Tina Cloud! Thanks! |
Thanks for your support! I really like the idea of Tina |
@ACoolTurtle I just tested this and it looks like it is fixed (we update the version being used in the cloud). |
Description
No matter what the request is, TinaCloud's response is "Something went wrong".
Steps to reproduce
Make a Graphql request to the Tina Endpoint
Expected result
Data should be returned
Actual result
{"message":"Something went wrong."}
A vague error is returned.
Environment
Tinacms Package Versions
Tools
The text was updated successfully, but these errors were encountered: