[banquepopulaire]init_login() fail with 'Should be on login2 page'
With which module do you encounter problems?
banquepopulaire (Grand Ouest)
Describe the problem you encounter
I think new homepage is published by BPGO : https://www.banquepopulaire.fr/bpgo/
so
if self.new_login.is_here(): self.do_new_login()
fail and go back to old login way which result an assert "Should be on login2 page"
Paste here the stacktrace or error message you observe
Bug(banquepopulaire): Should be on login2 page
Traceback (most recent call last):
File "/home/stun/Dev/woob/woob/core/bcall.py", line 88, in backend_process
result = function(backend, *args, **kwargs)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/home/stun/Dev/woob/woob/tools/application/base.py", line 348, in _do_complete
res = getattr(backend, function)(*args, **kwargs)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/home/stun/Dev/woob/modules/banquepopulaire/module.py", line 163, in iter_resources
return self.iter_accounts()
^^^^^^^^^^^^^^^^^^^^
File "/home/stun/Dev/woob/modules/banquepopulaire/module.py", line 113, in iter_accounts
return self.browser.iter_accounts()
^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/home/stun/Dev/woob/modules/banquepopulaire/browser.py", line 91, in wrapper
ret = cb()
^^^^
File "/home/stun/Dev/woob/modules/banquepopulaire/browser.py", line 87, in cb
return func(browser, *args, **kwargs)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/home/stun/Dev/woob/woob/browser/browsers.py", line 1154, in inner
browser.do_login()
File "/home/stun/Dev/woob/woob/browser/mfa.py", line 201, in do_double_authentication
self.init_login()
File "/home/stun/Dev/woob/modules/banquepopulaire/browser.py", line 426, in init_login
self.do_old_login()
File "/home/stun/Dev/woob/modules/banquepopulaire/browser.py", line 573, in do_old_login
assert self.login2_page.is_here(), 'Should be on login2 page'
AssertionError: Should be on login2 page
What are the steps to reproduce the problem?
What woob version are you using?
Git HEAD
Additional info you'd like to mention
I try to investigate (I retried to fix #624 but I faced that new issue)