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

Backend - Bug Fix - Drivers Unable to Accept Voter Match #418

Open
PamelaJohn opened this issue Nov 4, 2018 · 4 comments
Open

Backend - Bug Fix - Drivers Unable to Accept Voter Match #418

PamelaJohn opened this issue Nov 4, 2018 · 4 comments

Comments

@PamelaJohn
Copy link
Collaborator

PamelaJohn commented Nov 4, 2018

Upon receiving notification of a voter match, some drivers report they are unable to accept the match.

Driver 1 reports success accepting the match when logged in via computer, but unable to accept the match on their mobile device, making it difficult for him to accept new ride requests while driving in the field on Election Day.

Driver 2 reports inability to accept voter match from iPhone.

Driver 3 reports inability to accept voter match from mobile or PC using IE, Firefox, and Chrome.

Thank you!

@PamelaJohn PamelaJohn changed the title Backend - Bug Fix - Drivers Unable to Accept Voter Match via Mobile Backend - Bug Fix - Drivers Unable to Accept Voter Match Nov 4, 2018
@jkbits1
Copy link
Collaborator

jkbits1 commented Nov 4, 2018

@PamelaJohn thanks for clear descriptions. The emails (and texts, I think) contain a link to the self-service portal. It would be interesting to hear whether the self-service works on mobile devices - it is more likely to work.

Don't share it here, but do we have the details of the drivers?

Driver 3 sounds like another issue, but maybe leave it in your comment in case it's related.

The issue may relate to this issue voteamerica/backend#188 if so, there isn't a quick solution to this

@PamelaJohn
Copy link
Collaborator Author

PamelaJohn commented Nov 4, 2018

Hi @jkbits1, in answer to your questions:

LINKS
Driver 2 reports inability to access the link via SMS and ultimate success accepting the match via the email access link.

Driver 2 also reports a workaround for Login Problems:

Sometimes the carpoolvote login asks me for reference number and phone number (which does not work, I put in reference number and it never works) and sometimes just the phone number is asked for and that works fine.

Let me know if you'd like me to create a new issue for the Login issue.

DRIVER DETAILS
Driver 1 details are in the database. Status "Match Proposed".
Driver 2 details are in the database. Status is "Match Confirmed".
Driver 3 details are in the database. Status is "Cancelled".

Thank you for everything!

@jkbits1
Copy link
Collaborator

jkbits1 commented Nov 5, 2018

@PamelaJohn thanks for the updated details. Here's some feedback on those:

Driver 2 - that does sound like the iPhone is preventing the links working due to spam concerns (as in the related issue). Thanks for reporting their work-around - this will happen with the login if they don't put in the reference number correctly. That's not so hard to do (there are trade-offs involved). When just the phone number is requested, the correct reference has been provided automatically by the link that was clicked.

Driver 3 - if that driver was cancelled, then any previous links to matches will not work. Although, perhaps they cancelled after the problems.

General notes about the system

  1. the system provides a limited response when someone tries to accept a match that’s been confirmed by another rider. It’s not a failure and causes no new issues – the system has received the request but the driver has missed out on this match. Quite possibly some of the reported mobile errors are this issue. If we take a note of the driver, we can look at the operator page and work out the situation.

  2. if drivers contact us, they can be matched by an operator. That should work in all cases.

@jkbits1
Copy link
Collaborator

jkbits1 commented Nov 5, 2018

@PamelaJohn I'll remove the high priority label as there is no immediate action to take

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

No branches or pull requests

2 participants