We keep getting (not from all users) the following exception regarding BlueBox. can someone point me to a solution ?
Thank you
Fatal Exception: java.lang.Exception: Exception : Error dispatching event bb-ioError: Error dispatching event ioError: You can't change the BlueBox mode while the connection is running at Sfs2X.Bitswarm.BitSwarmClient.ForceBlueBox (System.Boolean val) [0x00000] in <00000000000000000000000000000000>:0
at Sfs2X.SmartFox.HandleConnectionProblem (Sfs2X.Core.BaseEvent e) [0x00000] in <00000000000000000000000000000000>:0
at Sfs2X.Core.EventListenerDelegate.Invoke (Sfs2X.Core.BaseEvent evt) [0x00000] in <00000000000000000000000000000000>:0
at Sfs2X.Core.EventDispatcher.DispatchEvent (Sfs2X.Core.BaseEvent evt) [0x00000] in <00000000000000000000000000000000>:0
at Sfs2X.Core.EventListenerDelegate.Invoke (Sfs2X.Core.BaseEvent evt) [0x00000] in <00000000000000000000000000000000>:0
at Sfs2X.Core.EventDispatcher.DispatchEvent (Sfs2X.Core.BaseEvent evt) [0x00000] in <00000000000000000000000000000000>:0
at Sfs2X.Http.HttpResponseDelegate.Invoke (System.Boolean error, System.String message) [0x00000] in <00000000000000000000000000000000>:0
at Sfs2X.Http.SFSWebClient.UploadValuesAsync (System.Uri uri, System.String paramName, System.String encodedData) [0x00000] in <00000000000000000000000000000000>:0
at System.Threading.TimerCallback.Invoke (System.Object state) [0x00000] in <00000000000000000000000000000000>:0
at System.Threading.WaitCallback.Invoke (System.Object state) [0x00000] in <00000000000000000000000000000000>:0
at System.Threading.ThreadPoolWorkQueue.Dispatch () [0x00000] in <00000000000000000000000000000000>:0 at Sfs2X.Core.EventDispatcher.DispatchEvent (Sfs2X.Core.BaseEvent evt) [0x00000] in <00000000000000000000000000000000>:0
at Sfs2X.Core.EventListenerDelegate.Invoke (Sfs2X.Core.BaseEvent evt) [0x00000] in <00000000000000000000000000000000>:0
at Sfs2X.Core.EventDispatcher.DispatchEvent (Sfs2X.Core.BaseEvent evt) [0x00000] in <00000000000000000000000000000000>:0
at Sfs2X.Http.HttpResponseDelegate.Invoke (System.Boolean error, System.String message) [0x00000] in <00000000000000000000000000000000>:0
at Sfs2X.<truncated: 491 chars>
at Sfs2X.Core.EventDispatcher.DispatchEvent(Sfs2X.Core.EventDispatcher)
at Sfs2X.Http.HttpResponseDelegate.Invoke(Sfs2X.Http.HttpResponseDelegate)
at Sfs2X.Http.SFSWebClient.UploadValuesAsync(Sfs2X.Http.SFSWebClient)
at System.Threading.TimerCallback.Invoke(System.Threading.TimerCallback)
at System.Threading.WaitCallback.Invoke(System.Threading.WaitCallback)
at System.Threading.ThreadPoolWorkQueue.Dispatch(System.Threading.ThreadPoolWorkQueue)
Getting bluebox exception
Re: Getting bluebox exception
Hi,
we need more details in order to understand what might be going on.
Please take a look here:
https://forums.smartfoxserver.com/viewt ... 18&t=16497
Thanks
we need more details in order to understand what might be going on.
Please take a look here:
https://forums.smartfoxserver.com/viewt ... 18&t=16497
Thanks
Re: Getting bluebox exception
Here are some more information
We are using Unity SDK 1.7.0
we are using SFS v2.13 on aws EC2
The issue exist in production (attaching 2 images from firebase crashlytics and unity analytics)
we suspect the issue is happening with slow network but we are not sure - we are still trying to reproduce it ourselves but it's not easy
we tried to use the java client API (not the Unity SDK) to try to figure out where the issue happening we pinpoint to this code and we are trying to reproduce it
We are using Unity SDK 1.7.0
we are using SFS v2.13 on aws EC2
The issue exist in production (attaching 2 images from firebase crashlytics and unity analytics)
we suspect the issue is happening with slow network but we are not sure - we are still trying to reproduce it ourselves but it's not easy
we tried to use the java client API (not the Unity SDK) to try to figure out where the issue happening we pinpoint to this code and we are trying to reproduce it
Re: Getting bluebox exception
Thanks.
The client API 1.7.0 is really, really old. 2016
I would strongly recommend to replace them with the latest available and see if it improves.
Let us know.
The client API 1.7.0 is really, really old. 2016
I would strongly recommend to replace them with the latest available and see if it improves.
Let us know.