signalapp / signalapp/Signal-Android

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

Open
#11,447 7 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

acknowledged
Dominant language
Kotlin
Stars
29.4k
Forks
6.9k
PR merge metrics
No merged PRs in 30d

Description


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

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the QR-code flow on Android 11 with Signal 5.15.6, using a URL with ?parameters as described in the steps. Trace the entry point that handles the link and verify that the recipient and message body are separated and prefilled according to the expected standard.

Written by the indexing model from the issue text.

Assessment

Tech stack
android, kotlin
Domain
mobile
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.