Introduction

In my journey of setting up a Sitecore XM Cloud Site Collection, my goal was to integrate it with Sitecore Content Hub for managing campaigns and leveraging Sitecore’s marketing capabilities. However, while deploying the project to Vercel, I encountered several issues that provided valuable insights into the deployment process.

First Roadblock: API Key Not Generated

Before pushing my code to Vercel, I ran into the following error:

[Leave space for an error image and description]

Upon investigation, I found that the API key was not generated correctly. Additionally, I noticed that the XM Cloud Deployment App contained two versions of JSS (JavaScript Services)—one of which was outdated (older than xxx.xx). This mismatch caused inconsistencies in key management. After generating the correct API key, I retried the deployment.

Second Roadblock: 404 NOT_FOUND on Vercel

After successfully resolving the API key issue, I proceeded with the deployment using the following commands:

vercel
vercel --prod

Unfortunately, this resulted in a 404 NOT_FOUND error. Unlike typical 404 errors, Vercel assigns specific meanings to different error codes, making it crucial to refer to their documentation for proper resolution.

Next Steps

This blog is part of my XM Cloud Site Build series, and in the next post, I will provide a detailed breakdown of how I resolved the 404 NOT_FOUND issue. Stay tuned for more insights on successfully deploying Sitecore XM Cloud to Vercel.

Have you faced similar issues with Vercel deployments? Drop a comment below!