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
On Porto, successful transactions are not showing up on accounts. We have tested with faucet, aptos_account::transfer_coins, and coins::transfer functions. None of them are available via the TS or Go APIs (via AccountTransactions functions), or the explorer.
Note that there are 7 deposit events, but 0 transactions.
Option B (we have a deployed case)
Create an account via a wallet provider.
Fund with faucet or transfer.
Go to explorer page for account.
Note that there are no transactions for the account.
Code
Using the Go SDK:
var start uint64 = 0
var limit uint64 = 100
if transactions, err := client.AccountTransactions(address, &start, &limit); err == nil {
util.Info(ctx, "@Count transactions retrieved.", len(transactions))
}
This logs out 0.
Expected behavior
All of these transactions should be available via the AccountTransactions call on the TS + Go APIs, as well as in the explorer. This includes faucet and transfers.
Describe the bug
On Porto, successful transactions are not showing up on accounts. We have tested with
faucet
,aptos_account::transfer_coins
, andcoins::transfer
functions. None of them are available via the TS or Go APIs (viaAccountTransactions
functions), or the explorer.To Reproduce
Steps to reproduce the behavior:
Option A
Option B (we have a deployed case)
Code
Using the Go SDK:
This logs out 0.
Expected behavior
All of these transactions should be available via the
AccountTransactions
call on the TS + Go APIs, as well as in the explorer. This includes faucet and transfers.Screenshots
Here is a txn, function is
0x1::coin::transfer
.Here is the recipient's account. Note that Balance is updated, as is
deposit_events
on the coinstore, but there are no transactions available.I tested the same code on Aptos' Devnet and I cannot reproduce. This is specific to Movement Porto (and maybe Bardock).
Here is an example of the same code creating a txn on Aptos devnet. The recipient account is updated and has the transactions available.
The text was updated successfully, but these errors were encountered: