After installing v1.3.0-beta.1, when I toggle the relay switch, the explorer doesn't show any schema. I've also tried a few other graphql tools, none can introspect the relay schema. I'd be happy to provide any info you need to debug, just let me know.
Having said that, I can run graphql queries against the relay endpoint perfectly fine, since I happen to know the shape of the query.
I don't have a full repro for this, but I believe it's to do with how views are exposed.
I have a view that's essentially a table with some extra metadata joined in, with an id field.
When I look at the network request for the introspection schema, I get the following error message:
{"errors":[{"extensions":{"path":"$","code":"unexpected"},"message":"type info not found for: 'accounts_view'"}]} where accounts_view is a view over accounts.
Note that on the regular view, accounts_view would be the second item to be exposed not the first, suggesting it's this particular view and not whatever table/view was found first.

@njaremko Please give us minimal reproduction schema.
@Winwardo I could confirm the issue. It'll be fixed in next beta release.
Similarly, I'm getting
{"errors":[{"extensions":{"path":"$","code":"unexpected"},"message":"type info not found for: 'user_roles_select_column'"}]}
user_roles is a view
CREATE VIEW user_roles AS
SELECT role_id as id, model_id as user_id, name, created_at, updated_at
FROM model_has_roles
LEFT JOIN roles
ON model_has_roles.role_id = roles.id
WHERE model_type = 'users'
Here are the relevant schemas:
-- Sequence and defined type
CREATE SEQUENCE IF NOT EXISTS roles_id_seq;
-- Table Definition
CREATE TABLE "public"."roles" (
"id" int4 NOT NULL DEFAULT nextval('roles_id_seq'::regclass),
"name" varchar(255) NOT NULL,
"guard_name" varchar(255) NOT NULL,
"created_at" timestamp(0),
"updated_at" timestamp(0),
PRIMARY KEY ("id")
);
CREATE TABLE "public"."model_has_roles" (
"role_id" int4 NOT NULL,
"model_type" varchar(255) NOT NULL,
"model_id" int8 NOT NULL,
CONSTRAINT "model_has_roles_role_id_foreign" FOREIGN KEY ("role_id") REFERENCES "public"."roles"("id") ON DELETE CASCADE,
PRIMARY KEY ("role_id","model_id","model_type")
);
@njaremko @Winwardo
Please try the preview app in the comment and let us know if the issue still persists.
Thank you.
I updated my Docker image to hasura/graphql-engine:pull5013-f7fd3648, without changing anything else, and now I can see the Relay schema.

Thank you!
Schema introspection works using the version from that PR, but the Relay schema is missing all my views. For example, with the above schema I have user_roles in my non-relay schema, and only users_connection in the relay schema.
I opened a new issue for that - but have just realised that it's probably still related to this particular issue + PR.
Most helpful comment
@Winwardo I could confirm the issue. It'll be fixed in next beta release.