[French Rage]

Wait, I missed last week due to a family event, but I use Google Wallet on an Android, will that not work anymore?!

That's what I use. To check if you'll be able to get in, just go to your Google wallet and see if you have the "tap" logo on your tickets. Looks like  this )))) with each wave getting bigger.

I have a Samsung S8, so I'm not sure I have any tap-and-go functionality.  They were scanning bar codes earlier this year.  Did they just throw those machines away??

I know sometimes scanning the barcode was taking a few tries, but it didn't seem to affect the whole entry process significantly.

[French Rage]

Wait, I missed last week due to a family event, but I use Google Wallet on an Android, will that not work anymore?!

That's what I use. To check if you'll be able to get in, just go to your Google wallet and see if you have the "tap" logo on your tickets. Looks like  this )))) with each wave getting bigger.

I have a Samsung S8, so I'm not sure I have any tap-and-go functionality.  They were scanning bar codes earlier this year.  Did they just throw those machines away??

I know sometimes scanning the barcode was taking a few tries, but it didn't seem to affect the whole entry process significantly.

[82lsju]

It must be "NFC" (near field communication) that you have to turn on on your phone for tickets to work now.

Stanford's scanners have had the ability to work with either NFC or bar codes / QR codes for several years. I can't imagine why they want to start forcing NFC in the middle of a season.

I'm fairly sure it's possible to have a phone that still works fine but is too old to have NFC capability.

use of NFC started with this season as I've used it at all the games I have been to.  The still scan my e-parking pass QR code to get into lot 2

New ticket scanners will be deployed at entry gates, and "Tap and Go" mobile tickets will be used for all ticketed athletic events on The Farm. Once added to a smartphone's mobile wallet, these tickets will display a "Hold Near Reader" animation in place of a QR code or barcode. Fans will simply open their ticket within their smartphone's mobile wallet and position their device in close proximity to the ticket scanner to validate their ticket(s) for entry.

https://gostanford.com/news/2023/9/7/foo...-2023.aspx

[82lsju]

It must be "NFC" (near field communication) that you have to turn on on your phone for tickets to work now.

Stanford's scanners have had the ability to work with either NFC or bar codes / QR codes for several years. I can't imagine why they want to start forcing NFC in the middle of a season.

I'm fairly sure it's possible to have a phone that still works fine but is too old to have NFC capability.

use of NFC started with this season as I've used it at all the games I have been to.  The still scan my e-parking pass QR code to get into lot 2

New ticket scanners will be deployed at entry gates, and "Tap and Go" mobile tickets will be used for all ticketed athletic events on The Farm. Once added to a smartphone's mobile wallet, these tickets will display a "Hold Near Reader" animation in place of a QR code or barcode. Fans will simply open their ticket within their smartphone's mobile wallet and position their device in close proximity to the ticket scanner to validate their ticket(s) for entry.

https://gostanford.com/news/2023/9/7/foo...-2023.aspx

[French Rage]

Wait, I missed last week due to a family event, but I use Google Wallet on an Android, will that not work anymore?!

That's what I use. To check if you'll be able to get in, just go to your Google wallet and see if you have the "tap" logo on your tickets. Looks like  this )))) with each wave getting bigger.

I have a Samsung S8, so I'm not sure I have any tap-and-go functionality.  They were scanning bar codes earlier this year.  Did they just throw those machines away??

I know sometimes scanning the barcode was taking a few tries, but it didn't seem to affect the whole entry process significantly.

OK, apparently my phone does have it.  I just never used it because I don't believe in evil magic.  (I say this as a software developer.)

[French Rage]

Wait, I missed last week due to a family event, but I use Google Wallet on an Android, will that not work anymore?!

That's what I use. To check if you'll be able to get in, just go to your Google wallet and see if you have the "tap" logo on your tickets. Looks like  this )))) with each wave getting bigger.

I have a Samsung S8, so I'm not sure I have any tap-and-go functionality.  They were scanning bar codes earlier this year.  Did they just throw those machines away??

I know sometimes scanning the barcode was taking a few tries, but it didn't seem to affect the whole entry process significantly.

OK, apparently my phone does have it.  I just never used it because I don't believe in evil magic.  (I say this as a software developer.)

[82 Card]

It must be "NFC" (near field communication) that you have to turn on on your phone for tickets to work now.

Stanford's scanners have had the ability to work with either NFC or bar codes / QR codes for several years. I can't imagine why they want to start forcing NFC in the middle of a season.

I'm fairly sure it's possible to have a phone that still works fine but is too old to have NFC capability.

In the Android world, it doesn't have to be an old phone to not have NFC. For example Moto G Power 5G is a current model. No NFC capability. The pricier models tend to be the ones with NFC.

[82 Card]

It must be "NFC" (near field communication) that you have to turn on on your phone for tickets to work now.

Stanford's scanners have had the ability to work with either NFC or bar codes / QR codes for several years. I can't imagine why they want to start forcing NFC in the middle of a season.

I'm fairly sure it's possible to have a phone that still works fine but is too old to have NFC capability.

In the Android world, it doesn't have to be an old phone to not have NFC. For example Moto G Power 5G is a current model. No NFC capability. The pricier models tend to be the ones with NFC.

[CompSci87]

It must be "NFC" (near field communication) that you have to turn on on your phone for tickets to work now.

Stanford's scanners have had the ability to work with either NFC or bar codes / QR codes for several years. I can't imagine why they want to start forcing NFC in the middle of a season.

I'm fairly sure it's possible to have a phone that still works fine but is too old to have NFC capability.

In the Android world, it doesn't have to be an old phone to not have NFC. For example Moto G Power 5G is a current model. No NFC capability. The pricier models tend to be the ones with NFC.

Yikes. I was going to write "old / low end", but I assumed Stanford and their ticketing partner were sufficiently aware of the phone market that they wouldn't start insisting on NFC until almost everyone could be expected to have it.

Since that hasn't happened yet -- and it's years away if there are still current phones without NFC -- what a botch it was to not at least allow QR codes as an automatic fallback if your phone doesn't have NFC.

[CompSci87]

It must be "NFC" (near field communication) that you have to turn on on your phone for tickets to work now.

Stanford's scanners have had the ability to work with either NFC or bar codes / QR codes for several years. I can't imagine why they want to start forcing NFC in the middle of a season.

I'm fairly sure it's possible to have a phone that still works fine but is too old to have NFC capability.

In the Android world, it doesn't have to be an old phone to not have NFC. For example Moto G Power 5G is a current model. No NFC capability. The pricier models tend to be the ones with NFC.

Yikes. I was going to write "old / low end", but I assumed Stanford and their ticketing partner were sufficiently aware of the phone market that they wouldn't start insisting on NFC until almost everyone could be expected to have it.

Since that hasn't happened yet -- and it's years away if there are still current phones without NFC -- what a botch it was to not at least allow QR codes as an automatic fallback if your phone doesn't have NFC.

[PVTree]

It must be "NFC" (near field communication) that you have to turn on on your phone for tickets to work now.

Stanford's scanners have had the ability to work with either NFC or bar codes / QR codes for several years. I can't imagine why they want to start forcing NFC in the middle of a season.

I'm fairly sure it's possible to have a phone that still works fine but is too old to have NFC capability.

In the Android world, it doesn't have to be an old phone to not have NFC. For example Moto G Power 5G is a current model. No NFC capability. The pricier models tend to be the ones with NFC.

I have the Moto G stylus... Some 3 years old. Sounds like I may not have NFC capabilities.

[PVTree]

It must be "NFC" (near field communication) that you have to turn on on your phone for tickets to work now.

Stanford's scanners have had the ability to work with either NFC or bar codes / QR codes for several years. I can't imagine why they want to start forcing NFC in the middle of a season.

I'm fairly sure it's possible to have a phone that still works fine but is too old to have NFC capability.

In the Android world, it doesn't have to be an old phone to not have NFC. For example Moto G Power 5G is a current model. No NFC capability. The pricier models tend to be the ones with NFC.

I have the Moto G stylus... Some 3 years old. Sounds like I may not have NFC capabilities.

[CowboyIndian]

Sounds like I may not have NFC capabilities.

You've got to be at least as good as the NY Giants!

[CowboyIndian]

Sounds like I may not have NFC capabilities.

You've got to be at least as good as the NY Giants!

[Goose]

OK, here is what I got back from Stanford tickets:

When viewed in an online account, tickets delivered by Stanford have a barcode. Fans can swipe horizontally to view additional tickets, indicated by the “1/2” and two dots at the top of the screen in the screenshot below. The barcode in the screenshot is intentionally cropped. When these tickets are added to a mobile wallet, they are enabled as NFC tickets.

<screenshot>

Prior to the release of the Android 14 operating system this month, when Android users who did not have NFC enabled on their device added tickets to Google Wallet, those tickets displayed a QR code, which they were able to scan for entry.
 
After Android 14 was released, the QR code on these tickets was replaced by the “hex code” you referenced. Enabling NFC on the device and closing/re-opening the Google Wallet app converts the ticket into a NFC ticket that can be scanned for entry.
 
NFC is not available on some older Android devices, however, so unless Google reverts back to the previous code of displaying the QR code, the barcodes in the Stanford ticket account should be displayed for entry.
 
Based on other online threads (two of which are linked below), Google is aware of the issue and is working on a fix. We have asked the developers from our ticketing provider to reach out to Google as well so we can receive progress updates. We did not change systems or any setting in our system mid-season.

Stanford did not actually INTEND a change in the status quo ante. The revision to the Android system is currently being blamed for the issue. There are still some questions about the functionality. It appears that if you transfer the ticket to your wallet with NFC turned on, the QR code is forever gone. Why? Makes no sense. Also, it is unclear how one could "scan the barcode" if it is intentionally cropped. This also makes no sense.

It is also clear that the website describing the "mandatory change to NFC" is not correct. If Google had not introduced a "bug", people with no NFC capability could have gone right ahead with the QR code approach, despite what the website says. I am going to ask these questions, because I am still not sure how the ticket system is supposed to work.

UPDATE: Stanford tickets explanation of the process is wrong. The "QR" code is displayed when NFC is not enabled (or present). The "Tap and pay" graphic is displayed when NFC is on and the "QR" code is not displayed. Your ticket isn't altered when you put it in your wallet with NFC on. The display depends on the state of NFC in your phone. Obviously this is the way it SHOULD work, and it indeed does. If the Android display "bug" gets fixed, all is well for everybody. The question about "scan the barcode" remains however.

[Goose]

OK, here is what I got back from Stanford tickets:

When viewed in an online account, tickets delivered by Stanford have a barcode. Fans can swipe horizontally to view additional tickets, indicated by the “1/2” and two dots at the top of the screen in the screenshot below. The barcode in the screenshot is intentionally cropped. When these tickets are added to a mobile wallet, they are enabled as NFC tickets.

<screenshot>

Prior to the release of the Android 14 operating system this month, when Android users who did not have NFC enabled on their device added tickets to Google Wallet, those tickets displayed a QR code, which they were able to scan for entry.
 
After Android 14 was released, the QR code on these tickets was replaced by the “hex code” you referenced. Enabling NFC on the device and closing/re-opening the Google Wallet app converts the ticket into a NFC ticket that can be scanned for entry.
 
NFC is not available on some older Android devices, however, so unless Google reverts back to the previous code of displaying the QR code, the barcodes in the Stanford ticket account should be displayed for entry.
 
Based on other online threads (two of which are linked below), Google is aware of the issue and is working on a fix. We have asked the developers from our ticketing provider to reach out to Google as well so we can receive progress updates. We did not change systems or any setting in our system mid-season.

Stanford did not actually INTEND a change in the status quo ante. The revision to the Android system is currently being blamed for the issue. There are still some questions about the functionality. It appears that if you transfer the ticket to your wallet with NFC turned on, the QR code is forever gone. Why? Makes no sense. Also, it is unclear how one could "scan the barcode" if it is intentionally cropped. This also makes no sense.

It is also clear that the website describing the "mandatory change to NFC" is not correct. If Google had not introduced a "bug", people with no NFC capability could have gone right ahead with the QR code approach, despite what the website says. I am going to ask these questions, because I am still not sure how the ticket system is supposed to work.

UPDATE: Stanford tickets explanation of the process is wrong. The "QR" code is displayed when NFC is not enabled (or present). The "Tap and pay" graphic is displayed when NFC is on and the "QR" code is not displayed. Your ticket isn't altered when you put it in your wallet with NFC on. The display depends on the state of NFC in your phone. Obviously this is the way it SHOULD work, and it indeed does. If the Android display "bug" gets fixed, all is well for everybody. The question about "scan the barcode" remains however.

[82 Card]

I have the Moto G stylus... Some 3 years old. Sounds like I may not have NFC capabilities.

Could go either way, depending on exact model:

The Moto G Stylus 2020 does not have NFC according to PC Magazine review.
https://www.pcmag.com/reviews/moto-g-stylus

The Moto G Pro (with stylus), also sold in 2020, does have NFC.
https://www.gsmarena.com/moto_g_pro-review-2138.php

The current 5G version of the Moto G Stylus does have NFC but the current 4G version does not.

[82 Card]

I have the Moto G stylus... Some 3 years old. Sounds like I may not have NFC capabilities.

Could go either way, depending on exact model:

The Moto G Stylus 2020 does not have NFC according to PC Magazine review.
https://www.pcmag.com/reviews/moto-g-stylus

The Moto G Pro (with stylus), also sold in 2020, does have NFC.
https://www.gsmarena.com/moto_g_pro-review-2138.php

The current 5G version of the Moto G Stylus does have NFC but the current 4G version does not.

[M T]

Did “intentionally cropped” refer just to the screenshot included in the response , so you couldn’t use that particular screenshot by to gain access

[M T]

Did “intentionally cropped” refer just to the screenshot included in the response , so you couldn’t use that particular screenshot by to gain access

[Goose]

Did “intentionally cropped” refer just to the screenshot included in the response , so you couldn’t use that particular screenshot by to gain access

No, apparently. My phone does exactly the same thing. If there was a scroll bar, you could scroll it up and expose the bar code "full size". I am unsure if they believe you can use the "cropped" version to get in. I am asking them this exact question.

[Goose]

Did “intentionally cropped” refer just to the screenshot included in the response , so you couldn’t use that particular screenshot by to gain access

No, apparently. My phone does exactly the same thing. If there was a scroll bar, you could scroll it up and expose the bar code "full size". I am unsure if they believe you can use the "cropped" version to get in. I am asking them this exact question.

[CompSci87]

Here's what I see on my OnePlus 6 phone with Android 11, Google Play last updated 9/1/23, OxygenOS 11.1.2.2. My phone has NFC.

If I turn on NFC, Google Wallet displays the NFC symbol )))) above the ticket. If I turn it off, Wallet displays a hex number in the ticket where the QR code should be. I tried this with my WBB ticket and my football ticket.

With my WBB parking pass (hmm, not sure why I have one of those this year!), I get a hex number either way. Presumably that's because Stanford doesn't have NFC capable scanners at the parking lot.

So this is a bug that needs fixing.

[CompSci87]

Here's what I see on my OnePlus 6 phone with Android 11, Google Play last updated 9/1/23, OxygenOS 11.1.2.2. My phone has NFC.

If I turn on NFC, Google Wallet displays the NFC symbol )))) above the ticket. If I turn it off, Wallet displays a hex number in the ticket where the QR code should be. I tried this with my WBB ticket and my football ticket.

With my WBB parking pass (hmm, not sure why I have one of those this year!), I get a hex number either way. Presumably that's because Stanford doesn't have NFC capable scanners at the parking lot.

So this is a bug that needs fixing.

[PVTree]

My friend also has issues with NFC and his phone. He does have the parking pass, and the bar code was visible for it.

We're supposing that the parking attendants don't have NFC capable scanners.

[PVTree]

My friend also has issues with NFC and his phone. He does have the parking pass, and the bar code was visible for it.

We're supposing that the parking attendants don't have NFC capable scanners.

[CompSci87]

If I view the parking pass in the Stanford Cardinal app, I do see a bar code (not a QR code). It's when I view it in Google Wallet that I see a hex number instead of a bar or QR code. 

The same is true with my tickets if NFC is turned off.

There's a slight difference in that with the parking pass, the bar code is fully visible in the Stanford Cardinal app, but with the tickets, it's scrolled partly offscreen and can't be moved onscreen.

[CompSci87]

If I view the parking pass in the Stanford Cardinal app, I do see a bar code (not a QR code). It's when I view it in Google Wallet that I see a hex number instead of a bar or QR code. 

The same is true with my tickets if NFC is turned off.

There's a slight difference in that with the parking pass, the bar code is fully visible in the Stanford Cardinal app, but with the tickets, it's scrolled partly offscreen and can't be moved onscreen.

[Goose]

If I view the parking pass in the Stanford Cardinal app, I do see a bar code (not a QR code). It's when I view it in Google Wallet that I see a hex number instead of a bar or QR code. 

The same is true with my tickets if NFC is turned off.

There's a slight difference in that with the parking pass, the bar code is fully visible in the Stanford Cardinal app, but with the tickets, it's scrolled partly offscreen and can't be moved onscreen.

Here is the reply I got regarding the bar code.

There is a barcode back up option for all tickets. When the ticket is displayed in your online account, the full barcode is displayed. I cropped the image intentionally in the screenshot I shared since it is an active barcode and I did not want the full image displayed for you (or anyone else) to use. However, any fan can open their tickets from the Tickets section in their online account and scan those barcodes for entry. No NFC required.
 
If you are seeing a cropped version of the barcode in your account, please do share a screenshot with us. We have seen this with other fans and have found that reducing the font size on the device has allowed for the full barcode to display on the screen. It would be nice if the ticket image was more dynamic so it fully displayed regardless of device settings. We will check-in with the developers on that.

At least in my case (using Firefox), reducing the font size slightly did get the bar code from the ticket to display. I am going to try this approach at Big Game to prove it works.

[Goose]

If I view the parking pass in the Stanford Cardinal app, I do see a bar code (not a QR code). It's when I view it in Google Wallet that I see a hex number instead of a bar or QR code. 

The same is true with my tickets if NFC is turned off.

There's a slight difference in that with the parking pass, the bar code is fully visible in the Stanford Cardinal app, but with the tickets, it's scrolled partly offscreen and can't be moved onscreen.

Here is the reply I got regarding the bar code.

There is a barcode back up option for all tickets. When the ticket is displayed in your online account, the full barcode is displayed. I cropped the image intentionally in the screenshot I shared since it is an active barcode and I did not want the full image displayed for you (or anyone else) to use. However, any fan can open their tickets from the Tickets section in their online account and scan those barcodes for entry. No NFC required.
 
If you are seeing a cropped version of the barcode in your account, please do share a screenshot with us. We have seen this with other fans and have found that reducing the font size on the device has allowed for the full barcode to display on the screen. It would be nice if the ticket image was more dynamic so it fully displayed regardless of device settings. We will check-in with the developers on that.

At least in my case (using Firefox), reducing the font size slightly did get the bar code from the ticket to display. I am going to try this approach at Big Game to prove it works.

[CompSci87]

I get the partly cropped barcode for some tickets in the Stanford Cardinal app, not a web browser. However, setting the system font size to the smallest possible and restarting the app does work around it.

[CompSci87]

I get the partly cropped barcode for some tickets in the Stanford Cardinal app, not a web browser. However, setting the system font size to the smallest possible and restarting the app does work around it.