Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Clipper single-use tickets throw TagLostException in v2.9.38 #383

Closed
iangcarroll opened this issue May 9, 2019 · 2 comments
Closed

Clipper single-use tickets throw TagLostException in v2.9.38 #383

iangcarroll opened this issue May 9, 2019 · 2 comments

Comments

@iangcarroll
Copy link

Please read the guidelines for contributions (CONTRIBUTING.md) before submitting new issues to this tracker. Failure to adhere to these guidelines may cause offense.

Description of the issue

Clipper single-use tickets fail to read in v2.9.38, throwing a TagLostException on my Pixel 3. I'm doing some research on these and have plenty of dumps if needed.

For card-specific issues

  • Name of the card type: Clipper (single-use)
  • Name of the transit operator: Clipper
  • Location: San Francisco, CA

For all issues reading a currently supported card format (eg: balance shown is incorrect), please export a card dump from Metrodroid and email it to me privately.

Steps to reproduce

  1. Scan a Clipper single-use ticket (only tested with Muni-issued ones).

Expected behaviour

Card reads, as it does in v2.9.37.

Actual behaviour

TagLostException every time.

Workarounds (if any)

Logs

Generate a bug report ZIP using the instructions here: https://developer.android.com/studio/debug/bug-report.html

Please do not attach it to this issue. You may be asked for a copy later via private email.

Details from About screen:

  • Version:
  • Model: Pixel 3 (blueline)
  • Manufacturer: Google (google)
  • Android OS version: 9 (PQ2A.190405.003)
  • NFC: enabled
  • MIFARE Classic: not supported
@phcoder
Copy link
Collaborator

phcoder commented May 10, 2019

Try #384

@micolous
Copy link
Collaborator

This will be fixed in v2.9.40.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants