XM cloud - Metadata editing failing when using beta feature "Authoring environments and Editing hosts"

[Nelsjnjr123]

What happened?

Description

Metadata editing is not working when using XM Cloud with the setting
“Now you can use different repositories for your Authoring environments and Editing hosts” enabled.
The issue occurs in a project created based on these settings.

Reproduction Steps

1. Open

   Project Setup

   • Created an XM Cloud project with the "different repositories for your Authoring environments and Editing hosts" (beta feature) enabled.
   • Used the Next.js starter kit for the main site.
   • Created two authoring environments:
     • One using the Next.js starter kit.
     • Another using the ASP.NET Core (.NET) starter kit from Sitecore's GitHub repo.

   Editing Host Configuration:

   • For the Next.js site:
     • A dedicated editing host was created.
     • Metadata editing works as expected.
   • For the .NET Core site:
     • No editing host was created.
     • The site is published and accessible via localhost:5001.
     • Attempting metadata editing results in the error:
     • "Could not connect to host."
   • Tried tunneling by registering a rendering host under:
   • /sitecore/system/Settings/Services/Rendering Hosts
   • using the tunneling values, but received the following error in the Page Editor:

   Error Rendering Rendering: /sitecore/layout/Devices/Default: Unexpected character encountered while parsing value: <. Path '', line 0, position 0.

2. Execute

Actual Behavior

Metadata editing is not working, but when we create a XM cloud project without the (Now you can use different repositories for your Authoring environments and Editing hosts) setting enabled it works, but when creating a fresh project and environments then the metadata editing not works even after configuring tunnelling setting in /sitecore/system/Settings/Services/Rendering Hosts.

Expected Behavior
Metadata editing should work similarly like when the setting (Now you can use different repositories for your Authoring environments and Editing hosts) disabled in xmcloud,
I hope this issue is causing because there is no editing host available for aspnet core in the starter kit.

Relevant log output

Code of Conduct

• I agree to follow this project's Code of Conduct