Trouble publishing data on deployed Sanity studio, solved by adding production environment variables

HALP! I am having trouble publishing data on my deployed studio with Sanity. When I run the studio locally, I can change data and click publish and I see the toast immediately that it was published. My deployed studio doesn't show the toast and the publish button just stays green in limbo. I can refresh the studio and see that my changes are present in the editor, so it seems the draft is being saved but not published, because I can then reload my local development copy and it was publish right away with that drafted change.
Does anyone know why my deployed studio won't complete the publish process?

Additionally, each time that I deploy my studio, running

sanity deploy

, I am left with a series of modified files after the process completes. Is this normal?

I am left with a series of modified files after the process completes.

That’s normal. It’s the result of building the studio .
For the issue in your deployed studio, I assume there are no unusual errors in the console?

Oh goodness. There is an error in the console.

It's odd that the error is not present in my local, though.

Have you tried deploying more than once?
I came across
this post from last year, but unfortunately the problem seemed to resolve itself for the person (though that’s assuming the issues in your deployed studio are tied to this error).

Have you tried deploying more than once?
I came across
this post from last year, but unfortunately the problem seemed to resolve itself for the person (though that’s assuming the issues in your deployed studio are tied to this error).

Yes I deployed once again this morning.

I will try again.

Are you configuring for multiple environments in your env files, and if so, does anything differ besides the dataset?

I have not changed anything about the environment from the start, but I will look at my commits and see if something changed inadvertently.

no dice. The dataset is the same on both local and on sanity.studio : "production".

K, checking into it.

I assume you’re using your set slug on publish snippet? If so, has your deployed studio worked in the past with it?

Good question. I'm not sure that my snippet would cause an issue with the projectId, but it does work locally and has also worked deployed in the past.

That seemed like the most obvious place for me to look (since that code prevents publishing), but it does work locally.

I can both publish new Tags and I can publish edited Tags.

I find it especially karmic that a developer is having their own "it works on my machine" moment here. 😆

I find it especially karmic that a developer is having their own "it works on my machine" moment here. 😆

I'm going through the code of my slug documentAction. It uses the environment variables to instantiate a sanity client. Is there an issue with using these variables in production? I am certain that I've used this code in production before, but I've had egg on my face as early as two days ago so I'm willing to be wrong again.

Circling back here, , to say that the eggs are back and this time they are scrambled.
I disabled my slug snippet and publishing is working again in the deployed version of the studio. I will have to spend some time discovering the errors of my ways here. My thoughts are that this has to do with a difference in the availability of the environment variables that I have access to on the deployed studio, so I will go back to reading the documentation around that. Once I figure it out I'll be sure to bring those changes back to my community snippet as well!

Thanks for the rubber ducky'ing.
🙏

Okay, thanks Ken. I’d be interested to hear how you solve it.

I had a

.env.development

but not a

.env.production

. I found this line in the documentation:

For instance, a development configuration would be named .env.development while a production version would be .env.production

https://www.sanity.io/docs/studio-environment-variables
I might include a note on my snippet documentation about the need for production environment variables to expose the connection information that enables this snippet to pull from the database and check for other existing slugs before approving a publish.

I simply copied my a

.env.development

and named it

.env.production

and now it works!

I had a

.env.development

but not a

.env.production

. I found this line in the documentation:

For instance, a development configuration would be named .env.development while a production version would be .env.production

https://www.sanity.io/docs/studio-environment-variables
I might include a note on my snippet documentation about the need for production environment variables to expose the connection information that enables this snippet to pull from the database and check for other existing slugs before approving a publish.

Final note: I'm starting to realize that y'all have made things too easy. While I have read over this part of the documentation and I did so again, specifically, when I started working on this snippet; it turns out that I only read the first sentence and then moved on because my problem was easily resolved.
This time, reading the second sentence resolved my problem...


😂
Thanks!