search

mclear / NFC_Ring_Control

NFC Ring Control App
Apache License 2.0
93 stars 28 forks source link

Issue with Nokia Lumia 1520 and Lumia 925 #19

Closed wooshping closed 10 years ago

wooshping commented 10 years ago

I have downloaded the latest version of NFC Ring Control to a Lumia 1520 and Lumia 925. Both devices are running latest available software versions. Steps to failure are as follows ... Download App Start up App Hit Create Select Twitter Add @wooshping Hit next Get warning about sweet spot locator Hit OK Place phone over tags and hear audible NFC ringing sound continuously After 4 or five attempts hit Finish Confirm that Tag is still blank.

Inlays we are trying to use are Wet Ultralight 1K chips (ready and able to write to using other apps) NTAG 203 on metal tags (ready and writable to from other apps) Standard NTAG203 - same as above

This is identical for both devices.

JohnMcLear commented 10 years ago

You didn't get an alert saying "Woohoo your ring is written?" Oh... Do me a test.. Try to write a URL to the tag using another app then try to use our software.. Afaik on WP we listen for NDEF URI records because WP doesn't properly support other records, it could be that write event isn't firing because it hasn't detected a URL. FWIW the NFC Ring comes with a URI written by default..

wooshping commented 10 years ago

Hi John. OK my bad (sort of) seems like the issue is with the UL chips. Can't write to them using the 1520. If I try the UL first and then go straight to the NTAG203 it doesn't work. If I exit the app and relaunch and then go straight for the NTAG203 it writes it OK. Go figure....? So the UL seem to be an issue which is strange because I have been writing successfully to them for months and months using the 925.

wooshping commented 10 years ago

Hi John. Update. You were right. I wrote a URL to the UL tag and this time I did get the Woohoo message. However it still doesn't work. When I go to write the tag I get a prompt from the NFC system that someone is trying to share a website with me. If I cancel that message I then see the Wohooo confirmation message (which was hidden by the NFC message). If I try and read the tag the original URL is still programmed to it, and not the twitter handle that I was trying to program to it. Make sense? I can send screenshots if you are interested?

JohnMcLear commented 10 years ago

I will double check here before you send through screenies, PS are you running latest version of the app with the new branding etc? It only got approved today so you might be due an update?

wooshping commented 10 years ago

Yep. Latest version with branding. Also BTW - When I tell the app where the sweetspot is the app just sits there, with the red dot on the screen, so not sure if it is submitting it or not - and a bit of a dead end from a UI perspective. :-) Cheers.

JohnMcLear commented 10 years ago

Good spot will review that too :) +1

JohnMcLear commented 10 years ago

Peep http://youtu.be/Sovw3xjOFzM in an hour or so, my net SUCKS

JohnMcLear commented 10 years ago

Got some fixes up for this, peep the video too.. I'm gonna try merge in some "Help" pages too which should help out with stuff like this.. Hopefully get an update built over the weekend and published early next week, usual workflow on WP is: day 1 - bug report day 1 - fix day 2/3 - waiting for enough fixes/commits to make a push to store worthwhile day 4 - paperwork day 5 - publish update day 10 - receive rejection day 10 - republish with whatever MS ask for day 14 - receive acceptance

With each push to we make to MS store we have to fill out some paperwork so it's a bit time consuming. Will keep you posted :)

JohnMcLear commented 10 years ago

Resolved, waiting on MS to publish :)

wooshping commented 10 years ago

Amazing! Many thanks!! :-)