Another quick update: The issue was fixed by an Apple engineer manually removing the corrupted Home from their side.

Quick update on anyone with the same issue: I had a call with two CloudKit engineers last week and they basically confirmed my theory that something is corrupted. Essentially one of my homes is shared with an inexistant Apple ID (no clue how that happened, the other Apple ID still exists), so that's why iCloud servers are continuously responding with Not Authenticated and Internal Server Error. In other words, there's nothing you can do client-side, you need to have a CloudKit engineer manually delete the broken home from your iCloud. @Marco and @John, could I have a quick update on the deletion of the corrupted home? It's been a week and I don't have any other way to contact you other than this forum post. 😕

Using the reset profile for HomeKit on a device running iOS/iPadOS 17.5.1 (as was suggested by an Apple Engineer) does not reset the container. Logs show that the iCloud container is (I would assume) too corrupted to purge. The following error is logged repeatedly: [Reset Config] purgeShares CKModifyRecordsOperation failed: <CKError 0xc7b21f5d0: "Internal Error" (1/1000); "Received a didCompleteWithError without an error but no response body where one was expected"> [Reset Config] purgeShares returned error <CKError 0xc7b21f5d0: "Internal Error" (1/1000); "Received a didCompleteWithError without an error but no response body where one was expected">. Will try to continue. [Reset Config] :Purging shares of zones on HH2 failed with error: <CKError 0xc7b21f5d0: "Internal Error" (1/1000); "Received a didCompleteWithError without an error but no response body where one was expected">

Still no fix for this? Especially for NavigationSplitView?

You can get the current URL with this code: browser.tabs.getSelected(null, function(tab) {     document.getElementById("activetaburl").innerHTML = tab.url; });