Signing back into the Community for the first time? You'll need to reset your password to access your account. Find out more.
Forum Discussion
mikeriz
2 months agoNew Contributor
Suggesting Microsoft 2fa for Microsoft todo
Suggesting Microsoft 2fa for Microsoft todo I’m using Microsoft todo on iOS. When I’m in a list you can see at the bottom of add new item it says verification code for xyz. It thinks I’m looking for a code when there is no login or password. I’m logged in. It should be blank and 1pass should not be trying to take over the page.
1Password Version: Not Provided
Extension Version: Not Provided
OS Version: Not Provided
Browser: Not Provided
- mikerizNew Contributor
You can see this at the bottom of the screen. When I go into edit mode to type a new task in ToDo, it brings up a login for Microsoft that I have.
- 1P_Dave
Moderator
Thank you for the screenshot! I can see how the current behaviour is not ideal when working in the Microsoft To Do app. AutoFill is specifically handled by iOS so we are unable to control when suggestions appear above the keyboard when you tap on a field inside of another app. 1Password only provides the data for the experience.
I recommend reporting this to Microsoft so that they can investigate this further on their end to see why iOS is suggesting a one-time password in the "Add a Task" field.
-Dave
- mikerizNew Contributor
Yeah , thanks for the idea, but I’m not gonna spend anymore time on this. You’re punting it and that’s where my support for this ends.
- 1P_Dave
Moderator
I'm sorry that I don't have a better answer to provide. Since iOS is more locked down than a desktop environment like macOS, 1Password doesn't actually have the ability to detect fields, provide suggestions, and fill those fields in other iOS apps. Instead 1Password uses an iOS technology called AutoFill:
It's iOS itself that is suggesting your one-time password in Microsoft To Do and our code isn't actually running there, we just provide the data for the experience. That being said, our development team has filed feedback with Apple and hopefully this is fixed in a future version of iOS.
-Dave
ref: dev/core/core#33171