Did you have your ticket in the Apple wallet or the DB App? I have found that DB Scanners don’t like the wallet version.
When it wasn't scanning and I took my phone off the scanner, I briefly glimpsed the Apple Pay screen before it animated away, so I realised I was "holding it wrong", and was able to get it to scan by holding it at a different angle to keep the NFC sensor at the top of the phone away from reader, but I can imagine a less technically minded user than myself might have serious problems.
I don't know anything about the scanner or NFC standards used by this system, sorry.
It took me a second to realize you weren't talking about the NFC chip, which is codenamed Stockholm ;)
Same flawed workflow. Show QR to scanner => not work => check phone on apple pay mode with credit cards => repeat => ask the (human) controllers.
You can ping me @ lucas@concpt.io
If Apple wants feedback from its developers, it should try actually listening to all of them, not just the ones that make enough noise on social media.
(I'm assuming the parent comment is from someone at Apple. If not, my point still stands in general.)
This isn’t to say HN is a good replacement for a proper support channel, but sometimes you need a little help. These are big companies, so these small issues (for Apple) don’t always make it to the right team. The parent poster here isn’t even the dev of the app in question. How are they supposed to know where to report that?
This is very handy in Chicago if you are making a single leg journey. Due to Apple Pay’s privacy architecture it can’t recognize transfers and always charges full fare.
I don't think this is the case—in London, I'm pretty sure you can pay with Apple Pay and have your fares "capped" (so you never pay more than the price of a full-day ticket). You can also set up an account with your card number (the one on your physical card) and view any recent journeys you've made.
The card number of a given card on a given device does not change between taps for Apple Pay. Otherwise, tapping for refunds would not work, among other things.
But I wonder how much 'normal' Apple consumers realize how shoddy some of that custody really is.
I bet your customers blamed you for that bug, not Apple?
As the creator, notify your users about it and there you can blame Apple as long as you want. But if the users are not notified, they don't really know that the creators are waiting for Apple.