When saving a place as an .rbxlx file, the file will then break and be unable to be opened, showing this error.
To reproduce it, create a new place, and make a union. Then save the place as .rbxlx. It also happens when building via rojo, which is what initially led me to encounter this, so beta features should not be relevant.
My broken file is linked here.
testfile.rbxlx (80.5 KB)
I am also having this issue. I did not have this issue earlier today with the exact same .rbxlx file – so studio must have updated and caused something to break.
Having this issue too, with the same message and MD5. I’m using rojo, wally and roblox-ts in a nodejs environment with the rbxlx place I’m working on. I didn’t have this issue yesterday ~17h ago.
My project is not new - it was made multiple months ago.
I got the exact same thing. I am unsure why I am getting this. I have not previously had it with this file, it was just after I saved it.
Having the issue too this weekend… 
Opening the .rbxlx file and removing the NetAssetRef entries reported in the error, the file will open again in Studio. But saving adds it back.
There are 9000+ NetAssetRef entries. Do I remove all of these??
9000+ is a lot! I only had two. Here is what I would do: (a) Take a backup. (b) Start by removing all those NetAssetRef entries with yuZpQdnvvUBOTYh1jqZ2cA== value and try opening again. Or wait for the next update to come through 
.
This just happened to me lol. Legit spent an all nighter on the map and left it alone for 2 hours, I come back to not being able to open it again. Im not a scripter and I really dont wanna tamper with code like that cause I fear I might mess it up. Is there another alternative?
On rojo the issue happens when you save an .rbxm containing a union back into your project. More than unions might be affected.
Data Roblox is adding to the file is corrupted, and thus it stops working.
Use .rblx if your project supports it. It should unless you need to edit the xml directly.
It doesnt work when I change it to RBLX either. Am I doomed?
Did you export a still working place to .rblx? If you just renamed the file that won’t work.
I’ve followed Ribasu’s advice above in these steps:
Ctrl+F or Cmd+F to open the top-right find menu. Type in “<NetAsset”.Cmd + Forward Slash, or manually comment out with syntax <!-- ... -->.<SharedString\> in the screenshot below.The game, as they said, should be in working order until you save. After saving, the MD5 hash is reintroduced. To try and avoid this, save your project as an RBXL as OP said like so:File > Save To File As > Save as RBLX. Don’t save as RBXLX. I don’t think you need to remove the NetAsset tags if you are saving as an RBXL, as they should be removed by the conversion to a binary place file.
Now, if we save, the issue is gone, and we can re-open the project. We can also connect with Rojo.
Because Rojo modifies a place through the Rojo plugin and localhost server connection, and not with the RBXL(X) file directly, our edits should still work (to my knowledge), and we can continue our work.
I would keep hold of your backup for a few days as you work though, just in case other issues pop up!
Same problem started for me a few hours ago.
Hello everyone, thanks for the report. Really sorry about this.
In the short term we will turn off saving files with the NetAsset fields. This should kick in a couple hours, I will follow up when that is complete. Once this is done all new rbxlx files should save and load normally.
For those already impacted, the next Studio release will be able to load the impacted files again. If you don’t want to wait until then you can safely remove any NetAsset that have the value yuZpQdnvvUBOTYh1jqZ2cA==. It’s strongly suggested to keep a backup and if that doesn’t work they will load when the update is available.
The change to file saving should now be complete. If you’ve been using Studio you may need to restart for changes to take effect. Any newly saved files should now work as before.
I’ll be monitoring this thread so please reply if you are still running into issues.
Studio has been updated which should now let everyone open up all those files. You may need to restart for the changes to take effect.
Thanks everyone for you patience, and please follow up again if any issues are still occurring.
