I haven't figured out how to reproduce this; it seems to happen at random.
After handling the bang payload (type 1), the next payload should be streaminfo (type 13). For some reason the bang handler is being called a second time though, receives the type 13 payload, and returns the error StreamConnection expected bang payload but received something else. Then, the streaminfo handler is called for the next payload, but the streaminfo payload has come and gone already so streaminfo receives an unexpected payload type as well.
Since I haven't found similar bug reports on other platforms, I think this may be related to how the threading is implemented on Vita.
I haven't figured out how to reproduce this; it seems to happen at random.
After handling the
bang
payload (type 1), the next payload should bestreaminfo
(type 13). For some reason thebang
handler is being called a second time though, receives the type 13 payload, and returns the errorStreamConnection expected bang payload but received something else
. Then, thestreaminfo
handler is called for the next payload, but thestreaminfo
payload has come and gone already sostreaminfo
receives an unexpected payload type as well.Since I haven't found similar bug reports on other platforms, I think this may be related to how the threading is implemented on Vita.