Unable to edit/save metdata template when custom metadata view.xml present

Adobe Bridge CC 2021 11.0.0.83 (also Bridge CC2019 and CC 2018)
macOS 11.1 (also macOS 10.14 and 10.15)

I posted this over at the Adobe Bridge Feedback site but repeating here in case anyone has a solution.

If I add a custom Metadata Extension view.xml that contains any of the following three Dublin Core properties I am unable to edit and save a metadata template.

name="dc:title"
name="dc:description"
name="dc:creator"

(other Dublin Core properties such as name="dc:rights" and name="dc:subject" work as expected and do not thrown the error when editing/saving a template)

If data is already present in any of these when editing the template from the Tools - Edit Metadata Template menu an error dialog pops up reporting "The operation could not be completed" for the following actions:

1. Editing the existing data and coming out of the property field (tab or clicking)
2. Adding/editing data to any other property fields and clicking Save

This error is reproducable using the Sample Extension provided as part of the Adobe XMP SDK.

It seems to be View related as I can clear down any addtional schema definitions from the SDK example and leave only the custom View XML code containing these properties in the View.xml file. For example:

<?xml version="1.0" encoding="UTF-8"?>

<views xmlns="http://ns.adobe.com/metadata/ui/1.0/"> 

	<view
	
		xmlns:dc="http://purl.org/dc/elements/1.1/" 
		xmlns:exif="http://ns.adobe.com/exif/1.0/"
		xmlns:photoshop="http://ns.adobe.com/photoshop/1.0/"
		name="sample.usingDefaultSchemas"
		label="$$$/sampleSchema/Property/usingDefaultSchemaViewLabel=Default Schemas"
		description="$$$/sampleSchema/Property/usingDefaultSchemaViewDescription=This view demonstrates how properties of default schemas be used">
		
		<!-- Three below will cause error -->		
		<property name="dc:title" />
		<property name="dc:description" />
		<property name="dc:creator" />
		
		<!-- These will work -->
		<property name="dc:rights" />
		<property name="dc:subject" />
						
	</view>		
	
</views>

Conversely I can leave custom schema properties in the View.xml, removing the problematic ones and everything works as expected.

Given the example provided by Adobe has one of these fields specifically shown (name="dc:creator") as a custom view example I feel this should work as documented. 

Anyone else seen this? Bug for sure?

Thanks 🙂