search

jakehilborn / debbit

Automate spending requirements for high interest checking accounts / credit cards
https://jakehilborn.github.io/debbit/
MIT License
261 stars 29 forks source link

Error: Clicked "Place your order" button, but unable to confirm if order was successful. When it was successful #71

Open trilogy-09 opened 2 years ago

trilogy-09 commented 2 years ago

Hello, I am getting the following message on 2.1.2 on windows 10.

It says it cant confirm whether the purchase was successful when it was successful. I understand why it would stop continuing to purchase, but it is working AFAIK.

Hope this helps.

ERROR: 2021-09-28 22:34:08,336 Clicked "Place your order" button, but unable to confirm if order was successful. INFO: 2021-09-28 22:34:09,267 Successfully sent failure report for developer email to debbit.failure.notify@gmail.com ERROR: 2021-09-28 22:34:10,074 Unable to verify XXX_debbit_card_amazon_gift_card_reload purchase was successful. Just in case, NOT SCHEDULING MORE XXX_debbit_card_amazon_gift_card_reload. Stop and re-run debbit to try again.

robotomeister commented 2 years ago

There's a pull request by bjhiltbrand to fix this that adds an extra condition to check for.

bjhiltbrand commented 2 years ago

The PR that fixes this was pulled into master and is now waiting for a release to be built (hopefully tomorrow). This issue can be closed.

GlenNicholls commented 2 years ago

Does anyone have a status update on this?

robotomeister commented 2 years ago

The pull request was merged but a new build with executables has not been released. If you are technically inclined, you can try these instructions to run the code from source which is what I have been doing.

RBJervey commented 2 years ago

Any idea if there's a new release coming soon? The purchases are successful and it takes me less time to open Debbit and have it do them than to manually do them in Amazon but it'd be nice to have this work on the backend again without my focusing on it.

jakehilborn commented 2 years ago

Debbit v2.1.3 has been released which fixes this issue. It's actually been fixed for a while now from that PR but I haven't gotten around to putting out a new release. I wrote some scripts to do the release for me so it should be a lot easier to push out releases faster from here on out.