Redeploying Hydrogen v1.3 on Vercel now causes Shopify API error when fetching data

[1forh]

What is the location of your example repository?

No response

What version of Hydrogen are you using?

1.3

What version of Remix are you using?

No response

Steps to Reproduce

Redeploy Hydrogen v1.3 on current Vercel platform.

Expected Behavior

Should build and load website successfully. All of our websites were working yesterday morning.

Actual Behavior

When loading the page and using the useShopQuery, now receiving this error in Vercel logs on multiple Hydrogen sites.

ERROR:  Failed to connect to the Storefront API: Invalid URL string.

Multiple websites were working yesterday using v1.3 of Hydrogen. All we did was redeploy them to Vercel yesterday afternoon after making a very small change, now they all show this error when loading and trying to connect to the Storefront API.

I'm not 100% sure what the URL it is referring to is but I've double checked that my store domain is correct if that is what it is talking about.

Any insight would be incredibly appreciated.

[1forh]

Upgrading to v1.4.3 seems to have fixed 2 out of 3 of the sites. Interesting and not sure why.

[georgeosutton]

Having the same issues v1.4.1 when redeploying on Vercel. Nothing has changed since last deployment.

[1forh]

@georgeosutton does upgrading to v1.4.3 help at all? It worked for 2 of my sites but not the third. Still wondering why.

[georgeosutton]

@georgeosutton does upgrading to v1.4.3 help at all? It worked for 2 of my sites but not the third. Still wondering why.

No but to the latest version v1.6.7 did help.

[juanpprieto]

My immediate advise is to bring this to Vercel. I have seen many frameworks failing to build/erroring after what seems like a big update to their backend.

In this discussion Vercel is suggesting pining down the build version via an env variable. Maybe this could help.

[georgeosutton]

My immediate advise is to bring this to Vercel. I have seen many frameworks failing to build/erroring after what seems like a big update to their backend.

In this discussion Vercel is suggesting pining down the build version via an env variable. Maybe this could help.

Thanks for this will be useful if problems persist.