Description

Fixes a crash that occurs when viewing asset details for Solana tokens in the Bridge flow. The issue was caused by getTokenDetails assuming all non-EVM asset addresses are already in CAIP format, when the Bridge API sometimes returns raw Solana addresses.

Related issues

Fixes #16734
Fixes SWAPS-2525

Manual testing steps

1. Navigate to Bridge feature
2. Select Solana as source or destination chain
3. Select any Solana token from the token list
4. Tap on the asset detail info button
5. Verify the asset details screen loads without crashing
6. Verify contract address and other details display correctly

Screenshots/Recordings

Before:

After:

Pre-merge author checklist

• I've followed MetaMask Coding Standards
• I've clearly explained what problem this PR solves
• I've linked the issue that this PR fixes
• I've included manual testing steps
• I've included screenshots/recordings if applicable
• I've added unit tests if applicable

Pre-merge reviewer checklist

• I've manually tested the PR (e.g. pull and build branch, run the app, test code being changed)
• I confirm that this PR addresses the issue linked above
• I've checked that all unit tests pass

Solution Details

Root Cause

The getTokenDetails function was calling parseCaipAssetType directly on asset.address for non-EVM assets, assuming it was already in CAIP format. However, the Bridge API sometimes returns raw Solana addresses instead of CAIP-formatted addresses, causing parseCaipAssetType to throw an error.

Fix Applied

Implemented the same defensive approach used in useTokenHistoricalPrices:

// Detect if address is already in CAIP format
const isCaipAssetType = asset.address.startsWith(`${asset.chainId}`);

// Convert to CAIP format if needed
const normalizedCaipAssetTypeAddress = isCaipAssetType
  ? asset.address
  : `${asset.chainId}/token:${asset.address}`;

Benefits

• ✅ Fixes crash: Solana asset details now load without errors
• ✅ Backward compatible: Handles both raw and CAIP format addresses
• ✅ Consistent pattern: Uses same approach as useTokenHistoricalPrices
• ✅ Zero breaking changes: All existing functionality preserved
• ✅ Future-proof: Works with any non-EVM chain automatically

Testing

• Added comprehensive unit tests covering both scenarios
• All 12 tests pass including new test cases
• Verified with existing Bridge test suite
• Manual testing confirms crash is resolved