Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Look at the icon #224

Closed
AgentMulder006 opened this issue Jan 13, 2021 · 13 comments
Closed

Look at the icon #224

AgentMulder006 opened this issue Jan 13, 2021 · 13 comments

Comments

@AgentMulder006
Copy link

I have one I can which is signed by a lock. I have no idea to open this I can. So I’m not able to enter my email account. Can somebody explain me what to do?
Thank you.

@rvdse
Copy link

rvdse commented Jan 20, 2021

When you add a token, you have the option to require you to unlock the phone to activate the token.

If I enable this, there's a small padlock on the icon. When I try to open it, it asks for touch id before showing me the 6-digit code. It seems to work as intended - is this not what happens to you?

@josejulio
Copy link

I have the same problem. The thing is that it worked before, but now it doesn't ask for anything. I'm supposing something should be failing silently.

Using FreeOTP 2.2.1 from App Store.

@justin-stephenson
Copy link
Collaborator

Can you confirm if this issue is still happening for locked tokens in the latest FreeOTP 2.3 ?

@josejulio
Copy link

Just tried on 2.3 and yes, still an issue.

@justin-stephenson
Copy link
Collaborator

@josejulio There was an issue with migrated locked tokens, can you try adding a new locked token to see if it exhibits the same problem?

@justin-stephenson
Copy link
Collaborator

@josejulio See #225 (comment) for more detail

@josejulio
Copy link

can you try adding a new locked token to see if it exhibits the same problem?

Adding a new one works well.

Is there any way to save the others? or should I see them as lost?

@josejulio
Copy link

Is there any way to save the others? or should I see them as lost?

From #225 (comment) It looks like they are lost

@justin-stephenson
Copy link
Collaborator

Please re-open this issue if the problem still persists on the latest FreeOTP version.

@dleske
Copy link

dleske commented Apr 5, 2022

I am experiencing this issue in 2.3.1.

@dleske
Copy link

dleske commented Apr 6, 2022

Following up on that. The experience I am having is that I had FreeOTP on an old iPhone, I started a new job where they insist on issuing me a new phone, everything transfers over to my new phone, including FreeOTP. I have two OTP profiles "locked" (requiring me to unlock the phone before I can get the token) and they cannot be unlocked on the new device under FreeOTP 2.3.1. It's 2.3.1 on the older device as well but I don't know that hasn't updated itself since the mindmeld of old device to new.

I don't know what the underlying issue is but it would be good if I got some error or information message when trying to unlock the token on the new device--I get no response at all, and at first thought the app was broken/frozen. If I'd had only locked token profiles, that's probably the conclusion I would have reached.

@eno-afk
Copy link

eno-afk commented Mar 4, 2024

Hi, same problem over there
I changed phone and now it is impossible to see the code due to my token being locked
Anyone had ideas?

@dleske
Copy link

dleske commented Mar 4, 2024

I changed phone and now it is impossible to see the code due to my token being locked Anyone had ideas?

Unfortunately @eno-afk I think your options are unlock on old phone or use recovery codes. This thread is referenced above and might provide more background.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants