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

log in using cookies for the "normal" mod #111

Open
shishiawase opened this issue Feb 8, 2024 · 13 comments
Open

log in using cookies for the "normal" mod #111

shishiawase opened this issue Feb 8, 2024 · 13 comments

Comments

@shishiawase
Copy link

When you log in to the "safe" mod using cookies, everything works. It doesn't work with the "normal" mod.

headless: True
Screenshot

@Yudaotor
Copy link
Owner

Yudaotor commented Feb 8, 2024

shows "The cookies login failed, please go to the browser to log in manually and try again."

@shishiawase
Copy link
Author

shows "The cookies login failed, please go to the browser to log in manually and try again."

I've tried it 3 times)

@Yudaotor
Copy link
Owner

Yudaotor commented Feb 8, 2024

shows "The cookies login failed, please go to the browser to log in manually and try again."

I've tried it 3 times)

are u select "stay singned in"?

@shishiawase
Copy link
Author

shows "The cookies login failed, please go to the browser to log in manually and try again."

I've tried it 3 times)

are u select "stay singned in"?

yeap, it shows this problem even when you log in successfully in safe mode
Снимок

@Yudaotor
Copy link
Owner

Yudaotor commented Feb 8, 2024

shows "The cookies login failed, please go to the browser to log in manually and try again."

I've tried it 3 times)

are u select "stay singned in"?

yeap, it shows this problem even when you log in successfully in safe mode Снимок

that is meaningless.nvm

@shishiawase
Copy link
Author

Logically speaking, if logging in to safe mode is successful, then it should be successful in normal mode and everything is fine with cookies

@Yudaotor
Copy link
Owner

Yudaotor commented Feb 8, 2024

Logically speaking, if logging in to safe mode is successful, then it should be successful in normal mode and everything is fine with cookies

this "cookies button" is not the same thing like cookies with login.so it will never matter.just igore

@shishiawase
Copy link
Author

Logically speaking, if logging in to safe mode is successful, then it should be successful in normal mode and everything is fine with cookies

this "cookies button" is not the same thing like cookies with login.so it will never matter.just igore

I understood that. But the problem remains, the normal mod does not log in with cookies when everything is fine in the save.

@shishiawase
Copy link
Author

Now I have entered the normal mod using cookies, but headless was set to False. When headless: True and you try to log in using cookies, it doesn't work.
1
2

@shishiawase
Copy link
Author

shishiawase commented Feb 8, 2024

I started logging in debug mode in the python version. I get a response with code 404 on the button.osano-cm-accept-all element

when I run in headless: true with cookies

2024-02-08 20:54:13,001 DEBUG: Remote response: status=404 | data={"value":{"error":"no such element","message":"no such element: Unable to locate element: {"method":"css selector","selector":"button.osano-cm-accept-all"}\n (Session info: chrome=121.0.6167.161)","stacktrace":"\tGetHandleVerifier [0x00471673+52979]\n\t(No symbol) [0x003F7961]\n\t(No symbol) [0x002DDD3D]\n\t(No symbol) [0x00315FBB]\n\t(No symbol) [0x003160FB]\n\t(No symbol) [0x0034CF92]\n\t(No symbol) [0x00334534]\n\t(No symbol) [0x0034B3FE]\n\t(No symbol) [0x00334286]\n\t(No symbol) [0x0030C063]\n\t(No symbol) [0x0030CECD]\n\tGetHandleVerifier [0x00788D83+3294723]\n\tGetHandleVerifier [0x007C6CC2+3548482]\n\tGetHandleVerifier [0x007C1C9C+3527964]\n\tGetHandleVerifier [0x0050870E+671630]\n\t(No symbol) [0x00401EB4]\n\t(No symbol) [0x003FD808]\n\t(No symbol) [0x003FD92D]\n\t(No symbol) [0x003EF7E0]\n\tBaseThreadInitThunk [0x7650FCC9+25]\n\tRtlGetAppContainerNamedObjectPath [0x779B7B1E+286]\n\tRtlGetAppContainerNamedObjectPath [0x779B7AEE+238]\n"}} | headers=HTTPHeaderDict({'Content-Length': '969', 'Content-Type': 'application/json; charset=utf-8', 'cache-control': 'no-cache'})

@Yudaotor
Copy link
Owner

Yudaotor commented Feb 8, 2024

I started logging in debug mode in the python version. I get a response with code 404 on the button.osano-cm-accept-all element

2024-02-08 20:54:13,001 DEBUG: Remote response: status=404 | data={"value":{"error":"no such element","message":"no such element: Unable to locate element: {"method":"css selector","selector":"button.osano-cm-accept-all"}\n (Session info: chrome=121.0.6167.161)","stacktrace":"\tGetHandleVerifier [0x00471673+52979]\n\t(No symbol) [0x003F7961]\n\t(No symbol) [0x002DDD3D]\n\t(No symbol) [0x00315FBB]\n\t(No symbol) [0x003160FB]\n\t(No symbol) [0x0034CF92]\n\t(No symbol) [0x00334534]\n\t(No symbol) [0x0034B3FE]\n\t(No symbol) [0x00334286]\n\t(No symbol) [0x0030C063]\n\t(No symbol) [0x0030CECD]\n\tGetHandleVerifier [0x00788D83+3294723]\n\tGetHandleVerifier [0x007C6CC2+3548482]\n\tGetHandleVerifier [0x007C1C9C+3527964]\n\tGetHandleVerifier [0x0050870E+671630]\n\t(No symbol) [0x00401EB4]\n\t(No symbol) [0x003FD808]\n\t(No symbol) [0x003FD92D]\n\t(No symbol) [0x003EF7E0]\n\tBaseThreadInitThunk [0x7650FCC9+25]\n\tRtlGetAppContainerNamedObjectPath [0x779B7B1E+286]\n\tRtlGetAppContainerNamedObjectPath [0x779B7AEE+238]\n"}} | headers=HTTPHeaderDict({'Content-Length': '969', 'Content-Type': 'application/json; charset=utf-8', 'cache-control': 'no-cache'})

cant find button.osano-cm-accept-all element is ok.
Don't worry about this place anymore. It won't affect anything. Just ignore it. The error report has nothing to do with it.also The cookies in this place have nothing to do with the cache login used.

@shishiawase
Copy link
Author

shishiawase commented Feb 8, 2024

cant find button.osano-cm-accept-all element is ok. Don't worry about this place anymore. It won't affect anything. Just ignore it. The error report has nothing to do with it.also The cookies in this place have nothing to do with the cache login used.

ideas that is, why doesn't it start with headless: true? when everything is fine with cookies and safe mode works. And it works in the normal mode with headless: false

but I need exactly headless:true and normal mod

@Yudaotor
Copy link
Owner

Yudaotor commented Feb 9, 2024

cant find button.osano-cm-accept-all element is ok. Don't worry about this place anymore. It won't affect anything. Just ignore it. The error report has nothing to do with it.also The cookies in this place have nothing to do with the cache login used.

ideas that is, why doesn't it start with headless: true? when everything is fine with cookies and safe mode works. And it works in the normal mode with headless: false

but I need exactly headless:true and normal mod

In fact, safe mode and normal mode have no impact on whether the script can log in normally.It's confusing if you can't run it properly

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

No branches or pull requests

2 participants