Lack of a subsequent confirmation of receipt

[WebworkrNet]

Checklist

• I can reproduce the bug with the latest version given here.
• I made sure that there are no existing issues - open or closed - to which I could contribute my information.
• I made sure that there are no existing discussions - open or closed - to which I could contribute my information.
• I have read the FAQs inside the app (Menu -> About -> FAQs) and my problem isn't listed.
• I have taken the time to fill in all the required details. I understand that the bug report will be dismissed otherwise.
• This issue contains only one bug.
• I have read and understood the contribution guidelines.

Affected app version

1.0.1

Affected Android/Custom ROM version

Android 14, One UI 6.1

Affected device model

Samsung Galaxy A13 5G (SM-A136B)

How did you install the app?

F-Droid / IzzyOnDroid

Steps to reproduce the bug

Preliminary remark:

As far as I know, the sending of an SMS is confirmed in two stages:
1st tick ≙ transmission confirmation (the SMS was sent successfully)
2nd tick ≙ confirmation of receipt (the SMS has been received by the recipient).

I assume that the network protocol(s) used are used for this purpose and is basically no different than if I as a user manually prefix the SMS with a code corresponding to my provider (e.g. *T#, "Deutsche Telekom").

A confirmation of receipt should not be confused with a read confirmation. Read confirmations are not supported by the protocol(s) used.

At the time the SMS is sent, the recipient may not be reachable via the network. This is the case if the device is switched off or is outside a radio cell (dead zone).

Expected behavior

When the receiver is available in the network again, the receiver device should send the confirmation of receipt. The missing 2nd tick should now be set.

Actual behavior

There is no subsequent confirmation of receipt if the recipient device is outside the network at the time the SMS is sent.

Screenshots/Screen recordings

No response

Additional information

No response

[Aga-C]

Have you turned on Enable delivery reports in Settings?

[WebworkrNet]

Related to [Feature request] Being able to see "sent time" of received SMS #56.

[WebworkrNet]

Have you turned on Enable delivery reports in Settings?

The delivery reports are activated, see screenshot.

This report only deals with the special case when the receiving device is not logged into the network at the time the SMS is sent.

[WebworkrNet]

Related to Notify user when message is not sent #201.

[WebworkrNet]

Related to Keep SMS send and receive reports available #196.

[parrenin]

Related to this issue, I have two questions:

• why delivery reports are not activated by default?
• why is there no 'read confirmation' support in the app?

[naveensingh]

why delivery reports are not activated by default?

It wasn't always that way. It was disabled because delivery reports can cost money as per this commit.

why is there no 'read confirmation' support in the app?

As far as I know, 'read confirmations' are not something supported by the SMS protocol.

[parrenin]

Just googling, I found that 'read confirmations' are handled by the RCS protocol, which uses internet.
Since the Fossify apps do not use internet, I suppose this is out of the scope.