Never goes to the next page #24
Comments
|
Will take a look when I get a sec. Seems to be related to #23 |
|
I'm sorry, was never able to reproduce this. I have two guesses though. Did you minimize the window? That causes it to break. The other possible culprit is you need to enable two factor authentication? |
|
Neither of those are the case. The window is not in the foreground, but is
not minimized, and it happens every time.
…On Sat, Feb 23, 2019 at 6:55 PM Jared Chapiewsky ***@***.***> wrote:
I'm sorry, was never able to reproduce this. I have two guesses though.
Did you minimize the window? That causes it to break. The other possible
culprit is you need to enable two factor authentication?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#24 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AA2HyTfbprW9oIZXAeNS8X2-S-gcjqT4ks5vQf8UgaJpZM4bN_n5>
.
|
|
One thing I notice is that my chromium doesn't use its entire window? |
|
Very strange. I was just using it and even did a release to fix #23 and #19 , for which I did lots of testing and let it run across multiple pages mutiple times and didn't have a problem. Maybe after updating to latest version, if it's still happening, could you record a video or get a screen grab on the page it is getting stuck on? Maybe the pagination buttons aren't rendering for some weird reason? The chromium window size is normal (though I honestly don't know why it does that). |
|
|
|
uhhh, you should probably delete that image, and change your amazon credentials!!! |
|
I'm really stumped. I just tried it again, using the CLI like you pictured, and it seems to be working fine. I'm really sorry you are having problems! If you can figure out the problem or can somehow better capture it I will gladly dig into it further. ¯_(ツ)_/¯ |
|
How would I get the perfect capture for you? |
|
I deleted your comment because the image you posted contained your amazon credentials (as I tried telling you), probably not something you want to share with the world! It's interesting that in the second screenshot you posted there were a bunch of "already entered" logs, which means the script did go into those giveaways? So it's working some of the time? I guess what I'd need at this point is something that shows how I can reproduce the problem. Or, something that showed the "why" behind it so I could take a shot in the dark at least. Maybe do some digging using chrome dev tools to show if certain elements the script is expecting don't exist? Right now I don't think there is anything else I can do at my end.... |
|
I changed the password, have no fear. I'm not sure how I can provide more
steps. It does the first 20'sh entries on a given page, then fails to do
5'sh more, then stops.
…On Mon, Feb 25, 2019 at 7:36 AM Jared Chapiewsky ***@***.***> wrote:
I deleted your comment because the image you posted contained your amazon
credentials (as I tried telling you), probably not something you want to
share with the world!
It's interesting that in the second screenshot you posted there were a
bunch of "already entered" logs, which means the script did go into those
giveaways? So it's working some of the time?
I guess what I'd need at this point is something that shows how I can
reproduce the problem. Or, something that showed the "why" behind it so I
could take a shot in the dark at least. Maybe do some digging using chrome
dev tools to show if certain elements the script is expecting don't exist?
Right now I don't think there is anything else I can do at my end....
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#24 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AA2HyT22FMygHeF-vS8IbF3lNyWbydKNks5vRAL6gaJpZM4bN_n5>
.
|
|
Im also getting this error, but it happens at number 20, without fail. |
|
I published a new release that might fix this issue. I say might as I still was not able to duplicate it, but I found something that might have been the culprit. Please upgrade and give it another shot. |
|
|
|
sigh, I have no idea. It's a riddle, wrapped in a mystery, inside an enigma. |
|
I had the same problem when I did the installation. I then cloned it and it worked fine. |
|
How do I do that?
…On Thu, Feb 28, 2019 at 2:44 PM mistergregg ***@***.***> wrote:
I had the same problem when I did the installation. I then cloned it and
it worked fine.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#24 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AA2HydOEyOwf-7Yx7VtqQ3yIPdPADL8tks5vSFu0gaJpZM4bN_n5>
.
|
|
Hit the green clone or download In the extracted folder navigate to that folder in cmd |
|
Huh, wow, it seems to be working! Thanks.
…On Thu, Feb 28, 2019 at 3:54 PM mistergregg ***@***.***> wrote:
Hit the green clone or download
Extract it somewhere
In the extracted folder
Edit .env.example put your user and pass then save as .env
navigate to that folder in cmd
npm install
npm start
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#24 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AA2Hycj7Cd6c4gWoBOBfVq7Qd9iERZkkks5vSGwsgaJpZM4bN_n5>
.
|
|
finally got around to trying to clean install it globally and run it the gg command. Still couldn't duplicate the problem. 🤷♂️ |
|
Closing this ticket as was never able to duplicate and sounds like you found a work around. |
giveaway 18 did not exist?
giveaway 19 did not exist?
giveaway 20 did not exist?
giveaway 21 did not exist?
giveaway 22 did not exist?
giveaway 23 did not exist?
giveaway 24 did not exist?
{ TimeoutError: waiting for selector "ul.a-pagination li:last-child" failed: timeout 30000ms exceeded
This happens every time, no matter the page. Then the entire process stops.
The text was updated successfully, but these errors were encountered: