Hi guys, I know you're already cautioning people away from upgrading to 2018.3.0f2, but you're citing issues with Package Manager as the reason. We are not managing the utilities through Package Manager, and my team discovered the showstopper-level issue described in the title a few days ago when we upgraded to 2018.3.0f2. There appears to be an issue logged with Unity about this already. It mentions Quest, but it applies to Go as well, and appears to be directly related to 2018.3.x.
Are you aware of this? It's kind of an emergency and needs to be fixed as soon as possible.
