Closed javydekoning closed 3 years ago
4 more transactions today with the same issue. Looks like the reason behind this is the duplicate detection:
https://github.com/wesselt/bunq2ynab/blob/master/lib/sync.py#L110-L148
Thanks for the detailed report! Mixing up payees and the same amount on the same day does point at the "occurrence" calculation. I'm already looking into for the other open bug and hope to make some progress this week.
This patch should fix it: https://github.com/wesselt/bunq2ynab/commit/0766cc86bfcc8a0d3fd95fced46addbe9551f1c9
How do we go about updating the serverless repository?
I'll publish to Serverless application repository tomorrow.
Published and deployed.
Hi @javydekoning, thanks for updating the repository. What's the easiest way to upgrade existing instances to the new code?
Just redeploy for Serverless Application Repository. The existing configuration in SSM will persist, hence no further action should be required.
I'm looking at this AWS console. How can I redeploy?
Same as the initial deployment as described in the README here: https://github.com/wesselt/bunq2ynab#deploying-the-function
Ah right, so like a fresh install. I'll just copy the tokens from the parameter store.
Went out for diner last Friday. I payed and shared a request with my friends.
Both transactions show in YNAB, but both show as "Friend A". 2 days later, friends C and D pay as well. Both of these transactions show as Friend C.
I can't figure out why from the JSON. They all have unique ID's