Protect what matters – even after you're gone. Make a plan for your digital legacy today.
Forum Discussion
flmklfrz
1 month agoNew Contributor
Autofill no longer works on HTTP pages; iOS shows white blank screen
I’m running into an issue where 1Password can’t fill on any http:// pages across multiple platforms, and on iOS it can even result in a white/blank screen when I try to fill. What’s happening iOS ...
- 1 month ago
Hi everyone, thanks for reaching out.
Our developers are aware of this issue and have a fix that is being tested in our current Nightly release for the browser extension. Once the fix has passed through the testing in the nightly release it will move to our Beta release and finally to the Production release.
If you are interested in using the Nightly release of the browser extension you can install the nightly release by referencing the details found on the page linked below:
As an alternative to testing the nightly release you can also use the Drag and Drop functionality in 1Password on Windows, Mac, and Linux devices to make filling the details on an HTTP page slightly easier while we wait for the fix to be released in the production version.
If you're using an iOS device, you can tap and hold a login field on HTTP pages > choose Autofill > Passwords > and then select the login item in the 1Password app.
I understand these workarounds are not ideal and I apologize for any inconvenience caused. Let us have any questions!
- FS-4500
Sharuru
1 month agoNew Contributor
The scope of this issue's impact is so large and it has lasted so long; it has not been fixed until now (nearly a month), which is completely unacceptable.
HTTP autofill, such an obvious and commonly used feature, surprisingly went unnoticed for issues across multiple release stages (nightly, beta, production). The funniest part is that fixing this bug also has to go through nightly, beta, and production versions.
It gradually becomes hard to trust.
- Sharuru1 month agoNew Contributor
By the way, at the very beginning of the issue, I searched the community and found that people had already reported this problem in the nightly and beta versions before the production release. XD