This article describes the known issues with the Sitecore® Experience Platform™ 10.1 Initial Release.
For all Sitecore Experience Platform documentation, visit the Sitecore Documentation Site.
For information about the availability of the fixes for the mentioned known issues, refer to the Release Notes of the future Sitecore Experience Platform releases.
- In the Kubernetes environment, screenshots are not generated in the Preview and start test window (458908).
Sitecore Headless Rendering 16.0.0 and Sitecore JavaScript Services 16.0.0:
- The Next.js Experience Editor integration does not work on Vercel when a route is configured with "fallback: false". This is caused by an open issue in Next.js: https://github.com/vercel/next.js/issues/16681 (460905).
- The GraphiQL UI shows an unhelpful error message that contains HTML markup for invalid queries (461176).
- The Layout Service returns an object reference error when the rendering definition item is missing for any rendering on an item (462233).
- Deploying two JSS sample applications with the same templates can cause broken GraphQL queries in sample code, due to duplicate template names (463187).
- Browsing a JSS site in Connected mode after opening the same site in the Experience Editor causes editing controls to be displayed. This is caused by shared cookies (463386).
- If you open an Angular-based JSS application in the Experience Editor, you might briefly see a page does not exist error before the page renders correctly (463527).
- When you open a Next.js-based JSS application in the Experience Editor, you might see a Warning: Prop "phkey" did not match error. This error does not affect content editing and you can ignore it (463325).
- If you provide an incorrect API Key, the GraphiQL UI sometimes shows an unhelpful error message that contains HTML markup (464009)
- When you open a JSS application in the Experience Editor, you might see a TypeError: Cannot read property 'baseNode' of undefined error in the console. For Next.js, you might see an on-screen indicator for this error when you are in development mode. This error does not affect content editing (464010)
Sitecore.CLI 3.0.0:
- Pushing a language item with Sitecore Content Serialization does not clear the language provider cache.
- On the Launchpad, the text for the Horizon icon does not fall back to English language version (458916).
- The Preference center is not updated in some situations (459455).
- If Sitecore Identity Server is enabled, authorized users are redirected to the login page (378901).
- If personalization is set on the whole composite component, it does not work (428358).
- If a user attempts to assign a data source to a component in the Content Editor, an error is displayed (444859).
- In the data source selection dialog, you cannot create a local data source for a component that already exists on a page (451739).
- Personalization does not work for composite components that use local data sources (450108).
- When one of the two composite components that use the same data source is removed from a page, the layout information that is stored in the data source is deleted (450122).