ah sorry, the issue might be on my end then.
It seems the plugin code in your session is
Dd0tit should beabcd
That code is randomly picked when creating the project via projucer->open example->AudioPluginDemo, but it might well have changed when I went to juce8 and reexported a project!
I’ll double check things more carefully and report back (probably not before a couple of days though)
Oh yes of course you’re right. It’s me who changed it to abcd at some point locally when I was testing some details about how Reaper was encoding the plugin code inside the VST2 plugin state. Fairly sure that’s all it was though so hopefully with that resolved I think the patch should work 
@lalala we’ve pushed an update to the VST3 SDK on develop, this should fix the outstanding bug you reported.
Thanks again for reporting.
I have used the develop build from 28.10.2024 and updated two of our plugins.
Loading plugin states from sessions saved with older JUCE versions did not work anymore. The following method returned null in that case:
getXmlFromBinary (data, sizeInBytes)
I tested this with two different plugins. It looks like this isn’t backward compatible. The problem showed up on all operating systems with the VST3. Tested in Reaper.
It looks like going back to the stable 8.0.1 release fixes the problem.
Is this related to the vst2 / vst3 state loading change?
It looks like this also solves the issue with the state. I’ll make some more tests.
