Privy/Abstract cross-app transact popup hangs indefinitely / becomes unresponsive for an AGW ERC1155 safeTransferFrom call on Abstract Testnet. App origin: http://localhost:3000 Provider app id: cm04asygd041fmry9zmcyn5o5 Chain: Abstract Testnet, 11124 Wallet/AGW address: 0x020B43140Dd70bc345AbF4d81D636e8c895A8694 NFT contract: 0xb7228fF93Aa7D4a3918C4d39F0FCa73bE8750B04 Token id: 10 Amount: 1 Function: safeTransferFrom(address,address,uint256,uint256,bytes) Args: from: 0x020B43140Dd70bc345AbF4d81D636e8c895A8694 to: 0x000000000000000000000000000000000000dEaD id: 10 amount: 1 data: 0x Observed: Popup opens at https://portal.abs.xyz/cross-app/transact ... It stays on Loading... Chrome eventually shows Page Unresponsive. No tx hash or rejection is returned to the app. Tried: @privy-io/cross-app-connect 0.5.12 viem 2.52.0 AGW normal sign/broadcast path using privy_signSmartWalletTx wagmiWriteContract, and Direct Privy smart-wallet send path using privy_sendSmartWalletTx On-chain simulation of the exact call succeeds. The exact same safeTransferFrom call succeeds when submitted directly from sepolia.abscan.org Write Contract. Working popup host: privy.abs.xyz/cross-app/transact Hanging popup host from our app: portal.abs.xyz/cross-app/transact So the calldata/contract/testnet transaction itself appears valid; the hang seems specific to the Abstract Portal cross-app transact page or the AGW cross-app connector request shape. NOTE: nft contract has no burn() function, that's why we're sending to dead address directly from client side (i.e. user-initiated transaction to burn their own nft). PS: there's a bug / ux issue on this very UI for submitting bugs, if you fill description field and then try to attach image, it asks you to sign in, but after sign in/registration only the Title is re-filled and body is empty. Good thing I copied body before coz I figured this might happen, but I'm sure it may discourage some others from re-writing bug description and they'll just give up