Google Wallet - adding all of my QR activity tickets

Instructions to add a QR activity pass to Google Wallet on Android

On your laptop or tablet: Open the activity ticket in whatever format - an email, pdf, jpg, png file, etc.
- this is key because you'll be using your phone's camera to take a photo of the ticket on your 2nd device - not a screenshot of the ticket on your phone (which isn't always possible for activity tickets, for security)

On your Android phone: (Sorry, I can't help with iPhone and Apple Pay, but perhaps someone else can)

• Open Google Wallet
• Click on the "+" sign (lower right) to bring up the Add to Wallet screen
• Click on "Everything Else" to add an activity ticket (this opens the phone's camera)
• Take a photo of the ticket - including all the details of the event time, date and location, and (critical) the QR code to be scanned at entry to your activity
• Click Done (or Retake, as needed)
• Wait while it processes ...
• Important: when processing finishes, edit the data as necessary, for example to change the date from dd/mm/yy to mm/dd/yy
• Click Add and view your pass as it now appears in Google Wallet, sorted by mm/dd/yy format (if that's your phone setting)

If you are able to take a screenshot of the activity ticket, you can follow the same steps except that instead of taking a photo on a 2nd device, you'll find the screenshot on your phone and add it that way.

But you can't always screenshot activity passes.

sounds like another tech tip for the October meeting - thanx

In case anyone reads this ....

It occurred to me, as I was glancing at all my shiny new Google Wallet tickets, that I made an error in judgment in revising all the dates to my own "mm/dd/yy" style. Not that I think the QR laser readers will care (they won't) but in the event that a human were to glance at a ticket, I've decided to enter all the dates in "dd Mmm yyyy" format so that it's (reasonably) clear to me and to readers in Europe.

I suppose you could even re-enter the date in the local language of the activity, but again, it's likely to be a QR reader, not a human, judging the ticket validity.

You can't "edit" the details of a ticket after you've added it, so I removed a few and added them back.

Unfortunately, I don't think Apple Wallet can do that. There are categories for adding Transit Cards, Debit and Credit cards, and a driver's license (or state ID) from seven states (unfortunately not MN), but there is no generic category for adding "Everything else." So unless the activity ticket/pass has a specific QR or button that allows it to be shared to Apple Wallet, you're out of luck.

I'm no Apple expert, but usually they're ahead of the game on tricks like this. So I had to research...

Is there an "Edit Passes" and then "Scan Code" option in Apple Wallet?

I found instructions but don't have an iPhone to try it:

https://qrcodedynamic.com/blog/how-to-add-a-qr-code-to-apple-wallet/

It’s definitely worth pursuing but these directions don’t work for me. The second step is Scroll down to Edit Passes. I don’t have that anywhere - either in Wallet or in Settings/Wallet.

Edit: I don’t think it’s possible without a secondary app. I am probably not willing to do that. For the ones where the issuer has not enabled Save to,AppleWallet, I save it to Files.

In answer to your original question about offline use, you could do a trial by putting your phone in Airplane Mode. I do know that Apple Wallet does not require data or WiFi to access passes (or credit cards) stored there.

I did read that you have to have a certain version of the Apple iOS. And I don't know what else may be required.

I did already confirm that my new Google Wallet passes worked fine in airplane mode, wifi off, no connectivity.

And I've got them the "old fashioned way" in Dropbox as backup.

I did read that you have to have a certain version of the Apple iOS. And I don't know what else may be required.

I have the most recent version; iOS 18, and it’s not working for me.

Hmmm, the only other thing I've found says "Verify that the QR code is designed for Apple Wallet."

If you are inclined, you could try a QR code that you already know can be added to Apple Wallet and see if you can re-add it using the manual scanning method. That would at least indicate whether it's a problem with a specific QR code or a problem with the process.

I realize that, at some point, it isn't worth the trouble.

ETA: I just realized that you said you can't even get to the step to add a new "everything else" type pass, so it doesn't really matter if the QR code is Apple compatible. Sorry about that!

Apple is very security conscious. It might have built only certain containers/paths for specific types of QR codes. As a programmer, "everything else" seems ripe for abuse.

Security firm:
https://usa.kaspersky.com/resource-center/definitions/what-is-a-qr-code-how-to-scan

[snip]

Are QR codes safe?
Attackers can embed malicious URLs containing custom malware into a QR code which could then exfiltrate data from a mobile device when scanned. It is also possible to embed a malicious URL into a QR code that directs to a phishing site, where unsuspecting users could disclose personal or financial information.

Because humans cannot read QR codes, it is easy for attackers to alter a QR code to point to an alternative resource without being detected. While many people are aware that QR codes can open a URL, they can be less aware of the other actions that QR codes can initiate on a user’s device. Aside from opening a website, these actions can include adding contacts or composing emails. This element of surprise can make QR code security threats especially problematic.

Verify that the QR code is designed for Apple Wallet.

And therein lies the problem. Apple is very specific in that it says if you can't use a QR code to get a ticket in Apple Pay, then to contact the merchant to make sure they support passes in the Wallet app. Generally, if it's not supported, then you can't add it. I tried several weeks ago to add the Warner Bros. Harry Potter tickets I bought to Apple Pay, and it does not work.