Beta 4 problems?

Never mind.. we got you covered: https://github.com/iBaa/PlexConnect/commit/5d27a67f986950965b7eb28840aab4332e38f6fa

Awesome work!!!!!

Afternoon,

Tired current shipping firmware (5.3?) with Trailers app and using the mod mentioned above WSJ Live and both work as expected.

Upgraded to 5.4 beta 4. System is setup clean, and Trailers app and WSJ app both reported " is currently unavailable, please try again later" where is either Trailers or WSJ Live. Netflix seems to connect, as do a few other things, so it seems Trailers and WSJ Live are both broken in beta 4. I did try changing DNS to see if PlexConnect would work with Trailers in this state, and it did not, which I believe we knew.

I'll re-test when the next beta appears and report back.

So are we out of luck in getting plexconnect to work with iOS 7 beta 4 on ATV? or is there a workaround?

Markuswarren, it is is not clear from your post if both the WSJ app and the Trailer app work for you on beta 4 before you change the DNS of the ATV. Could you please clarify that point. Thanks.

Markuswarren, it is is not clear from your post if both the WSJ app and the Trailer app work for you on beta 4 before you change the DNS of the ATV. Could you please clarify that point. Thanks.

To clarify:

The error I was seeing was BEFORE I changed DNS to point to the machine running PlexConnect. ie; it was a clean install of beta 4.

So are we out of luck in getting plexconnect to work with iOS 7 beta 4 on ATV? or is there a workaround?

From what I have seen, on screen and in the log below, Trailers and WSJ are not connecting to anything, even with a stock setup. I'd take a guess to say they are not even trying to connect to their respective servers, which could be why PlexConnect does not work, as if no traffic is sent from the apps, so there is no redirect getting to PlexConnect.

I do have the following from terminal, not sure if it is any use. I'm trying to remember exactly when I had the ATV running beta 4, think it was between the 10:56 and 13:35 time range. Prior to that I know I was on shipping firmware, and after that time I was back to shipping firmware and actually watching something via PlexConnect. Hope it might be of use. If there is some other log somewhere that might help, point me at it and I'll see what I can pull out.

Log from Terminal:

10:21:41 DNSServer: DNS request received!
10:21:41 DNSServer: Source: ('10.0.100.245', 57132)
10:21:41 DNSServer: Domain: api-global-1848156627.us-west-9.elb.amazonaws.com
10:21:41 DNSServer: ***forward request
10:21:41 DNSServer: -> DNS response from higher level
10:56:38 DNSServer: DNS request received!
10:56:38 DNSServer: Source: ('10.0.100.245', 54068)
10:56:38 DNSServer: Domain: ios-nccp-1848156627.us-west-9.elb.amazonaws.com
10:56:38 DNSServer: ***forward request
10:56:38 DNSServer: -> DNS response from higher level
11:21:42 DNSServer: DNS request received!
11:21:42 DNSServer: Source: ('10.0.100.245', 60815)
11:21:42 DNSServer: Domain: api-global-1848156627.us-west-9.elb.amazonaws.com
11:21:42 DNSServer: ***forward request
11:21:42 DNSServer: -> DNS response from higher level
13:35:26 DNSServer: DNS request received!
13:35:26 DNSServer: Source: ('10.0.100.245', 63912)
13:35:26 DNSServer: Domain: mesu.apple.com
13:35:26 DNSServer: ***forward request
13:35:26 DNSServer: -> DNS response from higher level
13:35:36 DNSServer: DNS request received!
13:35:36 DNSServer: Source: ('10.0.100.245', 64294)
13:35:36 DNSServer: Domain: ax.init.itunes.apple.com
13:35:36 DNSServer: ***forward request
13:35:36 DNSServer: -> DNS response from higher level
13:35:36 DNSServer: DNS request received!
13:35:36 DNSServer: Source: ('10.0.100.245', 59852)
13:35:36 DNSServer: Domain: itunes.apple.com
13:35:36 DNSServer: ***forward request
13:35:36 DNSServer: -> DNS response from higher level
13:35:39 DNSServer: DNS request received!
13:35:39 DNSServer: Source: ('10.0.100.245', 62641)
13:35:39 DNSServer: Domain: configuration.apple.com
13:35:39 DNSServer: ***forward request
13:35:39 DNSServer: -> DNS response from higher level
13:35:40 DNSServer: DNS request received!
13:35:40 DNSServer: Source: ('10.0.100.245', 49868)
13:35:40 DNSServer: Domain: a5.mzstatic.com
13:35:40 DNSServer: ***forward request
13:35:40 DNSServer: -> DNS response from higher level
13:35:41 DNSServer: DNS request received!
13:35:41 DNSServer: Source: ('10.0.100.245', 63804)
13:35:41 DNSServer: Domain: a2.mzstatic.com
13:35:41 DNSServer: ***forward request
13:35:41 DNSServer: -> DNS response from higher level
13:35:41 DNSServer: DNS request received!
13:35:41 DNSServer: Source: ('10.0.100.245', 64083)
13:35:41 DNSServer: Domain: a1.mzstatic.com
13:35:41 DNSServer: ***forward request
13:35:41 DNSServer: -> DNS response from higher level
13:35:41 DNSServer: DNS request received!
13:35:41 DNSServer: Source: ('10.0.100.245', 61726)
13:35:41 DNSServer: Domain: a3.mzstatic.com
13:35:41 DNSServer: ***forward request
13:35:41 DNSServer: -> DNS response from higher level
13:35:47 DNSServer: DNS request received!
13:35:47 DNSServer: Source: ('10.0.100.245', 56427)
13:35:47 DNSServer: Domain: init-p01st.push.apple.com
13:35:47 DNSServer: ***forward request
13:35:47 DNSServer: -> DNS response from higher level
13:35:48 DNSServer: DNS request received!
13:35:48 DNSServer: Source: ('10.0.100.245', 61806)
13:35:48 DNSServer: Domain: 26-courier.push.apple.com
13:35:48 DNSServer: ***forward request
13:35:48 DNSServer: -> DNS response from higher level
13:35:48 DNSServer: DNS request received!
13:35:48 DNSServer: Source: ('10.0.100.245', 60813)
13:35:48 DNSServer: Domain: a4.mzstatic.com
13:35:48 DNSServer: ***forward request
13:35:48 DNSServer: -> DNS response from higher level
13:36:21 DNSServer: DNS request received!
13:36:21 DNSServer: Source: ('10.0.100.245', 61332)
13:36:21 DNSServer: Domain: data.iana.org
13:36:21 DNSServer: ***forward request
13:36:21 DNSServer: -> DNS response from higher level
13:36:38 DNSServer: DNS request received!
13:36:38 DNSServer: Source: ('10.0.100.245', 55735)
13:36:38 DNSServer: Domain: trailers.apple.com
13:36:38 DNSServer: ***intercept request

I suggest waiting until the apps work normally but not with Plexconnect before too much effort is put into diagnoses.

I agree. When the next beta appears, I will try it, if the trailer / WSJ Live apps work normally, I'll then give PlexConnect a go.

Great work—thanks.

Yup, WSJ Live doesn't work, either, so I think this is a beta 4 bug and not a PlexConnect-specific issue.

(I filed it with Apple.)

If you are on the latest beta does anyone here know how to go back to the normal version on ATV3? Cause itunes doesnt seem to want to downgrade. 

Funny that even when you have the 5.2 IPSW, you cant flash it back from the beta :(

Does anyone have any idea how to get the ATV3 back to 5.2?

I don’t know if it is possible but it should be since apple is still signing that firmware. But this is the reason you always should back up your shsh blobs with tinyumbrella (firmware umbrella). But as i stated earlier apple still signs lates non beta fw so just keep trying. Try with different os and itunes version. If you have acess to it that is.

If it is similar to other iOS devices, then the firmware / os version is cryptographically signed. This signature is checked when you restore / upgrade your device. When a new OS version comes out, there is a small period of time where Apple still signs the previous version of the os, and then it stops signing it. When that happens, you cannot install that version of the OS, only the new one. This is where keeping a copy of your "blobs" comes into play, as, if I'm right, you basically use TinyUmbrella (or something similar) to 'pretend' to be the Apple authentication server, and it checks the OS file against this server, checks your blobs, confirms they are allowed and thus allows you to install the older OS version.

At this moment in time, as v5.4 is in beta, Apple does allow you to downgrade, as it is still signing v5.3. Once v5.4 is released (iPhone related event scheduled for 10th September, so I'd guess iOS 7 will be released then, or shortly after) then there will be a period when you can still sign 5.3, but that door will close and 5.4 will be the only version you can run.

The key question is, why would you not want to be on 5.3? Is there something you can do in 5.2 that you cannot do in 5.3?

For an iPhone / iPad, from a development viewpoint, being able to install whatever version of iOS you want (within the limitations of the stock version the device shipped with / can run) would be fantastic. I've had people upgrade a device running 5.1.1 that I needed to get 5.1.1 on, and I get very annoyed when this happens, as it's difficult to downgrade them. I do wish Apple would provide devs a way to do this, heck tie it into authorization with the dev portal / provisioning, but let us devs be able to do it.

With latest beta the trailers thing stopped working since latest beta update. And i have no other way to go back to the previous beta since i dont have it, and when i try to use the older 5.2 version it says it cannot install it.

http://www.iclarified.com/entry/index.php?enid=970

Latest i can grab is 5.2.1

Found 5.3 :)

Does TinyUmbrella support 5.3 now?

Last time I checked, it didn't, maxing out at 5.2.1 or something.

I just used itunes restore ;) with the IPSW file.

Also it worked for 3 hours now again im just getting the trailers when set to my local DNS (router), if i set it hard to use the DNS of plexconnect it works fine again.

When I ping to trailers.appletv.com on my router it pings to plexconnect, how is that possible?

DNS caching?

Ok, So I take that it is a bug with Apple? Hopefully they can get this issue resolved. I miss having Plex directly on my Apple TV.