Implementação no Android do preenchimento automático de OTP usando a API de Consentimento do Usuário e a API de Recuperação. Adicione a possibilidade de receber códigos OTP de outra entrada.
Orientação gerada a partir de informações públicas. Apenas para referência.
O pacote otp_autofill habilita o preenchimento automático de OTP no Android usando a API de Consentimento do Usuário e a API de Recuperador, permitindo que aplicativos detectem e preencham automaticamente senhas únicas de uso por SMS. Ele suporta a recepção de códigos OTP de fontes alternativas, melhorando a experiência do usuário durante a autenticação. O pacote também funciona no iOS, oferecendo compatibilidade entre plataformas para campos de PIN e OTP. Projetado para integração perfeita com campos de formulários, reduz erros de entrada manual e acelera os processos de login.
Casos de uso
Detecção automática de OTP em formulários de login
Melhorando a experiência do usuário durante a autenticação de dois fatores
Suporte a fluxos de verificação baseados em SMS
Integração com campos de entrada de PIN ou senha existentes
Habilitar recuperação de OTP de fontes alternativas
Principais recursos
Utiliza as APIs de Consentimento do Usuário e Recuperador do Android
Suporte multiplataforma (Android e iOS)
Extração automática de código OTP de SMS
Método de entrada alternativo para recuperação de OTP
Integração simples com campos de texto
Indicado para
Aplicativos que exigem entrada segura de OTP
Fluxos de autenticação com verificação por SMS
Desenvolvedores procurando reduzir a fricção do usuário
Projetos direcionados para plataformas Android e iOS
Aplicações com muitos formulários com campos PIN/OTP
Considerações
Requer Android SDK 28+ para funcionalidade completa
Limitado ao preenchimento automático de SMS do Android sem configuração adicional
A implementação no iOS depende do tratamento de OTP em nível de sistema
Permissões necessárias para acesso a SMS no Android
Pode exigir testes em diferentes fabricantes de dispositivos
README original
Snapshot do README original do repositório-fonte vinculado. Consulte o repositório para o conteúdo mais recente.
You could use autofill from another input by using the OTPStrategy (e.g. from push-notification).
For testing you could create a TestStrategy.
iOS
On iOS, the OTP autofill feature is integrated into the TextField component.
The code received from an SMS is stored for a duration of 3 minutes.
Rules for sms
Sms must contain the word code or its translation in iOS supported localizations.
The sms should contain only one sequence of digits.
iOS Testing
The iOS platform is capable of receiving OTP from any phone number, not just a specific sender.
Android
OTPInteractor.hint - displays a system dialog that allows the user to select from their saved phone numbers (recommendation from Google).
OTPInteractor.getAppSignature - creates the hash code of your application, which is used in the SMS Retriever API.
OTPInteractor.startListenUserConsent - the broadcast receiver that starts listening for OTP codes using the SMS User Consent API. It listens for a duration of 5 minutes, after which a timeout exception occurs.
OTPInteractor.startListenRetriever - the broadcast receiver that starts listening for OTP codes using the SMS Retriever API. It listens for a duration of 5 minutes, after which a timeout exception occurs.
OTPInteractor.stopListenForCode - used in dispose.
The plugin is designed to receive the full text of an SMS message and requires a parser to extract the relevant information from the message.
If you use the SMS User Consent API, the system will prompt the user for permission to access and read incoming messages.
It should contain a one-time code that the client sends back to your server to complete the verification process.
It should include an 11-character hash string that identifies your app (refer to the documentation for server for more details). For testing, you can obtain it from OTPInteractor.getAppSignature.
Android Testing
The OTPInteractor.startListenForCode method allows the application to start receiving verification codes from a specific phone number, specified by the senderPhone argument.
You also can use Android Emulator to test the plugin. To do this, you need to send an SMS to the emulator with the following command:
adb emu sms send <senderPhone> <message>
E.g.:
adb emu sms send 900 "Your code is 12345. Do not share it with anyone."
Make sure senderPhone is the same as the one you specified in the startListenForCode method.
Usage
You should use OTPInteractor to interact with OTP.
To simplify implementation, consider using the OTPTextEditController as a controller for your TextField.
OTPTextEditController.startListenUserConsent - uses the SMS User Consent API and listens to user strategies.
OTPTextEditController.startListenRetriever - uses the SMS Retriever API and listens to user strategies.
OTPTextEditController.startListenOnlyStrategies - only listens to user strategies.
OTPTextEditController.stopListen - used in dispose.
Installation
Add otp_autofill to your pubspec.yaml file:
dependencies:otp_autofill:$currentVersion$
At this moment, the current version of otp_autofill is .
Android Installation
Set minSdkVersion at least to 19 in <project root>/android/app/build.gradle.
To receive a new code when a timeout exception occurs, you can pass a callback function to the onTimeOutException parameter and start listen for a new code.
All significant changes to this project will be documented in this file.
Issues
To report any issues, submit them directly in the Issues section.
Contribute
If you wish to contribute to the package (for instance, by enhancing the documentation, fixing a bug, or introducing a new feature), please review our contribution guide first and then submit your pull request.
Your PRs are always welcome.
How to reach us
Please don't hesitate to ask any questions about this package. Join our community chat on Telegram. We communicate in both English and Russian.