From 29d6a9205b15ec56387a35caa58894459e37bb24 Mon Sep 17 00:00:00 2001 From: "Danilo M." Date: Mon, 2 Nov 2026 19:31:24 +0100 Subject: refactor(autofill): remove the fill-OTP-from-SMS paths Filling OTPs from SMS used Play Services' SMS User Consent API, removed with the nonFree flavor; since then AutofillSmsActivity was a stub that never offered the dataset. Delete it, its manifest entry, the dataset builders in both response builders, its drawable and string. AutofillAction.FillOtpFromSms stays in autofill-parser: it is public, metalava-checked API and harmless for a client that never fills it. Co-Authored-By: Claude Opus 5.5 --- app/src/main/res/values/strings.xml | 1 - 1 file changed, 1 deletion(-) (limited to 'app/src/main/res/values/strings.xml') diff --git a/app/src/main/res/values/strings.xml b/app/src/main/res/values/strings.xml index 61596e58..45afc227 100644 --- a/app/src/main/res/values/strings.xml +++ b/app/src/main/res/values/strings.xml @@ -219,7 +219,6 @@ This app is currently not supported Passwords don\'t match Create entry - Extract code from SMS Maximum number of matches (%1$d) reached; clear matches before adding new ones. This app\'s publisher has changed since you first associated a Password Store entry with it: The currently installed app may be trying to steal your credentials by pretending to be a trusted app.\n\nTry to uninstall and reinstall the app from a trusted source, such as the Play Store, Amazon Appstore, F-Droid, or your phone manufacturer\'s store. -- cgit v1.2.3