Exporting schema leads to "forbidden" error and empty model

[tomekbuszewski]

Describe the Bug

Exporting the schema in one instance and importing it in another doesn't move any model fields and does not allow for admin access.

To Reproduce

1. Create an instance of Directus via Docker with custom Dockerfile installing directus-extension-schema-sync, install it with docker compose exec -it directus_1 npx directus schema-sync install --force
2. Create some models;
3. Run docker compose exec -it directus_1 npx directus schema-sync export-schema (in the first instance);
4. Create another instance of Directus via Docker with the same custom Dockerfile;
5. Run docker compose exec -it directus_2 npx directus schema-sync export-schema (in the second instance);
6. Access the admin panel of second instance.

I've put a git repo for easy reproduction with steps 1-4 already completed: https://github.com/tomekbuszewski/directus-schema-problem

Version

3.0.1

Installed Extension Via

Docker file

[u12206050]

Can you share your schema config (not your schema)
You would always first need to run bootstrap before using schema-sync. It won't work on an empty database.