Roon app on iphone and Pixel crashes every time tries to reach Nucleus core

Core Machine (Operating system/System info/Roon build number)
Roon version 1.7 build 710
roon os 1.0 build 227
Nucleus
os version firmware 1.0 build 227

TEXT GOES HERE

Audio Devices (Specify what device you’re using and its connection type - USB/HDMI/etc.)

TEXT GOES HERE

Description Of Issue

TEXT GOES HERE
Roon remote app crashes every time it attempts to connect to core. I have uninstalled app several times. I have also rebooted phones. This is an issue on both phones and only occurs when trying to connect to the core. If I turn off wifi or don’t give it network access it will not crash. Of course it will also not connect but this is something that happens when it is connecting with the core. There are no firewall issues and I also gave the Nucleus a static IP address to make sure that was not the problem. Note I’ve tried all methods seen on this board and elsewhere. Why is the app so unstable? The Roon software on the computer is pretty great and, as a new lifetime member, I’m excited to use it. But if I can’t easily control via my mobile devices it’s a bit useless for most of my listening situations. Please help… :slight_smile:

Network Details (Including networking gear model/manufacturer and if on WiFi/Ethernet)
Unifi dream machine through UniFi Switch 16 POE-150W.

Sorry for the trouble here, @kit_roane!

Can you try navigating to the Nucleus Web Administration Interface and reinstall the OS? Is there any change after doing so?

Will do. Give me two hours as I’m not there at the moment. Just so I understand, what does it sound like might be the problem?

So, unfortunately Roon seems to break connection before the OS can be reinstalled. I’ve tried three times.

Just wanted to add that my iOS and Android remotes were both working fine until I installed a Nucleus, after which I started getting exactly the same issues you describe. Even with the Nucleus now removed, the apps will not work, but only with the account associated with the nucleus. Any other account, and they connect fine.

That’s bad news. I’ve now tried on three different devices and the remote crashes on all three. I was hopeful that reinstalling the nucleus OS would fix it but can’t get it to do so without the procedure failing out in the end. I was super excited by this upgrade to my life so not jazzed by the stumbles I’m experiencing on the maiden voyage.

I pulled the logs and this appears to be what happens on the phone app.

error	10:49:52.398103 -0500	kernel	Sandbox: RoonMobile(5569) deny(2) file-test-existence /usr/bin/gdb
error	10:49:52.398159 -0500	kernel	Sandbox: RoonMobile(5569) deny(2) file-test-existence /bin/gdb
error	10:49:52.398213 -0500	kernel	Sandbox: RoonMobile(5569) deny(2) file-test-existence /sbin/gdb
error	10:49:52.398380 -0500	kernel	Sandbox: RoonMobile(5569) deny(2) file-test-existence /usr/bin/lldb
error	10:49:52.398444 -0500	kernel	Sandbox: RoonMobile(5569) deny(2) file-test-existence /bin/lldb
error	10:49:52.398500 -0500	kernel	Sandbox: RoonMobile(5569) deny(2) file-test-existence /sbin/lldb
error	10:49:52.398122 -0500	kernel	Sandbox: RoonMobile(5569) deny(2) file-test-existence /usr/bin/gdb
error	10:49:52.398178 -0500	kernel	Sandbox: RoonMobile(5569) deny(2) file-test-existence /bin/gdb
error	10:49:52.398232 -0500	kernel	Sandbox: RoonMobile(5569) deny(2) file-test-existence /sbin/gdb
error	10:49:52.398401 -0500	kernel	Sandbox: RoonMobile(5569) deny(2) file-test-existence /usr/bin/lldb
error	10:49:52.398463 -0500	kernel	Sandbox: RoonMobile(5569) deny(2) file-test-existence /bin/lldb
error	10:49:52.398519 -0500	kernel	Sandbox: RoonMobile(5569) deny(2) file-test-existence /sbin/lldb
error	10:49:52.829763 -0500	kernel	Sandbox: RoonMobile(5569) deny(2) file-test-existence /private/etc/.mdns_debug
error	10:49:52.829742 -0500	kernel	Sandbox: RoonMobile(5569) deny(2) file-test-existence /private/etc/.mdns_debug
error	10:49:53.286145 -0500	kernel	Sandbox: RoonMobile(5569) deny(1) network-outbound*:9003
error	10:49:53.286175 -0500	kernel	Sandbox: RoonMobile(5569) deny(1) network-outbound*:9003
error	10:52:01.984773 -0500	kernel	Sandbox: RoonMobile(5595) deny(2) file-test-existence /usr/bin/gdb
error	10:52:01.984930 -0500	kernel	Sandbox: RoonMobile(5595) deny(2) file-test-existence /bin/gdb
error	10:52:01.984994 -0500	kernel	Sandbox: RoonMobile(5595) deny(2) file-test-existence /sbin/gdb
error	10:52:01.985128 -0500	kernel	Sandbox: RoonMobile(5595) deny(2) file-test-existence /usr/bin/lldb
error	10:52:01.985181 -0500	kernel	Sandbox: RoonMobile(5595) deny(2) file-test-existence /bin/lldb
error	10:52:01.985230 -0500	kernel	Sandbox: RoonMobile(5595) deny(2) file-test-existence /sbin/lldb
error	10:52:01.984704 -0500	kernel	Sandbox: RoonMobile(5595) deny(2) file-test-existence /usr/bin/gdb
error	10:52:01.984909 -0500	kernel	Sandbox: RoonMobile(5595) deny(2) file-test-existence /bin/gdb
error	10:52:01.984972 -0500	kernel	Sandbox: RoonMobile(5595) deny(2) file-test-existence /sbin/gdb
error	10:52:01.985109 -0500	kernel	Sandbox: RoonMobile(5595) deny(2) file-test-existence /usr/bin/lldb
error	10:52:01.985160 -0500	kernel	Sandbox: RoonMobile(5595) deny(2) file-test-existence /bin/lldb
error	10:52:01.985212 -0500	kernel	Sandbox: RoonMobile(5595) deny(2) file-test-existence /sbin/lldb
error	10:52:02.222077 -0500	kernel	Sandbox: RoonMobile(5595) deny(2) file-test-existence /private/etc/.mdns_debug
error	10:52:02.222048 -0500	kernel	Sandbox: RoonMobile(5595) deny(2) file-test-existence /private/etc/.mdns_debug
error	10:52:02.826129 -0500	kernel	Sandbox: RoonMobile(5595) deny(1) network-outbound*:9003
error	10:52:02.826105 -0500	kernel	Sandbox: RoonMobile(5595) deny(1) network-outbound*:9003
error	10:52:03.663597 -0500	SpringBoard	-[_UIKeyboardArbiter runOperations:onHandler:]_block_invoke Failed to access <_UIKeyboardArbiterHandle: 0x283672d60; PID 5595: com.roon.mobile <com.apple.frontboard.systemappservices::sceneID%3Acom.roon.mobile-default>; hosting PIDs {(
)}; level 0.000000; active NO [wants NO]; suppression 0; iav 0.000000; on screen NO> remote service: Error Domain=NSCocoaErrorDomain Code=4097 "connection on mach service named com.apple.UIKit.KeyboardManagement.hosted from pid 5595" UserInfo={NSDebugDescription=connection on mach service named com.apple.UIKit.KeyboardManagement.hosted from pid 5595}
error	10:52:03.663558 -0500	SpringBoard	-[_UIKeyboardArbiter runOperations:onHandler:]_block_invoke Failed to access <_UIKeyboardArbiterHandle: 0x283672d60; PID 5595: com.roon.mobile <com.apple.frontboard.systemappservices::sceneID%3Acom.roon.mobile-default>; hosting PIDs {(
)}; level 0.000000; active NO [wants NO]; suppression 0; iav 0.000000; on screen NO> remote service: Error Domain=NSCocoaErrorDomain Code=4097 "connection on mach service named com.apple.UIKit.KeyboardManagement.hosted from pid 5595" UserInfo={NSDebugDescription=connection on mach service named com.apple.UIKit.KeyboardManagement.hosted from pid 5595}
error	10:52:18.997380 -0500	kernel	Sandbox: RoonMobile(5598) deny(2) file-test-existence /usr/bin/gdb
error	10:52:18.997447 -0500	kernel	Sandbox: RoonMobile(5598) deny(2) file-test-existence /bin/gdb
error	10:52:18.997679 -0500	kernel	Sandbox: RoonMobile(5598) deny(2) file-test-existence /sbin/gdb
error	10:52:18.997744 -0500	kernel	Sandbox: RoonMobile(5598) deny(2) file-test-existence /usr/bin/lldb
error	10:52:18.997897 -0500	kernel	Sandbox: RoonMobile(5598) deny(2) file-test-existence /bin/lldb
error	10:52:18.997958 -0500	kernel	Sandbox: RoonMobile(5598) deny(2) file-test-existence /sbin/lldb
error	10:52:18.997409 -0500	kernel	Sandbox: RoonMobile(5598) deny(2) file-test-existence /usr/bin/gdb
error	10:52:18.997469 -0500	kernel	Sandbox: RoonMobile(5598) deny(2) file-test-existence /bin/gdb
error	10:52:18.997699 -0500	kernel	Sandbox: RoonMobile(5598) deny(2) file-test-existence /sbin/gdb
error	10:52:18.997764 -0500	kernel	Sandbox: RoonMobile(5598) deny(2) file-test-existence /usr/bin/lldb
error	10:52:18.997922 -0500	kernel	Sandbox: RoonMobile(5598) deny(2) file-test-existence /bin/lldb
error	10:52:18.997980 -0500	kernel	Sandbox: RoonMobile(5598) deny(2) file-test-existence /sbin/lldb
error	10:52:19.254842 -0500	kernel	Sandbox: RoonMobile(5598) deny(2) file-test-existence /private/etc/.mdns_debug
error	10:52:19.254821 -0500	kernel	Sandbox: RoonMobile(5598) deny(2) file-test-existence /private/etc/.mdns_debug
error	10:52:19.651738 -0500	kernel	Sandbox: RoonMobile(5598) deny(1) network-outbound*:9003
error	10:52:19.651759 -0500	kernel	Sandbox: RoonMobile(5598) deny(1) network-outbound*:9003
error	10:52:24.608731 -0500	kernel	Sandbox: RoonMobile(5599) deny(2) file-test-existence /usr/bin/gdb
error	10:52:24.608805 -0500	kernel	Sandbox: RoonMobile(5599) deny(2) file-test-existence /bin/gdb
error	10:52:24.608928 -0500	kernel	Sandbox: RoonMobile(5599) deny(2) file-test-existence /sbin/gdb
error	10:52:24.608995 -0500	kernel	Sandbox: RoonMobile(5599) deny(2) file-test-existence /usr/bin/lldb
error	10:52:24.609052 -0500	kernel	Sandbox: RoonMobile(5599) deny(2) file-test-existence /bin/lldb
error	10:52:24.609124 -0500	kernel	Sandbox: RoonMobile(5599) deny(2) file-test-existence /sbin/lldb
error	10:52:24.608768 -0500	kernel	Sandbox: RoonMobile(5599) deny(2) file-test-existence /usr/bin/gdb
error	10:52:24.608825 -0500	kernel	Sandbox: RoonMobile(5599) deny(2) file-test-existence /bin/gdb
error	10:52:24.608957 -0500	kernel	Sandbox: RoonMobile(5599) deny(2) file-test-existence /sbin/gdb
error	10:52:24.609016 -0500	kernel	Sandbox: RoonMobile(5599) deny(2) file-test-existence /usr/bin/lldb
error	10:52:24.609089 -0500	kernel	Sandbox: RoonMobile(5599) deny(2) file-test-existence /bin/lldb
error	10:52:24.609144 -0500	kernel	Sandbox: RoonMobile(5599) deny(2) file-test-existence /sbin/lldb
error	10:52:24.755156 -0500	kernel	Sandbox: RoonMobile(5599) deny(2) file-test-existence /private/etc/.mdns_debug
error	10:52:24.755133 -0500	kernel	Sandbox: RoonMobile(5599) deny(2) file-test-existence /private/etc/.mdns_debug
error	10:52:25.287112 -0500	kernel	Sandbox: RoonMobile(5599) deny(1) network-outbound*:9003
error	10:52:25.287045 -0500	kernel	Sandbox: RoonMobile(5599) deny(1) network-outbound*:9003

@dylan
I forgot to add Dylan Caudill
Appreciate any support help.

Happy to reinstall the OS from file if that is the only option.

Note that it appears the Nucleus did finally reinstall the OS after multiple tries over several days from two different computers. No change in the app on iphone or google pixel however. Those both immediately crash at the moment the Nucleus is contacted.

Also the computer app crashes every time I click “discover,” no matter what computer I use. I also have issues where only one zone of two paired zones will play but each zone will play fine if not paired. This latter issue was not a problem initially but now fairly common. Love the product when it works, but very surprised how buggy the software is, given the cost, and the importance of the software to the usability of the product and the experience.

Roon app still unusable — crashing on start — and “discovery” still crashes desktop version. Anyone have an idea of what I might do? Also, is there a better channel to reach support? Struggling through this is getting old.

Hi Kit, Just for support’s info, is this a Windows or Apple PC?

Hi, Thanks for looking at the post.

It’s an Apple PC. After trying everything else I upgraded to Big Sur, reformatted my internal drive, reinstalled the Roon OS and reset the Roon Database and Settings. Nothing helped however. The mobile app still crashes immediately upon attempting to connect to the Core (also does this if I try to connect to a Roon on my computer). And the desktop Roon software also continues to crash immediately if I attempt to click “discover.” So I’m feeling a bit hopeless at this point.

On the OS server, the iPhone seems to be getting the connection refused:

12/27 20:57:11 Trace: [push] retrying connection in 13550ms
12/27 20:57:11 Info: [raatserver] [iPhone] connecting (attempt 1)
12/27 20:57:11 Info: [transport] destroyed zone iPhone was playing? False
12/27 20:57:11 Trace: [zone iPhone] Suspend
12/27 20:57:11 Info: [zone iPhone] Canceling Pending Sleep
12/27 20:57:11 Info: [zone iPhone] Canceling Pending Sleep
12/27 20:57:11 Warn: [raat_ll/client] [iPhone] failed to connect Connection refused 

========

On the rat server log, the discovery seems to be unreachable.

12/27 20:52:14 Info: [discovery] unicast socket is bound to [0.0.0.0:9003](http://0.0.0.0:9003/)
12/27 20:52:14 Trace: [raatmanager] starting server
12/27 20:52:14 Info: [jsonserver] listening on port 33427
12/27 20:52:14 Trace: [raatmanager] announcing
12/27 20:52:14 Warn: [discovery] got send failure: network is unreachable
12/27 20:52:14 Debug: [discovery] broadcast op is complete
12/27 20:52:19 Trace: [RAATServer] network reachability changed, refreshing discovery
12/27 20:52:19 Trace: [raatmanager] updating network interfaces
12/27 20:52:19 Trace: [discovery] stopping
12/27 20:52:19 Trace: closing multicast
12/27 20:52:19 Trace: [discovery] closing unicast send socket
12/27 20:52:19 Trace: [discovery] closing unicast recv socket
12/27 20:52:19 Trace: [discovery] starting

On the Apple PC that is trying to connect, do you have any firewalls running.

You are using managed switches which can cause some issues. try moving everything to an unmanaged switch see except below from Roon’s best network practices FAQ.

Managed Switches

Managed switches can be very robust, but they are often designed for professional installation, so in many cases the out-of-box configuration is not right. If your switch has a “flow control” setting, please make sure that it is enabled. Also, make sure that the switch is not performing any sort of throttling that might impact communication between cores, storage, remotes, and/or audio endpoints. Finally, ensure that the switch is configured to pass multicast and broadcast traffic. If in doubt about any of this, try temporarily replacing your managed switch with a “dumb” switch to see if things improve.

I made sure the router on the computer was off and connected the Nucleus directly to the Unifi Dream Machine router and enabled flow control but no change. If I connect to a dumb switch that is connected to the dream dream machine, won’t it still be controlled in the same way?

Are there port rules I need to look at or configure… maybe port forwarding? I’m not very adept at this stuff but can follow directions ok… :slight_smile:

If everything is attached to one switch, then all the traffic between devices stay on the one switch. As it is now, both the ports on the dream machine and the UniFi switch are managed.

BTW, I am just a fellow user trying to be helpful until support re-engages.

Thanks. I greatly appreciate you taking a look. I saw somewhere that I should possibly allow port forwarding but I don’t know what sorts of settings I’d need to plug in for all the fields.
I don’t have any rules for these ports as far as I can tell.

  • UDP port 9003
  • TCP ports 9100-9200

Well a quick test would be to turn your firewall off and see if things connect. If they do then you can turn it back on and begin worrying about fiddling with setting up port rules.

Thanks. The router doesn’t have a way to turn off unfortunately. I’d have to delete all the rules I think. I’ll mess with it some more and then wait for tech support to weigh in if I can’t get anywhere. You have been very helpful in helping me center on the likely problem area.

Can you find a USB key (memory stick) that has no important files on it? Don’t worry about bios setup but follow rest of guide create and reinstall off USB. Friend had some odd problems until he picked up a USB from me and reinstalled. He had music on it he had backed up elsewhere (Hint Hint) so just reinstalled and things started to behave. He did not loose his music but be safe. It is also important to update your firmware once up and running.


Thank you. I can try that if the Nucleus will allow it. I also tried port forwarding but may have done that wrong. It didn’t help unfortunately.