UnityWebRequest Not Working on Quest 3 - "cannot resolve destination host" error

I apologize for not mentioning it earlier, but I'm using Unity version 2022.3.11.f1 for my project.

I have run into this as well... quite frustrating because I have found several topics about this and none seem to resolve it. It seems to be a problem for 2022 in general, maybe even 2021 as well. I loaded an old project from before WWW got replaced with UnityWebRequest and back then it worked for me in older projects, I can still load that project and download or load stuff from the web.

Found this thread where someone might have found a workaround, but it has not worked for me so far:
https://discussions.unity.com/t/web-requests-fail-on-android-meta-quest-2-only/287322

I think I managed to find a thread that has a reason why this problem exists and a possible solution. Downgrading the OpenXR plugin to 1.7 or add Internet permission in a custom android manifest.

https://forum.unity.com/threads/unity-removes-android-permission-internet-in-the-build-apk-after-build-is-completed.1466654/

Thank you so much, Cain_Bloodbane!

After going through the discussion in the link you provided, I managed to resolve the issue. For those who might face a similar problem in the future, here's what I did:

1. I did not downgrade the OpenXR plugin.
2. I did not directly modify the android manifest (I believe the settings made the necessary changes during the build).
3. I changed "Allow downloads over HTTP" to "Always allow" under Project Settings > Player > Configuration.
4. I set "Internet Access" to "Require" under Project Settings > Player > Configuration.
5. In Project Settings > XR Plug-in Management > OpenXR, under OpenXR Feature Groups > Meta Quest Support, I pressed the gear icon on the right and in the pop-up window, I unchecked "Force Remove Internet ~".

After making these adjustments and building, everything worked as expected.

Again, thank you for pointing me in the right direction!

Finally got it working, this time the only thing I did was flip the setting to force disable Internet in OpenXR under Meta Quest Support". It did activate that setting once, but I disabled it again. I think the problem with Gltfast was maybe that I needed to generate "shader includes". Edit -> Rendering -> "Generate Shader Includes"
But I guess it might also just be that I needed to compile it a second time.

I will experiment some more. Very strange how many problems it caused me earlier, but I guess maybe some of the solutions I implemented ended up causing more problems instead of helping.

But now hopefully I can begin to see if I can use Unity Mesh Simplifier to help me create LODs at runtime on the Quest, so I can make it possible for users to control the quality of each mesh they import.

So I did even more testing and this is becoming more and more frustrating.

It seems both the "force disable Internet" and the shader issue are both problems that decide to come back now and again. So every time I make a change, I should expecting having to build and run the app twice, because the first time it always fail... and then if it works the second time, then the "force disable Internet" option might have become enabled again at some point.

Oh well, at least now I can get a working build, even if it ends up taking 3 or more attempts every time. Because once I enable Internet again, the shader problem might return, and then after that... the Internet problem might return. The bug that keeps on bugging.

Quick update to anyone coming across this, to resolve this successfully, you have to:
* Edit your project manifest and update the OpenXR version to "1.9.1" Manually (doesn't show up in Unity yet)
* Return to Unity and let it update
* Check your OpenXR settings, likely they will need to be refreshed (internal thing)
* Select the OpenXR tab under the XR Settings (Player Settings window)
* With the Android tab selected, find the "Meta Quest Support" option and click the COG to the right of it
* DESELECT the option to "Force Remove Internet"
Your projects when deployed to the quests will now work as they should and have internet access again.

I maybe can understand why this option was added for "some" projects, but to add it, NOT document it and FORCE it ON by default is beyond me (since in C# and C++, a boolean is FALSE by default, so they would have had to intentionally set it), one can only hope this is a small blunder when they were testing it.

But on with the show, there is one day of pulling hair out I won't get back.