You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Been using ActualTap-py for a few days and I’m noticing some duplicate transactions appearing in Actual.
I think I’ve narrowed it down to this issue:
the wallet.txt file contains previous and current transactions. If a previous transaction has a merchant that has a rule to rename (e.g. McDonalds #2322 -> McDonalds), the previous transaction gets re-recorded because it doesn’t find the “McDonalds” one. Once it’s entered, Actual will rename the transaction with the rule but the duplicate was already created.
I’ve worked around this by modifying the shortcut to always send the current transaction in the json and ignore what was previously in the wallet.txt. And this seems to have resolved my duplicate issue.
thought I’d report it in case other users are also seeing this.
The text was updated successfully, but these errors were encountered:
Hello,
Been using ActualTap-py for a few days and I’m noticing some duplicate transactions appearing in Actual.
I think I’ve narrowed it down to this issue:
the wallet.txt file contains previous and current transactions. If a previous transaction has a merchant that has a rule to rename (e.g. McDonalds #2322 -> McDonalds), the previous transaction gets re-recorded because it doesn’t find the “McDonalds” one. Once it’s entered, Actual will rename the transaction with the rule but the duplicate was already created.
I’ve worked around this by modifying the shortcut to always send the current transaction in the json and ignore what was previously in the wallet.txt. And this seems to have resolved my duplicate issue.
thought I’d report it in case other users are also seeing this.
The text was updated successfully, but these errors were encountered: