Game Center real time match search failure serial number

A similar error I've been getting that does cause the app to eventually crash:

2020-03-11 17:30:17.635383-0700 Cirkus[46226:2540216] [ViceroyTrace] [ERROR] AGPSessionSendTo:1324 AGPSessionSendTo:: NOT ENOUGH TRANSMISSON WINDOW BUFFERS AVAILABLE!

I have nothing to offer except to say I see this error all of the time as well even though my game app works fine.

I am assuming this is what is happening ....

Viceroy seems to be a network algorithm which is used by Game Center to send packets over the peer-to-peer network. This error comes out as part of the viceroyTrace logging so I am assuming there was an issue sending some packets to some players in your game (ie: packet loss perhaps???) . I am assuming you are using TCPIP as a delivery protocol so the packets are re-transmitted until they arrive at the destination successfully. So you might get the viceroyTrace error but eventually the required network packets are received by the intended player (as a result of re-transmitting) and your game goes on successfully.

Thank you for your response! I am glad to know it is not just me.

During a Game Center real-time match, I'm seeing this error approximately every 11 seconds:

2020-06-28 10:09:37.425385-0700 <app name>[12860:1962955] [ViceroyTrace] [ERROR] AGPSessionRecvFrom:1954 0x123f87740 sack: SEARCH FAILURE SERIAL NUMBER (00000000) FROM (54D07057)...

I think this could be due to an aggressive connectivity check. Eventually, with a weak internet connection, this causes the real-time match to disconnect. In the past 3-4 weeks, some users have been reporting that 70-80% of their real-time matches have been getting disconnected. I reported a bug (FB 7816074).

if you set from .reliable to .unreliable the warning goes away, so it indeed has smth to do with packets not being able to send at first but then it will. Its annoying and I can't find any method to silence this warning

if you set from .reliable to .unreliable the warning goes away, so it
indeed has smth to do with packets not being able to send at first but
then it will. Its annoying and I can't find any method to silence this
warning

I'm only using unreliable, and I still get the error every ~11 seconds, even when no packets are being sent by my app.

I tried switching to reliable, and in addition to getting the error every ~11 seconds, I get the error every time my app sends a packet.

This occurred when testing on an iOS 13.5.1 device. When testing on an iOS 12.4.6 device, I didn't see this error in the debug log.

This issue is extremely annoying, there is also very little to be found on google/bing and etc

And the networking issue seems to be bigger when connected on 4G. I am trying to build a multiplayer real time game to learn Swift/SpriteKit and etc, but this is just unbelievably bad.

If anyone can shed a bit of light on the matter that would be fantastic.

On local WiFi I mostly get the error below ;

Code Block 
[ERROR] AGPSessionRecvFrom:1954 0x10cd064d0 sack: SEARCH FAILURE SERIAL NUMBER (0000017A) FROM (28388F35)...

Some of the errors I get when on 4G, after a while the connection is dropped :

Code Block 
NOT ENOUGH TRANSMISSON WINDOW BUFFERS AVAILABLE!
[ViceroyTrace]	[ERROR] OSPFParse_ParsePacketHeader:1087 bufferLength=38 is too small
[ViceroyTrace]	[ERROR] OSPFParse_ParsePacketHeader:1092 Bad version
[ViceroyTrace]	[ERROR] AGPSessionRecvFrom:1954 0x141208e50 sack: SEARCH FAILURE SERIAL NUMBER (00000000) FROM (12756BFB)...
2020-07-11 14:30:06.790292+0200 somesortofgame[12286:2400960] [ViceroyTrace]	[ERROR] RefreshAllocation:238 /Library/Caches/com.apple.xbs/Sources/AVConference/AVConference-1645.9.1.2/ICE.subproj/Sources/Relay.c:238: STUNEncodeMessage failed (80140008)
2020-07-11 14:30:06.790511+0200 somesortofgame[12286:2400960] [ViceroyTrace]	[ERROR] RelayRefreshProc:406 
[ViceroyTrace]	[ERROR] ICEStopConnectivityCheck:2733 ICEStopConnectivityCheck() found no ICE check with call id (1242799261)

This issue is extremely annoying, there is also very little to be found on google/bing and etc

If anyone can shed a bit of light on the matter that would be fantastic.

The bug report I filed has a resolution status of "Potential fix identified - For a future OS update". Hopefully, this means that they have found the cause of the issue and will fix it soon.

Thanks nasj442 !

On a side note, what are commercial games supposed to do meanwhile? There should be quite a few games with connection issues.

Oh by the way, is your bug report public ? if so do you have a link to your bug report?

Oh by the way, is your bug report public ? if so do you have a link to your bug report?

I posted the bug report number in my previous post, but I don't think you can see anyone's bug reports except your own.

iOS 13.6 is on the market, hopefully the issue has been resolved. I am going to check it later.