We use cookies to improve your site experience and analyze website traffic. Click Accept to agree to our website's cookie use as described in our Cookie Policy . Click Preferences to customize your cookie settings.
Hello! In my Unity VR app, I recently got a security vulnerability test
failure: "Unsafe HostnameVerifier Defined". In previous security tests,
this did not happen and I haven't changed any networking related code,
but now I am getting this failure. ...
I integrated the Firebase Unity SDK v8.7.0 for Firebase Storage and
confirmed it works, but after setting it up per their documentation
(https://firebase.google.com/docs/storage/unity/start) I got a security
vulnerability failure, "GCP API Keys Expos...
In code, how can I check if the Guardian has been completely turned off
in developer settings? I need to check for this so that I can run some
additional code if the guardian is completely disabled.
I uploaded a new build to Oculus Quest App Lab (alpha release channel).
Usually, automated testing runs immediately and finishes within a few
minutes. Then, the app updates for everyone. However, I am experiencing
an issue where no tests are initiate...
I am developing an Oculus Quest app for release on the App Lab.
Previously, I was able to get the player's user name just fine via
Oculus.Platform.Users.GetLoggedInUser().OnComplete(getLoggedInUserComplete);
but recently that stopped working and now ...
I fixed the issue. My solution was to remove the Amplitude Unity SDK
(along with the okhttp dependency that was likely causing the issue). I
then re-implemented Amplitude analytics via their HTTP API, using the
UnityWebRequest built-in functionality....
I haven't fixed the issue yet, but I was able to determine that the
Amplitude Unity SDK is indeed causing the problem. I copied my project,
and completely removed the Firebase SDK, built, and uploaded to Oculus -
still got the security vulnerability ...
Upgrading okhttp from version 4.2.2 to 4.9.3 also did not fix the issue.
Curious, as the release notes for okhttp v4.9.2 do mention a fix related
to HostnameVerifier:
