touch-packages team mailing list archive

[Niklas Wenzel <nikwen.developer@xxxxxxxxx>]

This happened again yesterday. With GOOD network connection!!! But this
time I was able to fetch the log file using the command Matthias posted.

** Description changed:

+ When sending text messages, Ubuntu displays the loading spinner forever.
+ In the provider's monthly reports, I can see that the message has been
+ sent multiple times, even though I only sent one message to one
+ recipient and the message was short enough not to be broken into
+ separate ones.
+ 
+ 
+ ======= Old description: =======
+ 
  When having a bad network connection, Ubuntu tries to send SMS multiple
  times but fails to recognize which messages have already been sent,
  resulting in very high costs due to the same message actually being sent
  several times.
  
  I found this when looking through my provider's monthly reports and I
  remember being on train journeys with very bad network connections on
  these days. See the attached screenshots.
  
  ==========
  
  This happened on a Nexus 4 running on the stable channel (with up-to-
  date images at the given times).

** Summary changed:

- High costs due to SMS being sent multiple times when having a bad network connection
+ High costs due to SMS being sent multiple times

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to telephony-service in
Ubuntu.
https://bugs.launchpad.net/bugs/1480554

Title:
  High costs due to SMS being sent multiple times

Status in telephony-service package in Ubuntu:
  Confirmed

Bug description:
  When sending text messages, Ubuntu displays the loading spinner
  forever. In the provider's monthly reports, I can see that the message
  has been sent multiple times, even though I only sent one message to
  one recipient and the message was short enough not to be broken into
  separate ones.

  
  ======= Old description: =======

  When having a bad network connection, Ubuntu tries to send SMS
  multiple times but fails to recognize which messages have already been
  sent, resulting in very high costs due to the same message actually
  being sent several times.

  I found this when looking through my provider's monthly reports and I
  remember being on train journeys with very bad network connections on
  these days. See the attached screenshots.

  ==========

  This happened on a Nexus 4 running on the stable channel (with up-to-
  date images at the given times).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/telephony-service/+bug/1480554/+subscriptions