There could be some issues with the Auth since it changes how JRemote connects. For example the disabled auth is a newish setting that JRemote may not be responding properly to. If you could temporarily set that to everyone and test that it could be helpful. Thanks!
Thanks Bob. I've done what you suggest and tested both ways. The crashing occurs when ro_auth=everyone, as well as with ro_auth=disabled. I'm currently testing with ro_auth=password but need some more time with that.
It's important to note that once the crashing starts, it happens 100% of the time, until I make a change to the auth settings. Merely restarting the server has no effect. If I make a change to auth settings, JRemote immediately reconnects on the next try.
So it goes like this:
Crash, crash, crash
Restart server
Crash crash crash.
Restart server
Crash crash crash
Change ro auth from disabled to everyone and restart server
Launch JRemote, Connects
(Eventually, app is removed from memory by IOS)
Relaunch JRemote, crash crash crash
Crash crash crash...
Or like this:
Crash, crash, crash
Restart server
Crash crash crash.
Restart server
Crash crash crash
Change ro auth from everyone to disabled and restart server
Then immediately change ro auth from disabled back to everyone and restart server
Launch JRemote, Connects
(Eventually, app is removed from memory by IOS)
Relaunch JRemote, crash crash crash
Crash crash crash...
So there is something about CHANGING the server auth settings, even if the changes are reverted, that triggers different behavior. Merely restarting the server, without changing the auth settings, does not affect the issue.