Open solarin opened 4 years ago
If you didn't save a copy of the file, we can only speculate.
the telephone i used was marked as spammer because it tried to reconnect too fast, shit! i need to wait 3 hours.
the telephone i used was marked as spammer because it tried to reconnect too fast, shit! i need to wait 3 hours.
That sounds like a different problem, not related to this issue.
this makes me think that the session file is storing some information about the next expected packet
the telephone i used was marked as spammer because it tried to reconnect too fast, shit! i need to wait 3 hours.
was that telephone emirati? Maybe related to issue 935?
the telephone i used was marked as spammer because it tried to reconnect too fast, shit! i need to wait 3 hours.
was that telephone emirati? Maybe related to issue 935?
no no this is a vietnamese number, the one that was working
this session file problem exists regardless of the number. so let's keep separated from #935
anybody has an idea of which fields in the session object can cause the communication to abort?
if sequence is not updated for example?
Hello, It happened that after closing the application, restarting the application, the software wasn't able to connect throwing an exception and I had to delete the session file and reauthenticate again.
I didn't see properly how this file is working, so, what can go wrong in this file to make this happen?
is the session storing information regarding the expected bytes to receive from the server?