Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Lack of a subsequent confirmation of receipt #220

Open
7 tasks done
WebworkrNet opened this issue Sep 13, 2024 · 9 comments
Open
7 tasks done

Lack of a subsequent confirmation of receipt #220

WebworkrNet opened this issue Sep 13, 2024 · 9 comments
Labels
bug Something is not working needs triage Issue is not yet ready for PR authors to take up

Comments

@WebworkrNet
Copy link

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

@WebworkrNet WebworkrNet added bug Something is not working needs triage Issue is not yet ready for PR authors to take up labels Sep 13, 2024
@Aga-C
Copy link
Member

Aga-C commented Sep 13, 2024

Have you turned on Enable delivery reports in Settings?

@Aga-C Aga-C added question Further information is requested waiting for author If the author does not respond, the issue will be closed. Otherwise, the label will be removed. labels Sep 13, 2024
@WebworkrNet
Copy link
Author

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

@github-actions github-actions bot removed the waiting for author If the author does not respond, the issue will be closed. Otherwise, the label will be removed. label Sep 13, 2024
@WebworkrNet
Copy link
Author

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.

Screenshot_20240913_113105_Messages

@WebworkrNet
Copy link
Author

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

@WebworkrNet
Copy link
Author

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

@Aga-C Aga-C removed the question Further information is requested label Sep 13, 2024
@parrenin
Copy link

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
Copy link
Member

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
Copy link

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.

@naveensingh
Copy link
Member

Yep :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something is not working needs triage Issue is not yet ready for PR authors to take up
Projects
None yet
Development

No branches or pull requests

4 participants