Attaching authenticator process bugged (or instructions)

I have been trying to attach the authenticator and SMS to my account. I have followed all steps in your help articles, and dealt with various GM’s to get it done via a ticket (Ticket Number: US108275534 for ref). They have directed me here.

As it stands, the instructions when trying to attach the authenticator leads to a page (mobile app) that asks for

i) Serial Number (which I have found)

ii)Security Code (which the little ‘i’ reports it can be found on my homepage of the app)

This security code does not exist anywhere accessible that I can I find in the app let alone as per the instructions provided.

Please advise on how to get this attached, where this security code exists, and update your app and help articles to reflect the correct process and locations

EDIT:

As it stands the GM’s instructions to use the mobile app explicitly has caused this issue since the instructions under the little ‘i’ in the app, differ from the instructions presented on the website via chrome and a PC

Mobile app reports the security code can be found on the homepage of the app (which is the social button at bottom left, the default displayed on load)

The website however, advises that the security code can be found via the app, and select ‘manual entry’, at which point the app displays the security code.

This very much seems like the “Right hand doesn’t know what the Left hand is doing” and vice-versa. When you have one set of instructions for the mobile app, and one set for the web, you end up utilizing time, resources, and money, on issues that should never occur in the first place. I’m sure your shareholders would comment on such things if they were aware.

And albeit, it took a customer not a payed employee or DEV to figure out where the screwup is, and how to resolve it. Ask your shareholders about that and see what their feedback is.