search

MaxxRK / chaseinvest-api

MIT License
6 stars 4 forks source link

Suddenly stopped working #46

Open Akagui opened 1 month ago

Akagui commented 1 month ago

Was working fine a few hours ago to queue up some sells then I tried to go and put some buys in and check holdings and I get this output: error

Reinstalled the Chase API and had the same result.

Akagui commented 1 month ago

And now it spontaneously works again, so seems to be intermittent as I had this same thing happen earlier in the day a few times when testing as well.

MaxxRK commented 1 month ago

Can you get me a screenshot of what the browser looks like when it errors.

Aug 15, 2024 8:48:30 PM Akagui @.***>:

Was working fine a few hours ago to queue up some sells then I tried to go and put some buys in and check holdings and I get this output: error.png (view on web)[https://github.com/user-attachments/assets/d28e4a19-0961-4725-8ebf-867925999cfe]

— Reply to this email directly, view it on GitHub[https://github.com/MaxxRK/chaseinvest-api/issues/46], or unsubscribe[https://github.com/notifications/unsubscribe-auth/AKZTL4QZKV5KWUC3K66TIQLZRVK65AVCNFSM6AAAAABMTGU7MKVHI2DSMVQWIX3LMV43ASLTON2WKOZSGQ3DSMRXGI3DKMA]. You are receiving this because you are subscribed to this thread. [Tracking image][https://github.com/notifications/beacon/AKZTL4RKBI6RL43SHZAITHTZRVK65A5CNFSM6AAAAABMTGU7MKWGG33NNVSW45C7OR4XAZNFJFZXG5LFVJRW63LNMVXHIX3JMTHJGLQ4JI.gif]

MaxxRK commented 1 month ago

There is a problem where chase detects something and stops the website from loading for awhile in playwright. It will pop up and say something like. "this part of our website is not working right now." After a few hours, sometimes a day, it will start working again. I have found that if I move to another computer it will usually work and then come back to the one I was on after awhile it will start working again. I do not really have a solution for this currently, and I am not sure how to come up with one.

Akagui commented 1 month ago

It's odd because it seems to happen on certain accounts and not others. I'm trying to use it with 3 different user accounts. Now I got it to where it connects but it is spitting this error if I use a different account:

image

However if I use my primary account it seems to work as expected. So it seems like it may be something specific to the account itself.

MaxxRK commented 1 month ago

I need a screenshot of the actual browser if possible.

Aug 16, 2024 5:59:39 PM Akagui @.***>:

It's odd because it seems to happen on certain accounts and not others. I'm trying to use it with 3 different user accounts. Now I got it to where it connects but it is spitting this error if I use a different account:

image.png (view on web)[https://github.com/user-attachments/assets/bea8de48-5ef2-45ff-bff4-feb15e97f24f]

However if I use my primary account it seems to work as expected. So it seems like it may be something specific to the account itself.

— Reply to this email directly, view it on GitHub[https://github.com/MaxxRK/chaseinvest-api/issues/46#issuecomment-2294421715], or unsubscribe[https://github.com/notifications/unsubscribe-auth/AKZTL4R6SO64SUDAJRITVXDZRZ75XAVCNFSM6AAAAABMTGU7MKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEOJUGQZDCNZRGU]. You are receiving this because you commented. [Tracking image][https://github.com/notifications/beacon/AKZTL4RCZHGTB5DNEKSSEG3ZRZ75XA5CNFSM6AAAAABMTGU7MKWGG33NNVSW45C7OR4XAZNMJFZXG5LFINXW23LFNZ2KUY3PNVWWK3TUL5UWJTUIYIMNG.gif]

Akagui commented 1 month ago

Ok looks like it's the page that is rejecting it for that specific account. I have 3 accounts I'm using and 2 of them are working currently.

image

It is the correct credentials though because they work with the app and on the chase.com site when I type them in manually myself. Apparently python has some weird escape characters so it might be something like it is not pulling the whole password for some reason.

MrMark1127 commented 1 month ago

Hi, I'm having this issue as well and I'm curious if you found any escape characters that may be causing issues with the passwords? I'm not a python guy but I looked into it a bit and I can't discern much info out that is helpful to me.

I'm getting this error as seen in the Original Issue:

Logging in to Chase...
Error logging in to Chase: 'NoneType' object has no attribute 'keys'
Traceback (most recent call last):
  File "C:\Users\mark1\OneDrive\Documents\Dev\auto-rsa-main\chaseAPI.py", line 114, in chase_init
    account_ids = list(all_accounts.account_connectors.keys())
                       ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
AttributeError: 'NoneType' object has no attribute 'keys'

This worked one time for me yesterday, randomly and on a whim. I did get a push notif to my phone asking if I was trying to log in to Chase, I haven't received another one since.

Let me know if there is anything else I can provide you with to help. Thanks!

Edit: The ENV file for my credentials is Username:Password:Last_4_of_phone. Password includes !!$

Second Edit: Of course after playing with this for hours yesterday and today, it worked after I submitted my comment and removed approved devices from my Chase account. I also enabled text 2fa when logging in from a new browser and it's fired off the OTP each time properly. Let me know if you'd like assistance for further testing/edge cases.

Akagui commented 1 month ago

Looks like the problem was with the account. The credential were valid, however that particular web portal for Chase would reject them whereas the Chase.com main site and app would take them. I had 2 other accounts I was using and they were able to log in fine. Once I reset the password for the account then I was able to log in with it. It does seem to have a different authentication prompt though than the other 2 accounts and the bot doesn't recognize it so it has to be selected manually with the headless option disabled so you can see it in the browser.

It looks like this:

image

Whereas the prompt on the other 2 accounts appears like this:

image