Open CoocooFroggy opened 9 months ago
Disney has changed the format of their dining json which is causing this issue.
Even moving past this, they have changed so now authentication is required to see reservation availabilty. Kind of debating how much sense it makes to still move forward with this given this would now require users to enter their Disney credentials for it to work.
I see—would any dummy account work, if users don't want to store their actual credentials to run the program? Although I understand if there's a lot of work involved in implementing authentication
I'm fairly sure a dummy account would suffice
Anyone planning this work for the future? I may try to take this up later this Spring but wanted to know if this project was dead or not...
I was trying to figure out the authentication for new API from the network tab/postman proxy but could not figure out how to use the google captcha stuff...
If dining reservations are protected by reCAPTCHA, we're probably out of luck (unless we can find a workaround endpoint).
There are captcha solving services which cost money; but if every availability refresh costs a token, it's going to get very expensive very quickly.
Although this might not be what you're implying? As I feel it would be a hassle for mobile devices to make dining reservations if every request is reCAPTCHA checked.
Describe the bug A clear and concise description of what the bug is.
Version 0.2.9.1
To Reproduce Steps to reproduce the behavior: