I created a new repository, following the steps in the terminal.
I opened Slice Machine, created a document (Page type) and after creating it, when accessing Page Builder, I got the error "Prismic has encountered an error" and the browser console returns "Error: Cannot find a master locale."
I am quite familiar with the process and have done it several times in many projects. It was expected that at this point, I would select the language, so that I could then start creating the documents in Page Builder.
What did I try to do to solve the problem and it didn't work?
Activate Legacy Builder
Add a locale through the URL settings/multi-languages/
Create a document by accessing the URL builder/pages/new?custom_type=home&locale=en-us, I can open the URL, but when I click Save, I get an error, probably because there is no master language.
This error has been happening since Friday, I tried again today (Monday) and it didn't work. I've already created the project and the repository several times and it always gives an error, even trying with different names.
I also get this error a lot when I am using Chrome. Switching to Firefox I have not had this issue. I also find that sometimes clearing cookies in Chrome will get this error to go away.
I am using Chrome, I logged into Prismic via Firefox, with cleared cookies, and when I clicked on the repository, I got the error message. Unfortunately, it didn't work for me.
I finally managed to solve my problem. I had to create the repository directly on the Prismic website, instead of doing it via CLI, which is how it is described in the documentation.
This way, I have me the opportunity to choose a default language, which was the cause of the problem.
Then, I had to link the repository to the project using the command:
Is it a known issue that creating repos doesn't work via the web app? I've tried multiple times now and every single one ends up getting the locale error.
It's a known issue. We're working on a fix, although as far as we're aware the issue is no longer blocking you from continuing - have you tried refreshing the page when you see the error and see if it lets you go on?