[Bug] [2.1.0.10] SMS to multiple recipients won't be sent to all

Hi @tom.i, we have tried to reproduce the issue you reported but failed. There must be something special in your device. We would ask you to help by collecting some logs from your device. There are two parts in this task, part A is an easy one, part B is not difficult either but requires the use of Developer mode. Please do A at least, and if you are familiar with the command line, then also B.

A) Install app oFono Logger from Jolla Store.

-Launch the app.
-Swipe left to get to the options.
-Pull down to enable all categories to log.
-Swipe right. You will already see the first lines of log on the display.
-Run your test case, i.e. write a test message and send it to multiple recipients.
-Make a note of the date and time of your device at the moment of sending the message.
-Return to oFono Log app. You can see the log on the display. Scroll to the top of it.
-Pull down "Pack and Send" and select "Email" to send your log. With email your log goes easily to the predefined address of a Jolla engineer (ofono-debug@jolla.com). We would not spread any personal information, should there be some in the log. Write to the email subject "oFono log for tjc 161292".
-Swipe right and then left to get to the category list. Pull down to disable all.
-Close the app.

B) Collect the journal log.

Do the following after completing phase A above.
-Enable Developer Mode.
-Open Terminal app.
-Get the super-user rights with command devel-su.
-Collect the journal log to a file in this way:

journalctl -a > /home/nemo/journal-for-tjc-161292.txt

-Send that file to email address ofono-debug@jolla.com. Write "journal log for tjc 161292" to the subject.
-Close Terminal.

Thank you for your help!

is not on 2.1.0.11 i tried this, and works perfect on my jp1.
Is that really important for jolla devs to know it? or user might be recommended to update to 2.1.0.11 version?
Then maybe it could be "solved" , or remained...

@jovirkku - both steps done ;) Thx for investigation ;)

Log has been created 9.5.2017 9:36

@cemoi71: We have not fixed any issues like reported here neither to 2.1.0.11 nor to the upcoming 2.1.1.xx, and have not been able to make the reported issue happen with those updates. Therefore an OS update would probably not help.
Updating the OS to the latest available version is always recommended, though. :-)

@tom.i: thanks a lot for your rapid actions. We will come back to this when our guys have investigated the logs.