Unable to Pair on iOS 15 beta 6

[wardsimon]

It seems like something has changed in the pairing mechanism for the latest iOS beta. On attempted casting the following is logged with an error Unable to connect:

2021/08/24 18:50:45 request received : GET /info body 70
2021/08/24 18:50:45 response sent : body 374
2021/08/24 18:50:45 request received : POST /pair-verify body 37
2021/08/24 18:50:45 response sent : body 140
2021/08/24 18:50:45 request received : POST /pair-setup body 6
2021/08/24 18:50:45 response sent : body 409
2021/08/24 18:50:45 request received : POST /pair-setup body 457
2021/08/24 18:50:45 response sent : body 69
2021/08/24 18:50:45 request received : POST /pair-setup body 159
2021/08/24 18:50:45 response sent : body 143
2021/08/24 18:50:45 request received : POST /pair-verify body 37
2021/08/24 18:50:45 server.go:82: Error:Error handling RSTP request Invalid internal pairing verify step Waiting

When paired through the home app there are no errors. However the following is in the log:

2021/08/24 18:57:20 request received : POST /configure body 148
2021/08/24 18:57:20 response sent : body 237
2021/08/24 18:57:20 request received : TEARDOWN rtsp://192.168.1.73/7350123517057450268 body 42
2021/08/24 18:57:20 response sent : body 0
2021/08/24 18:57:20 server.go:37: Error:Event error : EOF
2021/08/24 18:57:20 server.go:76: Error:Error parsing RSTP request EOF 

And the same error when trying to cast.

Casting works on iOS 14.7.1 and macOS devices.

[AlbanSeurat]

Thanks for the heads up. I will have a look

[noelhibbard]

Please tell me Apple isn't already trying to spoil the fun.

[AlbanSeurat]

It seems that there are issues with the Airplay 2 with other Apple Device (Airport Express / Apple TV).
I would wait to see if the final version has also some errors before trying to correct the possible bugs

[iChUdY]

Final iOS 15 is here and same problem:

2021/09/25 21:16:50 Starting goplay for device Pi: 35aa4396-8bb7-42e3-9e45-3803aecfdb90, guid: 35aa4396-8bb7-42e3-9e45-3803aecfdb90, Psi: 35aa4396-8bb7-42e3-9e45-3803aecfdb90
2021/09/25 21:17:04 request received : GET /info body 70
2021/09/25 21:17:04 response sent : body 374
2021/09/25 21:17:04 request received : POST /pair-verify body 37
2021/09/25 21:17:04 response sent : body 140
2021/09/25 21:17:04 request received : POST /pair-setup body 6
2021/09/25 21:17:04 response sent : body 409
2021/09/25 21:17:04 request received : POST /pair-setup body 457
2021/09/25 21:17:05 response sent : body 69
2021/09/25 21:17:05 request received : POST /pair-setup body 159
2021/09/25 21:17:05 response sent : body 143
2021/09/25 21:17:05 request received : POST /pair-verify body 37
2021/09/25 21:17:05 server.go:82: Error:Error handling RSTP request Invalid internal pairing verify step Waiting

[rainbowicenow]

Same with iOS 15.1 Public Beta 2
Adds to Home just fine at first, but needs to change the name when re-adding it to Home

2021/10/03 23:35:45 request received : GET /info body 70
2021/10/03 23:35:45 response sent : body 374
2021/10/03 23:35:45 request received : POST /pair-verify body 37
2021/10/03 23:35:45 response sent : body 140
2021/10/03 23:35:45 request received : POST /pair-verify body 37
2021/10/03 23:35:45 server.go:82: Error:Error handling RSTP request Invalid internal pairing verify step Waiting

[Neustradamus]

The iOS 15.0.x is now here, the problem is here too?

Note: The iOS 15.1 Beta 4 is here too.

[mightymatth]

Yes, the pairing doesn't work on iOS 15.

[gedw99]

Do apple publish change logs etc ?

Would make it way easier to see how to adjust the code

[flexzuu]

@AlbanSeurat is there something we can help with, or some documentation on how we could go about figuring out what changed?

[AlbanSeurat]

I pretty sure this is due to the way I pair goplay. I will try to change that in the comings days. Quite busy lately

[prashnts]

Curiously the python port still works fine (ish) with iOS15.

The only thing there that does not work is sync between my Sonos's Airplay (which seems to have longer delay).

And yes, happy to help if you need it, too!

[lucek8123]

@AlbanSeurat Any way to pair GoPlay2 with iOS/iPadOS 15 and macOS Monterey?

Any upadates? I still having that problem.

2021/10/03 23:35:45 response sent : body 374
2021/10/03 23:35:45 request received : POST /pair-verify body 37
2021/10/03 23:35:45 response sent : body 140
2021/10/03 23:35:45 request received : POST /pair-verify body 37
2021/10/03 23:35:45 server.go:82: Error:Error handling RSTP request Invalid internal pairing verify step Waiting

[noelhibbard]

@AlbanSeurat Any way to pair GoPlay2 with iOS/iPadOS 15 and macOS Monterey?

Any upadates? I still having that problem.

2021/10/03 23:35:45 response sent : body 374
2021/10/03 23:35:45 request received : POST /pair-verify body 37
2021/10/03 23:35:45 response sent : body 140
2021/10/03 23:35:45 request received : POST /pair-verify body 37
2021/10/03 23:35:45 server.go:82: Error:Error handling RSTP request Invalid internal pairing verify step Waiting

He seems to be busy on other obligations. Just curious, have you tried the development branch of shairport-sync? It has AirPlay 2 support and HomeKit pairing is working well with it. Even on iOS 15.2. It's stable enough that there is talk about merging AP2 into the master branch.

[lucek8123]

Hi, any changes?

[jasonkolodziej]

I am not on iOS 15 beta version, just normal but facing the same exact issues.

DEVICE: Raspberry PI ZERO W2

Running on Ubuntu Core 22.04 with a snap created for such.

I am trying out the feature/-- branch right now and will reply with updates.

btw if anyone would like the snapcraft.yaml file lmk :-)

[jasonkolodziej]

I am not on iOS 15 beta version, just normal but facing the same exact issues.

DEVICE: Raspberry PI ZERO W2

Running on Ubuntu Core 22.04 with a snap created for such.

I am trying out the feature/-- branch right now and will reply with updates.

btw if anyone would like the snapcraft.yaml file lmk :-)

Update for branch: feature/audio-sync

I noticed that audio/player.go might need a StreamCallback for audio.Player{}.stream from codec/stream.go aka codec.StreamCallback{} instead of a new codec.Stream{}?

This was a fast take at debugging the feature branch... Not sure if that's the case?