- Sep 26, 2020
-
-
- Sep 23, 2020
-
-
When doing a request on the login url with a `/` at the end, we receive a 301 and are redirected to the same url without a `/` at the end. And because of the `/` that is expected in the url, we end up not finding the page. Removing the `/` at the end in the regex leads to no redirection and it matches both cases.
-
Numerous wrongpass are still present. We let the retry to decide if we are in a real wrongpass case.
-
Thanks to this tool, we will be able to drop dumping to the old, custom, hard-to-parse format in favor of the new, ill-defined format: HAR!
-
For binary response, HAR allows base64 encoding so data is untouched. But no such thing exists for binary posted data. Some generators write JSON with the binary posted data as if it were latin-1 encoded text. But when reading, what can we do? Think it's binary to encode back to latin-1? Or think it's text? HAR gives no answer, so we add a non-standard "x-binary" key to indicate "text" is actually binary disguised with latin-1.
-
The condition was in ListElement instead of ItemElement and some accounts were filtered out by mistake.
-
-
-
When amount is not found by the first parsing, it must be done by a second one. I changed the condition on which this is triggered, since it not needed anymore, and would throw an AttributeError when page is parsed a second time.
-
This is mainly used during iter_accounts, but also in the cragr module before calling is_account_present.
-
The xpath to check if an account is present does not appear if the netfinca space is in action needed so I added a check_action_needed method that is used for iter_investments and iter_market_orders.
-
These accounts have no balance, we don't want to fetch them.
-
Loans currently have balance == NotLoaded, which is a problem for the backend: "TypeError: '>' not supported between instances of 'NotAvailableType' and 'int'"
-
It avoids bad config instantiation from parent.
-
Otherwise some connections have 'CenetBrowser has no attribute iter_market_orders'
-
Some users are redirected to a new url for their por account summary
-
A life insurance (ANAE) was not typed therefore its investments were not scraped correctly.
-
-
-
The login URLs changed and once we reach login page there is now a `<form>` instead of the former JSON login system.
-
It has been recently deleted from directaccess parent LoginPage, but is needed for openapi.
-
Between 2 synchronizations, client might have set up 2FA to be systematic. It also is often the case for pro users.
-
-
-
In some cases, an account can have its url missing, which caused the assert to fail and crash the iter_transfer_recipients. This can be fixed by searching the account from its iban instead of its id.
-
-
-
-
-
2FA to be done in a navigator by user
-
It fails with utf-8-bom.
-
This is a better trick than manually choping the BOM.
-
-
If the account was recently created (less than a month), there was only one period to be fetched, leading to a crash since we were accessing periods[1] to access the account page.
-
Seen with arkea. We want to avoid to force sending otp in other cases.
-
-
-
- Sep 19, 2020
-
-
-
The empty_xpath is not exactly the same on both spaces.
-