Roon app on new iPad stuck on 'Searching for Core' (ref#1R302T)

Hi! What’s not quite right with Roon?

· None of the above quite fits

None of the above quite fits

· App interface looks or behaves oddly

Tell us what's going on

· I have Roon operating on multiple devices successfully except a one particular (newish iPad). Worked initially. Now it searches endlessly. Yet when I tap “configure OS …,” Roon can see the device but the app never launches. It is on the same network and the Nucleus Titan is operational.

Tell us about your home network

· Deco 7 Pro BE63 Tri band

Hi @Chris_Causey,

Thank you for your post. Are you able to share a screenshot of what you see on the tablet?

More recent iOS updates can prevent Roon from automatically discovering the server due to a rotating private WiFi address. In your iOS Settings on the iPad, navigate to the WiFi Details dialog page for your home network. Ensure Private WiFi is set to “fixed,” not rotating.

As a test, make sure Roon on the iPad is using the same access point or mesh node serving the Nucleus via ethernet. We want to minimize device discovery announcements to a single hop to reduce the number of variables in play.

We’ll watch for your reply and gather logs in the meantime.

Thank you!

Thanks Connor. WiFi is set to fixed and I’m on the same node. No difference. Not sure how to attach the screen shot but I’m stuck at “Looking for your Roon Server.” When I go to “configure Roon OS devices” below, it shows the Nucleus Titan and the correct address.

for future reference:

Hello @Chris_Causey,

We checked the logs from your Nucleus Titan, and the iPad did connect to it on the morning of October 3, briefly, three times. We have not seen it connect since. Is the iPad working now, or is it still stuck on “Looking for your Roon Server” when you open Roon?

If it is still stuck, please open the iPad’s Settings app, select Roon, and make sure Local Network is turned on: https://help.roonlabs.com/portal/en/kb/articles/ios-permissions

If that was already on, please toggle it off and back on again.