Skip to content

[PM-39023] Autofill on HTTP sties stopped working on iOS, still works with popup warning on desktop #2787

Description

@jmooo

Steps To Reproduce

Has been going on for several months, and there are a lot of reddit reports of it and a similar android bug (bitwarden/android#5609) and similar iOS bugs #2538 as well.

iOS 26.5.0 bitwarden 2026.5.0 (3226)

Tested combinations, w/ match detection "Starts with"
✅ Desktop firefox/chrome/brave + HTTPS
✅ Desktop firefox/chrome/brave + HTTP
✅ iOS firefox/chrome/brave + HTTPS
❌ iOS firefox/chrome/brave + HTTP

If I visit my local app at https://192.168.10.100:9090, which presents an SSL cert even though it's invalid (you can't have a valid ssl cert for an IP address), both desktop and mobile bitwarden integrations show matching password options and thus autofill works great.

If I visit the same app on the non-ssl port http://192.168.10.100:8080 desktop bitwarden autofill works fine, but mobile does not suggest any matches so no autofill.

Expected Result

Password autofills on any site, http or https.

Actual Result

Password only autofills on https sites

Screenshots or Videos

Image

Additional Context

No response

Build Version

3226

What server are you connecting to?

US

Self-host Server Version

No response

Environment Details

No response

Issue Tracking Info

  • I understand that work is tracked outside of Github. A PR will be linked to this issue should one be opened to address it, but Bitwarden doesn't use fields like "assigned", "milestone", or "project" to track progress.

Metadata

Metadata

Assignees

No one assigned

    Labels

    app:password-managerBitwarden Password Manager app contextbetaThis is a beta bug/featurebugSomething isn't working

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions