Alert not NFC ring
If you're not having any luck, make sure that the subject line is clear - Unlock App Verification Code Request.
There are so many support requests that you can get lost in the mix, so be quite clear about what you need.
ajskuce last edited by
Been two days since I sent in an email about this and no response.
MauricioU last edited by
I have this same problem, I sent an email and have not received a response. Is there a solution?
There is a solution, just hold tight for now - @NFCringTom handles support requests plus a lot more.
@Lafunamor Sure, request # 7686
MLUM last edited by MLUM
This must be a huge problem.
1200 views of this thread and yet as far as I can tell the problem hasn't been solved.
I've been holding tight since May when I was supposed to receive my ring.
Now I'm holding tight for a verification code.
Around 20 rings as an estimate. Not a huge problem, just an irritating one. Lots of those views will be guest views that occur because this thread is continually bumped to the top.
@NFCringTom any update? Any way Lokki and I can help?
I received a password so that the I can get into the Lock app.
I downloaded the latest control app 0.1.11 but that app still does not work.
My support requests have been closed despite still not being able to get into the control app.
you mean the unlock app?
@Lafunamor Sorry, yes, Unlock App. I am now configuring that one.
now I'm confused. Did the code work? Is your problem now resolved or not?
The code worked and the Unlock App works!
Happy with that.
It was my mistake/misunderstanding about how/what the Control App is for.
The support requests related to the verification code have been closed as they should be.
(What I meant about the Control App is that the Register function does not work, but it doesn't matter to me because I received the code via email.)
Exactly. The naming is a bit confusing as "register" in the unlock is just to get a verification code for the unlock app.
idontknow544 last edited by
Has anyone had any success yet? I am having the same issue and have emailed the support team a week ago with no response.
@idontknow544 All of these supports tickets are closed, what is your number? Message me it
randumb last edited by randumb
Stealth Bomber NFC Ring
Get Started link embedded and functioning.
In The Control App (0.1.16) I get: ALERT NOT NFC RING error for both inlays.
In the Unlock App (1.5.113) I get: "Invalid key, try again" error for both inlays.
Looks nice, fits perfect! Hope I don't have to send back this one of a kind ring!
(Also, my email said one in-lay was supposed to be wood, did those get ousted?)
shama last edited by shama
@randumb I guess wood was one of the inlays the factory seemed incapable of delivering. I'm sure Tom or John (or someone else) will chip in with the state-of-play for substituted rings. They were mentioned in an update but I didn't pay that much attention to it.
EDIT: Ok, I looked it up ... this update here says this:
We’re at a point now with our factory where actually getting the correct order fulfilled by them is proving to be almost impossible. With that in mind, to keep things moving, some rings that had unique color options have had alternative colors supplied. For example if your order was a Titanium Ring with Red and black inlay covers and we didn’t get sent this exact color combination, then we will have replaced your ring with the closest match. (For example Red and Transparent inlay covers.) If you aren’t happy with this ring you can always return it or request a replacement. We appreciate this isn’t ideal, but from the feedback we have had with sending out replacement rings, we feel it’s the best possible approach in these circumstances.
... and I'd guess your wood inlay is one of those affected. If you aren't happy, request a replacement.
Yea wood was an issue where the factory failed too many at QA.
NOT NFC Ring is something you should email email@example.com to fix, it's easy for us to fix that one :)
Invalid key, try again, I'm not sure on the fix for that! I think it's documented on the forum though!
just remove the tag and add it again, that should fix the invalid tag error