- Jul 03, 2020
-
-
Impossible to login due to an assert in the on_load function. The error message as not impact on the success of the connection.
-
- Jul 02, 2020
-
-
-
-
ntome authored
pickle may be unsafe for loading data. All we want is a cookie jar, we can just serialize its cookies, not necessarily the whole jar with its type and policy. Old format is base64(compress(pickle(jar))). New format is base64(compress(json(jar))) where JSON conversion is on the list of cookies (taking name, value, domain, path, secure (https) and expires). dump_state will now save using the new format while load_state supports both new and old format. This allows compatibility for some time, then later old format support in load_state will be dropped too.
-
We can randomly get a 405 error back from our first request in the do_login(), causing a crash while trying to parse the empty response body as json.
-
For some reasons, trying to go to market history during an iter_savings can cause a ClientError. If not handled, this exception will make the browser try to relogin and start over the iter_accounts but the session is actualy not lost. In this case, we juste handle it when retrieving the market order and in the worst case we won't have this information
-
-
-
-
-
-
For now the 2FA is cross browser, so the user can validate it through his browser.
-
In authorize url we need to add the nuser when it exists and we also need to add the good type_srv value (pro/part)
-
The TYPE_CARD account's number was NotLoaded
-
-
-
Attempts to access to ProAccountsPage can lead instead to RedirectPage. It would end up to a '/sites/erreur-404' URL (but in code 200). This happens only on certain connections, as a wrongly activated security feature of the server, as discussed directly with the bank, when there is no accounts on ProAccountsPage. If redirection was followed the whole session would be broken, without being logged out, tough. Need to log back.
-
The ELCLBrowser's subdomain is no longuer used and is now equivalent of LCLBrowser. Only the login page still function (to not mess with end-user habits I guess) but is not needed anymore.
-
When the investment's currency is different from the account's, the unitvalue is in the original currency, so we must fill obj_original_currency & obj_original_unitvalut instead of obj_unitvalue.
-
There is no need to Format() with 'Vente' or Achat', this information is already available with MarketOrder.direction
-
-
-
-
Transfers to newly added recipients require an authentication with a personal key card code and an app validation.
-
Some connections are in bug because we cannot fetch the user's information correctly on profile_page because of an Action Needed. The user has to fill-in and update its personal data on the wbesite.
-
sometimes the account is already signed in so we have to disconnect them
-
A 400 error can occur in the json we use to retrieve the saving accounts even if there are account to fetch so sometimes there are no reasons to this to happen.
-
ntome authored
-
ntome authored
HAR file was rewritten on every request, because JSON libs don't allow inserting data in an existing JSON without rewriting the whole file. However, if we put request/response entries at the end of the HAR data, only a fixed suffix exists after the entries. Then we can seek near the file end to a computed position, write the new entry (which overwrites terminators), and we can rewrite the overwritten terminators right after. Not only can we write only the new data, but we do not need to keep track of the shifted bytes. If the HAR wasn't written with the exact same options, we won't seek accurately though.
-
Add missing Account().number for "Compte Titre Ordinaire" account
-
A lot of connections are in wrongpass because they are in phenix browser instead of the main browser. We first do login with the main browser and in case of BrowserIncorectPassword we try on Phenix Browser.
-
If the amount of the transaction is too large, it is displayed in scientific notation. When that's the case, we fetch it in the details page of the transaction.
-
Life insurances are on a different space so it could cause an error.
-
The precedent code is kept in case of still used url.
-
on some accounts, csv is not available, it results to an empty history, so we need to get them in another way
-
we now get an otp when trying to get to much history : probably more than x months, so handle that case by bypassing this
-
Change the head_xpath and item_xpath of TransactionsPage
-
-
Attempts to access to ProAccountsPage can lead instead to RedirectPage. It would end up to a '/sites/erreur-404' URL (but in code 200). This happens only on certain connections, as a wrongly activated security feature of the server, as discussed directly with the bank, when there is no accounts on ProAccountsPage. If redirection was followed the whole session would be broken, without being logged out, tough.
-
The messsage seems to have change. It is now : "Vous n’avez pas de solution d’authentification forte. Pas de panique !". Moreover, we don't want to raise NeedInteractiveFor2FA if no 2FA is present.
-
