Hi Arnaud, thanks for the post. We’ve been aware of this issue. It’s a problem with the way carriers deal with websocket connections. Let me explain. On the web there are several ways that nodes (server, clients, etc) can communicate. There are advantages and disadvantages to each but Flomio has chosen the most real-time one: websockets. Websockets maintains an open connection between the server and the client so that the application runs seamlessly. Scans are instantly recognized and feedback is immediate. This same approach is used by Google Docs, which runs powerful applications on the server-side without taking a lot of local resources. The problem is that cell phone service providers don’t like these “open connections” because they want to use their bandwidth more efficiently so they often tear them down in the middle. We’ve done some tricks to check for tear-downs and re-establish connections but sometimes we’ll miss a scan in the middle of doing so. This in effect prevents the picture to be posted.
There are more improvements we are working on to make the system more robust but in the meantime it’s best to use Wifi since that way websocket connections are not interfered with.
