Corrupted RBXLX file caused by SerializedEmulatedPolicyInfo property

[Anaminus]

Issue Type: Other
Impact: High
Frequency: Constantly
Date First Experienced: 2021-04-17 09:04:00 (+00:00)
Date Last Experienced: 2021-04-17 10:04:00 (+00:00)

Reproduction Steps:

1. Open Classic Baseplate template (or uploaded sample).
2. Save as a local file with rbxlx extension.
3. Close the place.
4. Open the file.

Original: Baseplate.rbxl (21.0 KB)
Corrupted: Baseplate.rbxlx (27.2 KB)

Expected Behavior:
File opens normally without errors.

Actual Behavior:
A dialog appears, indicating an error while opening the file:

Could not open the place ".../Baseplate.rbxlx" with exception: "Unexpected end of file while reading bytes".
Incident ID: 5590581526878548156
If you continue to encounter this error, please report it on the Developer Forum

Workaround:

1. Edit the XML file manually.
2. Search for the SerializedEmulatedPolicyInfo property, which is under the PlayerEmulatorService class.
3. Remove the content of this tag.

[PeZsmistic]

Should Roblox even be serializing the player emulator?
For accessibility, here is the broken piece of XML.

	<Item class="PlayerEmulatorService" referent="RBX98A7CF203A8241ACBC11D5E1148D8AD8">
		<Properties>
			<BinaryString name="AttributesSerialize"></BinaryString>
			<string name="EmulatedCountryCode">US</string>
			<string name="EmulatedGameLocale"></string>
			<string name="Name">PlayerEmulatorService</string>
			<bool name="PlayerEmulationEnabled">false</bool>
			<string name="SerializedEmulatedPolicyInfo">&#4;&#0;&#0;&#0;&#29;&#0;&#0;&#0;AllowedExternalLinkReferences&#7;&#0;&#0;&#0;&#0;&#28;&#0;&#0;&#0;ArePaidRandomItemsRestricted&#3;&#1;&#24;&#0;&#0;&#0;IsPaidItemTradingAllowed&#3;&#1;&#24;&#0;&#0;&#0;IsSubjectToChinaPolicies&#3;&#1;</string>
			<int64 name="SourceAssetId">-1</int64>
			<BinaryString name="Tags"></BinaryString>
		</Properties>
	</Item>

[OuterspaceNemo (Nemooo)]

Thanks for the report! A fix is in the works and we’ll follow up with updates.

[OuterspaceNemo (Nemooo)]

This issue should now be resolved!