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

Missed the shot with Book Token #119

Closed
htlorenzen opened this issue May 11, 2023 · 3 comments · Fixed by #122
Closed

Missed the shot with Book Token #119

htlorenzen opened this issue May 11, 2023 · 3 comments · Fixed by #122

Comments

@htlorenzen
Copy link

I have been testing my bot after getting it setup. I have read other closed threads with this same issue, and made the proper changes, but still no success (on venues with open slots). My bot gets to the point where it sees the reservation and attempts to book it, provides a book token, and still says it misses the shot. Other users said to add a header for both the get and post commands, which I have already done. Are there any other issues that could be causing this?

@Alkaar
Copy link
Owner

Alkaar commented May 12, 2023

I just pushed a fix 👉 #122. Seems like the Referer header is now required as well.

@Alkaar Alkaar linked a pull request May 12, 2023 that will close this issue
1 task
@draconics37
Copy link

draconics37 commented May 23, 2023

I'm still running into the same issue even after pulling in this new change (confirming even after recloning), even after triple checking (1) both authorization parameters, (2) the venue ID, and (3) that there exists open reservations for the selected date/times. It's showing me the same pattern of output described in this issue, with the bot showing a book token and still showing a Missed the shot/Reservation no longer available error. Please let me know if there's anything else I should check on here configuration-wise, or if some other fix is required here.

Edit: seems like this has already been flagged at #120

@Alkaar
Copy link
Owner

Alkaar commented Jun 9, 2023

Going to close this out and have everyone follow #120 for continued discussions

@Alkaar Alkaar closed this as completed Jun 9, 2023
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

Successfully merging a pull request may close this issue.

3 participants