- Apr 26, 2021
-
-
My thoery is that the website expect you to retrieve the account list before the details, which was not the case when we had retried before.
-
-
-
Helps put the browser in a good state.
-
- Apr 11, 2021
-
-
Romain Bignon authored
-
Romain Bignon authored
-
- Apr 08, 2021
-
-
The page is very similar to the loans page on the arkeabanqueprivee pro website, but it's a list instead of a table, so all xpaths are different. Like on arkeabanqueprivee pro, loans have no number and no ID on the website; only a label which isn't unique. We have no choice but to use the "index" which is an unstable JS generated value.
-
- Apr 04, 2021
-
-
- Mar 12, 2021
-
-
-
The header is already set in the next method.
-
In python 2, generators (including function with yield) use the 'next' method to get the next value. In python 3, they use the '__next__' method.
-
- Feb 12, 2021
-
-
Erase this bad practice. Moreover with a low STATE_DURATION, keep session headers has no interest anymore.
-
2FA is now automatically sent when it is needed. Only TPP can have access to consent url to check if 2FA is required.
-
- Jan 18, 2021
-
-
Some accounts don't have an IBAN, which is the case for life insurances for example.
-
-
When no par space is found, instead of retrying multiple times and raise a WebsiteUnavailable, we just send an empty list of accounts
-
Filter for current month transactions must also look at year since, upon changing year, filtering only on month would fail.
-
- Dec 26, 2020
-
-
Sometimes the page has accounts of multiple owners, we need to select the correct one to go to the right details page.
-
- Dec 11, 2020
-
-
Needed for bpe.
-
Some requests change (profile and login). Moreover the json profile content changes.
-
- Nov 27, 2020
-
-
Some internal recipients can have the same label and same owner, this caused some duplicate ids since we generated the internal recipients ids base on those values.
-
Damien Mat Jedrzejewski authored
CMSO has previously mistakenly switched 'code_verifier' and 'code_challenge'. For most child modules it is now in the ritgh order, but not for all. Now the code that calls for 'code_verifier' and 'code_challenge' making, is put in a separate function so it can be switch in the wrong order if needed, in a child module.
-
- Nov 17, 2020
-
-
For now, transactions were fetch on a month by month basis. Each month would display transactions with at least one type of id among 2 possible, and those are collected. Finally, a global history page is parsed, without month param. A special condition would avoid duplicates based on the ids. But at the turn of the month there are transactions that don't have any id, and so would not be selected. Solution: First page fetched is the 'SIX_DERNIERES_SEMAINES'. All transactions from current month are selected here (they don't bear any id). Then the month by month selection is done. No final page without month param is fetched at the end since we already got all transactions. Tested also on CMB and BPE child modules.
-
The previous method used the account label and owner to find it on the market accounts page. However sometimes the same owner can have two accounts with the same label, and the matching fails. This was used to fetch invests, history and market orders, but also to determine the account's id. We can get the same id from the accounts page so we do that instead and we use it for the matching.
-
-
- Oct 28, 2020
-
-
- Sep 23, 2020
-
-
Seen with arkea. We want to avoid to force sending otp in other cases.
-
- Aug 26, 2020
-
-
all the connections without a scope value raised an AssertionError but shouldn't this patch check if the scope is not None
-
Some clients have an UnavailableWebsite error, this is due to the SCA which is not catched because of the scope 'all' which is not managed by the module. Also, phone number is not found in the contact information because the client have a professional phone.
-
- Aug 07, 2020
-
-
The emitters and account do not have the same id. This force us to create a custom id based on the account/emitter label and owner (and co-owner if one). When there is no match between any emitter and the account, we cannot list the recipients and make transfer from this account.
-
After going to market space, subsequent calls return an error 403. The issue seems to be the base url of the referer, if we force it to the api host, it works.
-
On the pro website, we get an error 403 when we try to change of area after the first one is reached, and another one when we try to fetch a token on an account page. A redirection to a specific url before each request resolves that.
-
The commit 30cbc62b introduces regression and may duplicate transactions with id only. The patch keeps the idea of the guilty commit but ensure we do not get duplicated transactions with the same id, like it was before.
-
- Jul 15, 2020
-
-
Since the error is now handled properly, the try except is not useful anymore, I deleted it
-
- Jul 02, 2020
-
-
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
-
-
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.
-
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.
-
