Is anyone having success with their Apple Watch on the tube? I’m pretty much always getting a read error unless I position it perfectly on top of the reader. Surprisingly it was fine with my Series 1 but haven’t had success ever since I upgraded (to series 3 and now 4). I’m suspecting it might be my Milanese loop strap that’s interfering (although none of the other readers seem to mind, only the big round TfL readers hate it).
My iPhone X worked absolutely fine with Express Transit but now I’ve got an Xs Max it fails maybe 50% of the time I’ve not figured out the position. My X you could be pretty careless putting it on readers.
Yes, I’ve been using mine (Series 4 with a silicon band) non-stop for around three weeks now, and not had any errors.
2 Likes
I found some readers are not working yet. For example the 2 on the right going into Shoreditch High Street always report an error on mine. I started using the other ones and I solved that problem. 
Do you mean they’re not working for Express Transit, or with Apple Pay in general? There’s one in Clapham North (the middle one on exit) that don’t work with Apple Pay full stop.
1 Like
Just with Express Transit in my experience
Interesting. My own experience to date has been that they either work with both or none. I’ll keep trying other gates, and see what happens.
After trying last Monday and it not working on a 
, I thought I’d try again this morning.
Worked fine tapping in to my local National Rail station (Zone 3).
However, two failed attempts at exiting at Euston Square and lots of annoyed people behind me at the hate line*** meant I defaulted to using my card to exit.
This’ll be a fun one to sort out with TfL - I’m hoping my debit card journey will autocomplete so it’s just one horrendous fare I’m left with today 
Don’t think I’ll be using this again!
Edit:
*** hate line should read ‘gate line’ but this was probably quite accurate.
Did it not work manually authenticating Apple Pay?
1 Like
Is this working for everyone now?
I just linked up my card, and haven’t managed to get it to work a single time. I’ve had a couple of instances where the reader has refused to let me through, and then another couple of times where it has let me through, but then when exiting, it doesn’t recognise my phone. In those instances, I’ve had to touch out using touch ID, but then tfl have charged me for an ‘incomplete journey’, which suggests it never worked upon entry (but still opened the barrier).
Just wondered if I’m the only one have problems with this!
Worked perfectly from day 1 here. Actually, day -1/-2, thanks to the rumour mill on this forum.
1 Like
Have you registered your cards on the TfL website/app - that will enable you to see what has registered and what hasn’t
It’s been working everywhere for me since late last year. Have you followed the full guidance?
1 Like
Thanks - that’s good to hear it’s working well for everyone else!
I’ve linked my card to my account, and it seems 2 of them were from when I travelled from Monument to Angel, and the other from Essex Road. The latter is a mainline station, so possibly the oyster readers don’t work at mainline stations with ET?
Zero issues here. Not a bit!
I notice in one of your earlier posts that you mention authenticating through Touch ID, which means your device is likely at least a couple of years old. What iOS version are you using? Does your device support iOS 12.3 or above? If not, that would be the issue.
Good theory, but it’s an iPhone 8 and on 13.3, so should be fine.
Maybe I’ve just been unlucky. Has it been working for anyone at mainline stations where they don’t have a barrier?
I’m not sure which services go through that station, but I’m guessing if it’s not London Overground or TFL Rail, it possibly won’t support it as it won’t be running the latest contactless updates from TfL, the way it took ages for the bits of the network which weren’t managed by TfL to get PAYG and Contactless payments to work. The Apple website shows the roundels for TFL services specifically.
I guess if it doesn’t work for you that’s the answer.
Ah I see - that would explain the problem with one of the stations. thanks