Created
April 23, 2026 17:57
-
-
Save ahoward/0d3f4fef7ab9a242b081a0ebfe538486 to your computer and use it in GitHub Desktop.
ENT-357: Owner Vehicles Not Displaying in Patrol App — Investigation Summary
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| # ENT-357: Owner Vehicles Not Displaying in Patrol App | |
| ## TL;DR | |
| Backend is fine. Bug is in the patrol app. | |
| ## What We Found | |
| **Plate: 28A760M** (the Volvo, permanent owner registration) | |
| - Valid owner permit via `contacts_owners_passes/136` | |
| - Date range: 1970–2038 (permanent) | |
| - `Permit.permitted?` returns a valid record | |
| - LPR backend correctly returns `hitt` | |
| **Plate: VWL3627** (F&F workaround pass the owner created today) | |
| - Valid guest pass, expires 2026-04-26 | |
| - Created as a workaround — confirms owner knew the real one wasn't working | |
| ## The Problem | |
| The patrol app is not recognizing owner-type passes. The `passId` format | |
| for owner passes is `contacts_owners_passes/136` vs the standard `passes/XXXX` | |
| for guest/F&F passes. The patrol app likely filters or ignores the | |
| `contacts_owners_passes` format. | |
| ## What Needs to Be Fixed | |
| - Patrol app pass lookup / display logic for `contacts_owners_passes` passId format | |
| - NOT an lpr-rails backend issue | |
| ## Action | |
| Assigned to patrol app team for investigation. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment