Roon remote crashes on iPhone 11

Core Machine (Operating system/System info/Roon build number)
ROCK.

Network Details (Including networking gear model/manufacturer and if on WiFi/Ethernet)
Apple AirPort Extreme

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

Description Of Issue
Every 5-10 seconds Roon remote closes on iPhone 11. If I open it and don’t touch anything, it works fine. If I actively use it, like scroll, open albums, I’m getting crashes.

Reinstall, restart phone doesnt help. Helps to increase the time to 20-30 seconds a reset of cache and change memory size for photos.

iOS is 14.2, it looks like a some memory leakage. Very annoying!

On old iPad I don’t have this issue. So it’s not my network or ROCK.

Hi @Cooler,

I’ve just tried to activate diagnostics mode for you iPhone and what this should do is deliver a log report next time the app is able to communicate with our servers.

Can you please try to open the app and let it crash a few times? Then please let me know here so I can check for the log report’s arrival, thanks!

Hi @noris, yesterday i updated iOS on my phone and today roon was updated too. I cannot reproduce this issue any more. I will come back in a day or two with the results!

1 Like

@noris, exactly the same issue already for months. Across different iOS versions. Only if I completely reboot my iPhone, the problem stays away a little while. Seen many many more users reporting the same issue on the forum.

@noris, well, im getting this issue again. Just have got two crashes repeatedly a moment ago. Please check the report!

Hi @Cooler,

I haven’t seen any reports come in on my end, I just re-activated diagnostics mode.
Can you please use the Roon app on your iPhone and let me know here after? Thanks!

Hi @noris,
Actually I am using it mainly on iPhone 11, where it crashes and I have got near 10 crashes today, i also have iPhone 7, which I used before and maybe you activated logs on the old phone.

1 Like

Hi @Cooler,

Thanks for the update, I do see that your iPhone delivered a log set to our servers.

I’m going to ask QA to review the log, but it looks like you were getting quite a few networking issues in the logs that I noticed.

Have you by any chance tried to reproduce this issue on a different router yet?

We have had reports in the past that using Apple Airport routers can lead to issue, as mentioned in our Networking Best Practices Guide, perhaps this is impacting the iPhone traffic.

Hi @noris, yes, i tried different router, I switched to AVM fritz box 6490. Same behaviour! Just have got 2 crashes few minutes ago!

1 Like

Hi @Cooler,

Thanks for letting me know you tried a different router as well. Your Roon logs are still pending some feedback from QA at this time, but what can also help here would be seeing iOS Console logs, would you by any chance be able to reproduce the issue and retrieve these from your device?

Hi @noris here is a batch of errors few seconds before roon crashed on my phone:

error	10:37:12.432637+0100	SpringBoard	attention client lost event tag is not a number: (null)
error	10:37:15.032651+0100	backboardd	ImageQueueCollectable client message err=0x10000003
error	10:37:15.078875+0100	SpringBoard	HW kbd: Failed to set keyboard focus pid:0 ((null)) scene:(null)
error	10:37:15.084217+0100	runningboardd	RBSStateCapture remove item called for untracked item <RBProcessMonitorObserver| qos:0 qos:(null) configs:{
	}>
error	10:37:15.090760+0100	SpringBoard	Ignoring state for untracked process [application<com.roon.mobile>:16158]: <RBSProcessState| task:none debug:none>
error	10:37:15.166591+0100	SpringBoard	HW kbd: Failed to set keyboard focus pid:0 ((null)) scene:(null)
error	10:37:15.193557+0100	symptomsd	Suspicious packet count 106301 when bytes 630 for flow 1670453
error	10:37:15.193661+0100	symptomsd	Flow details for excess packet count <private>
error	10:37:15.193845+0100	symptomsd	Suspicious packet count 106301 when bytes 630 for flow 1670453
error	10:37:15.193880+0100	symptomsd	Flow details for excess packet count <private>
error	10:37:15.194021+0100	symptomsd	Suspicious packet count 106301 when bytes 630 for flow 1670453
error	10:37:15.195425+0100	symptomsd	Flow details for excess packet count <private>
error	10:37:15.195482+0100	symptomsd	Suspicious packet count 106301 when bytes 630 for flow 1670453
error	10:37:15.195954+0100	symptomsd	Flow details for excess packet count <private>
error	10:37:15.196073+0100	symptomsd	Suspicious packet count 106301 when bytes 630 for flow 1670453
error	10:37:15.196221+0100	symptomsd	Flow details for excess packet count <private>
error	10:37:15.196266+0100	symptomsd	Suspicious packet count 106301 when bytes 630 for flow 1670453
error	10:37:15.196660+0100	symptomsd	Flow details for excess packet count <private>
error	10:37:15.196717+0100	symptomsd	Suspicious packet count 106301 when bytes 630 for flow 1670453
error	10:37:15.196752+0100	symptomsd	Flow details for excess packet count <private>
error	10:37:15.197139+0100	symptomsd	Suspicious packet count 106301 when bytes 630 for flow 1670453
error	10:37:15.197254+0100	symptomsd	Flow details for excess packet count <private>
error	10:37:15.199991+0100	symptomsd	Suspicious packet count 212658 when bytes 630 for flow 1670450
error	10:37:15.200072+0100	symptomsd	Flow details for excess packet count <private>
error	10:37:15.200114+0100	symptomsd	Suspicious packet count 212658 when bytes 630 for flow 1670450
error	10:37:15.200149+0100	symptomsd	Flow details for excess packet count <private>
error	10:37:15.200285+0100	symptomsd	Suspicious packet count 212658 when bytes 630 for flow 1670450
error	10:37:15.200598+0100	symptomsd	Flow details for excess packet count <private>
error	10:37:15.200756+0100	symptomsd	Suspicious packet count 212658 when bytes 630 for flow 1670450
error	10:37:15.200851+0100	symptomsd	Flow details for excess packet count <private>
error	10:37:15.201062+0100	symptomsd	Suspicious packet count 212658 when bytes 630 for flow 1670450
error	10:37:15.201101+0100	symptomsd	Flow details for excess packet count <private>
error	10:37:15.201201+0100	symptomsd	Suspicious packet count 212658 when bytes 630 for flow 1670450
error	10:37:15.201247+0100	symptomsd	Flow details for excess packet count <private>
error	10:37:15.201289+0100	symptomsd	Suspicious packet count 212658 when bytes 630 for flow 1670450
error	10:37:15.201379+0100	symptomsd	Flow details for excess packet count <private>
error	10:37:15.201782+0100	symptomsd	Suspicious packet count 212658 when bytes 630 for flow 1670450
error	10:37:15.202260+0100	symptomsd	Flow details for excess packet count <private>
error	10:37:15.203660+0100	symptomsd	Ignoring UDP source 0x14de674a0, cannot infer interface type from snapshot RoonMobile UDP4 flow id 1670474 (close) so pkts rx 0 tx 0, bytes 0 0 cell 0 0 wifi 0 0 wired 0 0 deltas 0 0 0 0 0 0 0 0
error	10:37:15.203739+0100	symptomsd	Don't have a tracker for this flow's interface type: 0
error	10:37:15.203820+0100	symptomsd	Don't have a tracker for this flow's interface type: 0
error	10:37:15.204387+0100	appstored	tcp_input [C8.1:3] flags=[R] seq=3301828360, ack=0, win=0 state=LAST_ACK rcv_nxt=3301828360, snd_una=2041657259
error	10:37:15.204461+0100	appstored	tcp_input [C8.1:3] flags=[R] seq=3301828360, ack=0, win=0 state=CLOSED rcv_nxt=3301828360, snd_una=2041657259
error	10:37:15.219608+0100	symptomsd	Ignoring UDP source 0x14e9912c0, cannot infer interface type from snapshot RoonMobile UDP4 flow id 1670472 (close) so pkts rx 0 tx 0, bytes 0 0 cell 0 0 wifi 0 0 wired 0 0 deltas 0 0 0 0 0 0 0 0
error	10:37:15.219651+0100	symptomsd	Don't have a tracker for this flow's interface type: 0
error	10:37:15.219718+0100	symptomsd	Don't have a tracker for this flow's interface type: 0
error	10:37:18.516777+0100	CommCenter	Send request failed IDS Ack with device id: (null) and transaction id: 39111
1 Like

Thanks for the log @Cooler, this log does look helpful, let me get this over to the team!

One other theory regarding this issue could be that background apps on the iOS device are causing Roon to run out of RAM.

If have any background iOS apps running and force-quit the iOS apps (so that only Roon is running), does that help with the issue?

Thanks again for the logs and hope Happy Holidays!

Hi @noris, i closed all other apps and have got roon crash in 5 seconds. ;(

Happy New Year :balloon:

1 Like