Standardized ?params to prefill correctly, resulting in API issues (eg, QR code SMS template)

[dylanh724]

• [x ] I have searched open and closed issues for duplicates
• [x ] I am submitting a bug report for existing functionality that does not work as intended
• [x ] I have read https://github.com/signalapp/Signal-Android/wiki/Submitting-useful-bug-reports
• [x ] This isn't a feature request or a discussion topic

---

Bug description

For example, Taiwan gov't COVID tracking program will need me to register via QR code (that submits a pre-filled text containing the identity of the venue):

The result is an empty text compose with a broken "to" field (I'll edit this later with a screenshot). Eg:

{smsNum}?body={body} : {realPhoneNumHere}{messageHere}

The actual message has 0 prefilled.

Steps to reproduce

1. Scan a QR code that has ?parameters to send a prefilled text message.
2. Watch the "to" field containing the entire API line.
3. Even if you filled the body and sent, it's still broken due to the to field being messed up.

Actual result:
Prefill params are all in the "to" area: Need to change default app to anything except Signal to work (it's just you guys that don't follow these standards, it appears).

Expected result:
Message should be prefilled as standardized.

Screenshots

TODO

Device info

Device: Samsung S20+
Android version: 11
Signal version: 5.15.6

Link to debug log

n/a

[stale]

Is this still relevant? If so, what is blocking it? Is there anything you can do to help move it forward?

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.

[dylanh724]

Still relevant.

[cody-signal]

Would you be able to provide a sample QR code and example of expected/actual data.

[dylanh724]

{number}?body=probably%20is%20encoded

In Android, this would prefill the body (similar, if not identical to, mailto email link params). iOS enjoys rebelling against standards, so body param key may differ.

[dylanh724]

Randomly found this on Google. This seems to be a demo, so ignore the actual phone number (not mine).

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[FlorianObermayer]

Another example for broken parsing:

Here, the recipient will be parsed incorrectly, resulting in: ?body=www.whisp.ly/r/cjN0iYN instead of no recipient with body content: www.whisp.ly/r/cjN0iYN#uls1xlZbL2FTQ.