Results
2
comments of
Shy
Am unsure about whether to re-raise the exception or just log and move on, current implementation just raises the error again, any input will be great
[spl-token]: getOrCreateAssociatedTokenAccount throws TokenAccountNotFoundError for different errors
+1, it appears as if in the scenario above, where the payer does not have enough SOL, the usual error about not having enough SOL is caught by the try...