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

Session is not invalidated when a new login with different number occurs #38

Open
felix-exon opened this issue Apr 17, 2023 · 2 comments · May be fixed by #56
Open

Session is not invalidated when a new login with different number occurs #38

felix-exon opened this issue Apr 17, 2023 · 2 comments · May be fixed by #56
Labels
bug Something isn't working

Comments

@felix-exon
Copy link

felix-exon commented Apr 17, 2023

Description of the bug
When working with multiple accounts even if a different phone number and pin are supplied the previous session gets resumed.

To Reproduce
Login using pytr login using an existing key file. Then pytr login -n <somenumber> -p <somepin>. Might as well save a new key file. Now pytr dl_docs will use the first account not the one which was logged in last (given the session is still valid).

10:58:25 Found credentials file
10:58:25 Phone: +49***********, PIN: ****
10:58:29 Web session resumed.                           // <----- This should not be
10:58:29 Logged in
10:58:29 Created history file

Expected behavior
When logging in with a number other than the one the active session is linked to, I expect a the session to be invalidated and a new session to start.

Error log

Environment

  • OS: MacOS
  • pytr version: 0.1.5
@felix-exon felix-exon added the bug Something isn't working label Apr 17, 2023
@hansgans007
Copy link

Yeah it’s used the old session not the new one

@hansgans007
Copy link

@marzzzello

@MartinScharrer MartinScharrer linked a pull request Mar 14, 2024 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants