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
guardlet index =self?.transactions.firstIndex(where:{
128
+
guardlet index =self.transactions.firstIndex(where:{
129
129
$0.txId == coinTransaction.txId
130
130
})
131
131
else{return}
132
132
133
133
/*
134
134
Workaround to correctly set isOutgoing when multiple transactions share the same txId across different accounts.
135
135
136
-
This situation can happen when sending funds from a regular account to a secret one — technically two different transactions, but with the same txId.
136
+
This situation can happen when sending funds from a regular account to a secret one or vica versa — technically is the same transaction, but it should show different isOutgoing for sender and reciever.
137
+
137
138
Currently, there's no reliable way to assign a truly unique ID to each TransactionDetails instance, so this workaround helps distinguish them for now.
0 commit comments