Autofill Guide

What is Autofill

KeyMe Pass Autofill can fill and save account passwords in third-party apps and browsers (non-membership capability). It is in Beta and improving; please complete the default autofill service and permissions as guided in the app and on this page.

Before you start

1. Turn on the Autofill switch in KeyMe Pass first.
2. Set KeyMe Pass as the default autofill service in system settings, or suggestions will not appear in other apps.
3. Complete background pop-up/display and notification permissions as prompted by your device.

If the app cannot open Settings, go there manually, search for "Autofill" or "Default apps", and set KeyMe Pass as the default autofill provider.

Android: recommended steps

Mode A: Standard Autofill (recommended first)

This is the primary path for most apps that support standard Android Autofill APIs.

1. Default autofill service

First, in system settings, search for Autofill and set KeyMe Pass as the default autofill service. Only after this can you use filling in other apps.

2. Enable Autofill

Then return to KeyMe Pass Autofill settings and turn on the main switch.

3. Permission hints (as needed)

Follow in-app prompts (names may vary by device):

• Background pop-up / display (highly recommended): on some OEM systems, filling may not respond until this is allowed.
• Notifications (highly recommended): helps with password-update flows (behavior varies by Android version).

After returning from system settings, use refresh status in the app to update detection.

Mode B: Accessibility recognition (Android enhanced detection)

For some apps that do not trigger the standard Android Autofill APIs, you can enable Accessibility recognition as a supplemental detection path.

1. Turn on "Accessibility recognition" and "Smart floating window" in the Autofill settings page.
   

   Step 1: Enable Accessibility recognition and smart floating window

2. Open the system Accessibility settings homepage.
   

   Step 2: Open system Accessibility settings

3. Enable the KeyMe Pass accessibility service permission.
   

   Step 3: Enable KeyMe Pass accessibility service

4. Optional: trigger accessibility recognition from the quick-settings tile.
   

   Step 4: Trigger from quick-settings tile

Usage flow can be viewed in this video:

If matching fails (Android / iOS): URL and app linking

• iOS / web (domain matching): the login URL participates in matching; for WebView or multi-domain sites, add or verify domains on the password entry.
• Android native apps: package name and related metadata matter; in some cases you can use androidapp://package.name in the URL field (replace with the real package name) to associate the entry with an app.

If it still fails, check that the URL and app association fields on the entry are correct.

iOS: recommended steps

Open Settings → General → Passwords & AutoFill → AutoFill from and enable KeyMe Pass (exact labels depend on iOS language and version).

iOS is also in Beta: some apps may show no candidates. Specifically, iOS versions below 26.2 do not support automatic saving of new passwords yet (this depends on newer system APIs and is still being adopted across the industry).

In scenarios without auto-save, you can add entries manually in KeyMe Pass, or add directly from the password suggestion list; newly added items will be automatically associated and stored.

Known limitations

• Some apps (e.g. certain messengers) do not use the standard system autofill APIs and may never show candidates.
• Browsers, in-app WebViews, and redirects can make domain matching less stable.
• HarmonyOS version note: HarmonyOS Next (HarmonyOS 5.x and above) currently does not support autofill because the system has not exposed the required APIs. HarmonyOS versions below 5.x are Android-compatible and can use the Android autofill capability.
• iOS has system-level constraints on third-party password managers for auto-save; experience may differ from Android.