Connection issue on the Quest
Hello, I have an app that connects fine in the Editor but doesn't connect when running on the Meta Quest. I get the following error:
Realtime (native): BidirectionalClient: Connection Error: Unable to connect to normcore-matcher.normcore.io on port 3000, error: No address associated with hostname
Normal.Realtime.Native.Plugin:Log(LogLevel, String)
Normal.Realtime.Native.Plugin:MatcherTick(IntPtr)
Normal.Realtime.<ConnectToServer_Coroutine>d__100:MoveNext()
UnityEngine.SetupCoroutine:InvokeMoveNext(IEnumerator, IntPtr)
Normal.Realtime.CoroutineContext:_StartWithCoroutineRunner(CoroutineRunner)
Normal.Realtime.CoroutineRunner:RunCoroutine(CoroutineContext)
Normal.Realtime.Room:ConnectToServer(String, ConnectOptions)
Normal.Realtime.Room:Connect(String, ConnectOptions)
Normal.Realtime.Realtime:Connect(String, ConnectOptions)
Normal.Realtime.Realtime:Start()
Any idea or hint where that may come from? My Quest device is already connected to the internet
Thank you for your help!
9 Replies
Hi @Wadidi. I'm kapa.ai, your friendly support bot. I will try to answer your question by searching through the knowledge base. :wave:
----------------------
Hmm, I don't know enough to give you a confident answer yet. However, based on the error message you provided, it seems like there might be an issue with the connection to the Normcore server.
In the Normcore documentation, it's mentioned that to connect to a room server, you need to call
Connect() along with the room name and app key. All clients that connect to the same room name with the same app key will connect to the same room server. If you're working with Normcore Private, you need to set the matcherURL parameter to your Normcore Private matcher URL.
Please double-check these settings in your code. If the issue persists, I recommend reaching out to the Normcore support or checking their documentation (https://normcore.io/documentation/room/room#connecting-to-a-room-server) for more information.
----------------------
Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:
----------------------<@268827424488292354> kapa.ai is still learning and improving, please let us know how it did by reacting below
This error means the DNS lookup has failed. Here's a few reasons users have seen this in the past despite being connected to a network:
* The app doesn't have internet permissions
* The DNS servers are not valid on the device
* A firewall is blocking the request
You can test if it's the firewall by connecting through a mobile hotspot as described by Robi: https://discord.com/channels/393839515074297858/677646675560366141/948881332170276874
Thank you for your support! I have more information after some debugging. It looks like the issue came from the fact that the app could not reach the internet. That is due to the OpenXR plugin https://forum.unity.com/threads/unity-removes-android-permission-internet-in-the-build-apk-after-build-is-completed.1466654/
I had to:
- Toggle off the "Force Remove Internet" boolean - see https://forum.unity.com/threads/unity-removes-android-permission-internet-in-the-build-apk-after-build-is-completed.1466654/#post-9185654
- Force the internet access in the player settings https://forum.unity.com/threads/unity-removes-android-permission-internet-in-the-build-apk-after-build-is-completed.1466654/#post-9837141
Now it connects on the Quest ✨
Unity Forum
Resolved - Unity removes "android.permission.INTERNET" in the build...
Hi, I am building a TCP Client VR application that is being deployed to the Meta Quest Pro. Initially I was getting a SocketException of Access Denied...
Thanks for sharing! This was definitely trickier than expected to configure on the Unity side.
thanks for taking the time to look into this, i had the same problem
@NormalMark will you write up a Linear issue to make a script that fixes this automatically? If this is common Normcore should def detect and flip these settings imo
the force remove internet turns on by its own after restarting the editor btw
Thank you so much for sharing your solution to this problem! I just flipped those two checkboxes and it instantly started working.