Support entering otpauth:// URIs in details

[SimJoSt]

Is your feature request related to a problem? Please describe.
Currently, all my TOTP codes are in apps that save and display them in the edit screen as otpauth:// URIs. That makes them easy to copy and paste. As of now, there is no option to enter the full URI via the "enter details" option.

Describe the solution you'd like
It would be great, if there was an option next to TOTP, HOTP, MOTP & Steam to enter full otpauth:// URIs.

Describe alternatives you've considered
From the otpauth:// URI, it is possible to extract all the parameters to enter them separately into the form fields. It just takes a lot more work and requires a certain degree of precision.

Additional context
Apps and services using the otpauth:// URIs are e.g. 1Password & Bitwarden.

[flocke]

The easiest solution might be to just encode the otpauth:// URIs as QR codes and scan them.
Alternatively, if you get the URIs as clickable links on your Android phone, you can just click them and Android should offer to open them with andOTP.

[alexanderadam]

Would this be necessary to achieve something like the Authy push messages (see also this issue) or should this already work out of the box since #393 was implemented?

[alexanderadam]

I don't think the otpauth:// URLs can be used for something like push OTPs. They are mainly for transferring the secret, which is only needed once.

I see. So this would be another scheme then, right?
Any chance that you know already what schema Authy might be using or how it might work internally?
And the general workflow would probably having a push client (i.e. Unified Push) that reacts on the push message with opening a certain app intent?

To implement something like push OTP you would need a server side as well as a compatible client. For an open source project I would probably try something like UnifiedPush to transfer the messages.

I'm aware of that. As far as I understood the architecture, Unified Push usually needs a backend that's compatible to it (i.e. ntfy, NextPush or Gotify).
That's why I opened an issue on the ntfy server.

But I have no insights about Android development or its requirements for opening apps. That's why I asked.