Hi there! Thanks for reaching out and sorry to hear you’re having trouble.
It sounds like this issue may have been introduced sometime between the version you originally used to build your app and 6000.0.58f2. In the short term, you can use the patching tool to patch any build of your app, so you can keep using whatever 6000.0.x version you had been using previously. If you need to automate this, you can use a build postprocessor to run the UnityApplicationPatcherCLI program (included with the patcher) to patch every build coming out of Unity.
Longer term, you may still want to build and ship with the latest 6000.0 Editor. Are you able to submit a bug report with a project that replicates the issue? Does it happen with a clean, fresh project built with 6000.0.58f2? We will also investigate on our end.
Thanks again for reaching out, and good luck!