host error for contract existing value outputs contract id hash rather than contract address

[leighmcculloch]

What version are you using?

Protocol 22

What did you do?

Try to deploy an asset twice, where the first time it deployed successfully.

❯ stellar contract asset deploy --asset ABC:$(stellar keys address a)
❯ stellar contract asset deploy --asset ABC:$(stellar keys address a)

What did you expect to see?

The second time to display a error that could be understood by the user, where the contract address would be emitted as a C address.

What did you see instead?

An error with the contract ID displayed as a hex string.

❯ stellar contract asset deploy --asset ABC:$(stellar keys address a)
2024-12-13T08:27:36.552034Z ERROR soroban_cli::assembled: 0: "AAAAAAAAAAAAAAAAAAAAAgAAAAAAAAACAAAADwAAAAVlcnJvcgAAAAAAAAIAAAADAAAABAAAABAAAAABAAAAAgAAAA4AAAAXY29udHJhY3QgYWxyZWFkeSBleGlzdHMAAAAADQAAACCxdXaTv6o23MQp63HScGnKh7Hrfn620g/acIXeY3snjg=="
❌ error: transaction simulation failed: HostError: Error(Storage, ExistingValue)

Event log (newest first):
   0: [Diagnostic Event] topics:[error, Error(Storage, ExistingValue)], data:["contract already exists", Bytes(b1757693bfaa36dcc429eb71d27069ca87b1eb7e7eb6d20fda7085de637b278e)]