Sorry to be a pain, but it's hard for me to tell from that log which messages are from the web app vs the apple tv app (since they generate the same types of requests) - could you close any browser tabs that have the web app open, restart the recording service (to reset the logs), then try starting the apple tv app again, then zip and attach the logs again? This way I'll know the nrecord.log/web.log messages only relate to the apple tv attempt.
Quote:2018-09-09 15:12:14.009 [DEBUG][46] client_ip: 192.168.1.8
2018-09-09 15:12:14.009 [DEBUG][46] user_agent: MrMC/3.6-2 (AppleTV; CPU OS 11_4_1 like Mac OS X)MrMC HW_AppleTV/6.2 App_Bitness/64 Version/3.6-2-Git:2018-04-25-4528cc1-dirty
Can you try closing any browsers around the lan that might be looking at it, and close this MrMC build of Kodi, and restart the recording service, and just try the app, then zip and post the logs again?
Yep - logs look good this time. There isn't an obvious reason in there, but I can see it has gone at least some way through the initial connection.
Can you zip and attach your npvr.db3 file? I'll try loading your channels/recordings etc up here, to see if I can reproduce the problem with your data.
Annoyingly there was no easy fix I could do on the PC side. I've just submitted an updated build of the application to Apple. I'm checking to see if there is anyway to get an expedited review done, otherwise it'll probably take a day or so to make it through their normal review process.
It related to an issue with channel group selection, and people that had the earlier beta wouldn't have the issue with the final build (because their device would have the channel group set from the earlier build). Kicking myself...but these things happen occasionally.