What changed (plus any additional context for devs)
alignment with App telemetry
setting up Sentry and Rudderstack identify in new useEffect to absorb wallet switches
added getWalletContext util to prepare hashes and wallet types consistently throughout the codebase
added walletContext overrides in track and screen to support scenarios where the actioned wallet is different than the global selected wallet
overrode wallet context in dappPromptConnectApproved, dappPromptConnectRejected, dappPromptSendTransactionApproved, dappPromptSendTransactionRejected, dappPromptSignMessageApproved, dappPromptSignTypedDataApproved, dappPromptSignMessageRejected, dappPromptSignTypedDataRejected where the user can switch wallets prior to signing; this should cover all edge cases
Screen recordings / screenshots
What to test
confirmed event flow on rudderstack ✅
no race condition with Sentry initialization or logs fired by Sentry.setUser if useEffects are called in unexpected order
Fixes BX-1694 Figma link (if any):
What changed (plus any additional context for devs)
useEffectto absorb wallet switchesgetWalletContextutil to prepare hashes and wallet types consistently throughout the codebasewalletContextoverrides in track and screen to support scenarios where the actioned wallet is different than the global selected walletdappPromptConnectApproved,dappPromptConnectRejected,dappPromptSendTransactionApproved,dappPromptSendTransactionRejected,dappPromptSignMessageApproved,dappPromptSignTypedDataApproved,dappPromptSignMessageRejected,dappPromptSignTypedDataRejectedwhere the user can switch wallets prior to signing; this should cover all edge casesScreen recordings / screenshots
What to test
Sentry.setUserif useEffects are called in unexpected order