Unity announced a change in mid-2019, forum post 1, forum post 2 , but as it looks they didn’t think about all the Plugins/SDKs and what a mess will it cause. As announced, change was introduced in Unity 2019.3.0 on 27.01.2020.
Now, you would expect a huge announcement specially made for Plugin/SDK providers so they could adjust to this but that never happened. Even a whole year later there is no public statement that would notify all Plugin/SDKs providers to make changes so this error would go away. Not even a single official response on this breaking issue on this forum, very disappointing, like it is thrown under the rug. Plugins that still didn’t adjust to this change (many still don’t know about this) will crash the app if you are not using a workaround, but a workaround by some reports above causes another crash.
Probably we users (in fact beta testers, QA) should notify Plugin/SDK providers, as we also need to find and report breaking bugs that are dragged from version to version over several months until we report them. Unity has catastrophic QA, I’m pretty sure that many things are thrown under the rug until someone makes a detailed bug report.
Correct me if any of my statements are wrong.