Closed ronnystandtke closed 10 years ago
@mcginty it looks like this is another case of our phantom stack trace not logging. We gotta figure out what's happening there.
Same issue here. I don't know how it is in other countries, but in switzerland, data-rate is pretty expensive and many users use Wifi with their smartphones only. With this Problem unsolved, all these users will get TextSecure messages (sent between textsecure users) only if they connect to Wifi next time, which is a showstopper. Users just do not expect this from a SMS App. SMS is expected to be delivered instantly and you don't know if your peer actually has data enabled or not. The SMS fallback should take this into account. It has to check if the peer is online (within some timeframe) and resend the message over SMS if the peer is not reached over the data channel.
Is it happening again in 2.0.5? From my glance over the stacktrace it can be something about this W/MessageDatabase( 6818): Updating ID: 268 to base type: 22 ... W/MessageDatabase( 6818): Updating ID: -1 to base type: 21
what should be fixed in #1024
Seems to work now, thanks!
Sending a simple SMS (just text) to a certain contact fails reproducibly. I can successfully send push messages to this contact and SMS to other contacts. One thing to notice is that the contact regarding this issue is the only one I have who is also using TextSecure and we once had an established key exchange (which I disabled before producing the logfile below). Strangely she can successfully send me SMS.
Here is the log file: