Msg sending/receiving when with low signal

[TubaOrNotTuba]

The problem

NOTE: My apologies, I'd forgotten I posted this back in April. Just lost another potential customer to it and felt like it needed posted. In all honesty, though, this really should be your top priority. Not changing timing options that didn't need changed, but making sure first and foremost that Wire is able to communicate at every possible time.

If one does not have reasonably good cell or wifi signal sending/receiving msgs (forget media) is impossible. Msgs will either fail to send or be received. If I switch over to WhatsApp I can send/receive the exact same msg AND I'm able to send media, like photos, without issue when Wire will do neither. It's very much like Wire assumes that there will be at least strong 3G/4G service at all times. Unfortunately that's not always the case. Whatever protocols you're using, they're far less efficient than WhatsApp and that just lost a potential business customer today. They tried Wire for a while and found it to just be too unreliable in low signal areas, which is much of rural America.

Environment

• Wire version that exhibits the issue: All versions
• Last Wire version that did not exhibit the issue (if applicable): N/A
• Android OS version used to run Wire: 6.0, 7.0, 8.0
• Is this a custom firmware or a stock one: Stock
• Mobile phone model/manufacturer: LG, Samsung, (yes, even on iPhone), Google Pixels
• Mobile network type (EDGE/LTE/Wi-Fi/Offline): 1x, 3G, 4G LTE

Details

Very simply, if you don't have good service Wire either fails to send or takes an eternity to send where WhatsApp will send and receive msgs all day long on 1x without issue. If Wire wants to be the goto app for mobile messaging, it must be able to communicate in the worst of conditions.

Link to Debug logs

Create a GIST which is a paste of your Wire logs, and link them here. It is recommended to directly contact our customer support and send the debug report by email, because it can potentially contain some private information, that you don't want to share to the public.

How to send detailed debug report from Wire:

1. Go to Settings -> About
2. Tap "Wire swiss GmbH" 10 times
3. Reproduce your issue
4. Send the report from Settings -> Advanced -> Submit debug report
5. Go to Settings -> About
6. Tap "Wire swiss GmbH" 10 times again to disable detailed debug reports, because this slows down Wire

Screenshots

Please attach screenshots if you consider them as helpful to understand/reproduce the issue

[marcoconti83]

Hi @TubaOrNotTuba , Thanks for writing this up. I believe the issue is not with the message per se, but with the fact that dropping the websocket too often (which can happen when the connectivity is spotty, such as on 3G) will cause us to make too many requests.

It would be great to have a log report when this happens. At the moment the logs that are sent from the app are not very informative for us, so they won't help us, but we are adding the ability to send more logs (which takes time, because the logs should be sanitize not to contain any sensitive information). Once this is in place, we will ping here and ask you to try to reproduce and send us the logs.

[m4rkusxxl]

Logs should be available in wire, right?

[makingthematrix]

I think this should be better now, with changes to the http client functionality and the new OkHttp library. I know it's a tricky thing to test but can you give us some feedback on it?