Signal verification uses same phraseology to describe different functions

[UX-GURU]

• [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] This isn't a feature request or a discussion topic

---

Bug description

When setting up a new installation of Signal on an iPhone, the user is given the option to receive verification code via text message or voice call. Regardless of which option the user chooses, the user is presented with the same prompt saying "A verification code will be sent..." This leads the user to suspect the application may be performing the wrong function (i.e. sending a text message instead of a voice call). This is especially problematic when the user is troubleshooting failure of the verification system. This is especially problematic because the verification interface does not provide error messages, therefore the user could definitely benefit from a linguistically coherent user interface... of course the user could also benefit from error messages, but that's a whole other bug report.

Steps to reproduce

• Start off with an expectation of a linguistically coherent user interface. (I know, right?)
• Try to set up a new Signal account on an iOS device.
• When you get to the "Verification code" step, choose the "Resend Code" function.
• Wait a minute, then choose the "Call Me" function.

Actual result: Describe here what happens after you run the steps above (i.e. the buggy behaviour)

• Realize that the user interface is describing the text message function with exactly the same phraseology as the voice call function.
• Wonder if the same programmers who got the phraseology wrong also got the code wrong, resulting in the "Call Me" button actually activating the text message function instead of the voice call function.
• Receive no error feedback from the interface as to why you're not receiving the voice call (in order to emulate a user with a verification failure, for this exercise you need to pretend you're not receiving the voice call.)
• Have your troubleshooting generally slowed down and hindered and complicated by the fact that different functions are not referenced with distinct phraseology.

Expected result: Describe here what should happen after you run the steps above (i.e. what would be the correct behaviour)

• Realize that the user interface is describing the text message function logically and coherently with different and distinct phraseology as the voice call function.
• Realize that the programmers who implemented this phraseology correctly may have perhaps also correctly implemented the code, so the system is quite possibly not sending you a text when you are requesting a voice call.
• Have your troubleshooting of your verification failure assisted and advanced with this helpful and clear use of phraseology in the user interface.

Screenshots

I'll be honest, Signal project's normalized deviance discourages me from making the extra effort to plug in this phone to pull a screen shot off it and edit my number out of it. I already know there is a 99% chance this bug will be closed as "not a bug" so yeah, I'm not bothering with a screenshot.

Device info

Device: iPhone 7 Plus

iOS version: 15.7.3

Signal version: Can't find the Signal version because this Signal app is self-bricked because verification is broken. So, yeah, there's that. I can tell you that it's the version with the blue icon, if that helps any...

Link to debug log

Sorry I don't think I can get to the debug log because the app is self-bricked.

[EvanHahn-Signal]

Sorry this was confusing.

We've been actively working on improving registration, including updating the design and language. I hope those changes will help.

[UX-GURU]

Does any of this work and associated discussion occur in a public project management platform whereby interested users could monitor progress, form some basis for sharing your hope, and maybe even provide input?

[stale[bot]]

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.

[stale[bot]]

This issue has been closed due to inactivity.