You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After conflux becomes active after having to resign (e.g.: home button is pushed), sometimes the client is not able to reconnect. There seems to be a timing issue, as after a while, if conflux becomes inactive and active back again, then the client is able to reconnect.
EDIT: after extensive testing, the timing issue seems to reside on ios/CFSocket API itself, as no form of closing/releasing resources prior to becoming inactive resolves the problem arising when the applicaiton regains focus and tries to open the socket again.
The text was updated successfully, but these errors were encountered:
After conflux becomes active after having to resign (e.g.: home button is pushed), sometimes the client is not able to reconnect. There seems to be a timing issue, as after a while, if conflux becomes inactive and active back again, then the client is able to reconnect.
EDIT: after extensive testing, the timing issue seems to reside on ios/CFSocket API itself, as no form of closing/releasing resources prior to becoming inactive resolves the problem arising when the applicaiton regains focus and tries to open the socket again.
The text was updated successfully, but these errors were encountered: