Noted @Lafunamor 's first issue is resolved but his language issue is very relevant. Fixing this tomorrow on the train hopefully..

Done

just glad you can use your phone again ;-)

Excellent, thank you very much!

@Lafunamor See, I knew I was missing something! Cheers.

Ugh we also have an open support ticket for this, I'm going to copy/paste my response from there here:

Hey, you say the login for both apps are a challenge but only list issues with the UX for the unlock app, what issues did you have with the control app?

a)

Agreed. Hrm, not heard of this issue before, possibly caused by debouncing. (Actually see what Lokki said, I forgot this option existed....) We fixed that a few days ago I think, please update and test. Weird, possibly due to wifi/3g not connecting quick enough? Yea this is a limitation we're facing.

b)

Probably a combination of your phone and your ring. Yea it probably would, the read radius is much larger anyway so reads are easier.

I will close the support ticket and we can work on this here :)

@asbath said:

Creating a text tag "The quick brown fox jumps over the lazy dog." works just fine. I get the little pop up indicating that it worked, and reading it confirms that. Creating a text tag "The quick brown fox jumps over the lazy dog. The quick brown fox jumps over the lazy dog." works fine.This works on all 4 inlays. Creating a text tag "The quick brown fox jumps over the lazy dog. The quick brown fox jumps over the lazy dog. The quick brown fox jumps over the lazy dog." fails to write. I will hear the double beep tone indicating that it successfully accessed a NFC tag, but then the app freezes. This happens consecutively with multiple attempts on all 4 inlays. Creating a text tag "0123456789012345678901234567890123456789" actually fails to write. Creating a text tag "012345678901234567890123456789" fails. Creating a text tag "01234567890123456789" reads/write fine.

Hi @asbath , the first fox is 51 bytes, second is 96 bytes and third is failing at 141 bytes because your usable space is 137 bytes. So that's all normal there.
The third fox string also fails to write in the NFC Control App, but I was expecting this as it's oversized.
Your 01234567890123456789 is 27 bytes, second version is 37 bytes and works for me in NXP Tagwriter, first version is 47 bytes and also works fine for me in tagwriter.
The number strings failed for me in the NFC Control App, the writer application just stopped working.

Nope. Unlock when receiving call, never relock

Thanks for sharing. Can you please open an issue in the official issue tracker for each of those?

The beta app is now in production so it probably wont make a difference.

When you reset your password, that IS your verification code.. Use that password as your verification code.. It's pretty confusing I know... It's because we use Parse right now and Parse sucks, we hope to move away from it in the near future.

Excellent, no problem at all - one more thing I'll recommend is that if you aren't able to turn your standard lock screen off in settings then you should use something like 'no lock' to turn it off, it makes the whole experience more fluid-feeling!
Have fun with your ring!

I can't test it but from what I read there doesn't seem to be a user controlled white list for programs in that.

Ah, that's pretty much what I was doing when I was using my Nokia N9 - I haven't bothered with vCards since I started using the unlock, paranoia means I have both sides of the ring programmed in just in case.

Definitely do the faulty/returns procedure. If you try to fix the ring it's not going to be eligible as a return item because it'll seem like you caused the damage.
For what it's worth, I used my classic ring like that for an age before giving it to a friend to test devices. The failed inlay is workable when it's pressed the right way, it's just scary to do that on a phone.
The alpha I've tried a couple of repair techniques with varying success. I first lost my public inlay, regained that function for a fortnight then lost it again. At the moment I've got it back but the private inlay is dead. (This is due to my interference, attempting to reflow the broken solder joints. It's not recommended or advised and it does completely invalidate any warranty.)

If anyone does feel like doing tutorials off their own bat, I'll count a usable tutorial as grounds for a ring reward!

thanks for sharing

hi there. I somehow missed this thread or just had no time to answer. sorry!
The info about the issue with 2-factor auth is in the troubleshooting thread. I also recommend to enable the pin so you don't get locked out when flight mode is enabled.
Enable PIN: Application Security -> Manage application passwords -> PIN

@aomega001 if you have the latest version with the little button up top right of the screen that says 'enable', tap it to enable the unlock. it changes to say 'disable' which will disable the unlock if you tap it.
You also have to be sure that your unlock keys are entered into the app and also enabled - you can manually disable keys that way if you lose them or misplace them temporarily.