robosats
robosats copied to clipboard
RoboSats
Chat delays when in active order
Describe the bug Chat delays in an active order
To Reproduce
Steps to reproduce the behavior:
This is in the new apk, v0.6.1-alpha. I'm not sure it can be reproduced, but in an active order, once I got to the 3 of 4 screen (chat with seller), I was able to type a message, but was NOT able to hit send. It was disabled, grayed out. Then all at once, I got a bunch of messages from the other party in the trade, indicating that the other party had been typing messages previously, and I had not been responding. Like "hello?, anyone there" type messages. I was then able to send messages. The trade completed. The whole thing just probably took a couple more minutes than normal, but it's disconcerting to have the chat window open but not be able to send a message.
This has never happened in any other place I've used robosats.
Smartphone (please complete the following information):
- Device: google pixel 7a
- OS: android
- Browser graphene os
- Version - build number 2024050700
Additional context Add any other context about the problem here.
Hey @Purchase73 . Indeed, this is in fact a legacy problem.
Will further explain the causes here in case anyone feels jumping into fixing this one.
The Android app uses the HTTP API of the chatroom. On browser, we use Websockets for instant messaging, but the HTTP API is also available (under the name "Turtle mode" the small icon between the two chat status indicators).
That means in Android the app polls for messages very X seconds. This coordinator endpoint might have some other issues as well that make it slow.
The Android app didn't use the Websockets for instant chatting because that was not possible with our previous Tor library. However, it is likeky that the websockets might work with the new native Tor library @KoalaSat implemented. So this issue might not be too difficult to solve anymore.
FYI - same issue again, second time I tried. When you go to a different screen (like I switch from Order to Robot and back to Order again) it appears to kick-start something, and I get the messages that have been queued up. Otherwise, I don't know if I'd ever get them.
I am constantly switching to tor browser or opening my computer because robosats android app constantly not shows the incoming chat messages. I have to restart the app several times until I get it through and often chats do not load. There is a huge latency until I see the messages.
My app version is: v0.7.3-alpha
I am constantly switching to tor browser or opening my computer because robosats android app constantly not shows the incoming chat messages. I have to restart the app several times until I get it through and often chats do not load. There is a huge latency until I see the messages.
My app version is: v0.7.3-alpha
Did you try to switch to "turtle mode"?
Did you try to switch to "turtle mode"?
Hi, I still have to run to start my computer to access rhe robosat chat...
What is "turtle mode"? How to activate it ?
I am unable to see the chat messages on an active order on android app. I have to open my computer and access through tor in order to see the messages. This is the case on many different brand of android mobile phones I have.
I am unable to manage the order on my mobile while I am traveling or away from my computer. I have to use online solutions to pass the information to my mobile to manage the payments etc. It is ver unpractical.
That would be great if we could fix it.
I am unable to see the chat messages on an active order on android app. I have to open my computer and access through tor in order to see the messages. This is the case on many different brand of android mobile phones I have.
I am unable to manage the order on my mobile while I am traveling or away from my computer. I have to use online solutions to pass the information to my mobile to manage the payments etc. It is ver unpractical.
That would be great if we could fix it.
I still did no received any other user feedback on this reward and testing it myself I see no problem, hownks your general Tor experience? Is it possible your location has a lower internet connectivity?
Hey @KoalaSat, are you currently working on this issue?
As I said on my last comment I'm not able to reproduce it. Maybe you can give it a try, but first try to reproduce it.
I tried to reproduce it, but I didn't notice anything unusual. I'll give it one more try tomorrow. Would it be better to implement WebSockets directly with the new Tor library and hope that resolves the issue?
I tried to reproduce it, but I didn't notice anything unusual. I'll give it one more try tomorrow. Would it be better to implement WebSockets directly with the new Tor library and hope that resolves the issue?
That's already implemented 🙂 that's why I believed this issue was actually fixed