You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I tried to make production release to Vercel with customized GraphQL Endpoint and I got this error: [MV-0001] "sitecoreEdgeContextId" is required. I got correct data from custom Edge, but then this Exception is raised.
I created custom GraphQL Endpoint with URL /sitecore/api/graph/edgePreview and this was deployed to Sitecore XM Cloud. This endpoint returns data of items in specific workflow states. I need to have non public site, which displays site without Draft workflow items. This works for local development, but not for production.
I was able to identify reason, why it works in dev environment.
headapps\XXX\src\Bootstrap.tsx
.....
if (process.env.NODE_ENV === 'development') {
console.debug('Browser Events SDK is not initialized in development environment');
}
.....
else {
CloudSdk({...})
}
If I modify this condition, I am able to connect to different Edge and application works.
I tried to make production release to Vercel with customized GraphQL Endpoint and I got this error: [MV-0001] "sitecoreEdgeContextId" is required. I got correct data from custom Edge, but then this Exception is raised.
I created custom GraphQL Endpoint with URL /sitecore/api/graph/edgePreview and this was deployed to Sitecore XM Cloud. This endpoint returns data of items in specific workflow states. I need to have non public site, which displays site without Draft workflow items. This works for local development, but not for production.
Environment variables looks like this:
SITECORE_API_KEY=XXX
GRAPH_QL_ENDPOINT=https://XXX.sitecorecloud.io/sitecore/api/graph/edgePreview
SITECORE_SITE_NAME=XXXX
DEFAULT_LANGUAGE=en
GRAPH_QL_SERVICE_RETRIES=3
FETCH_WITH=GraphQL
In previous versions it was not necessary to set SITECORE_EDGE_CONTEXT_ID for production. Is there any solution for this use case?
The text was updated successfully, but these errors were encountered: