[2.6][T4] Misleading error message when updating a bridgechain not registered by the same business

[Lemii]

Summary
When a business tries to update an existing bridgechain / ID that has not been registered with the same account, the following error is returned:

[
  {
    "type": "ERR_APPLY",
    "message": "Failed to apply transaction, because bridgechain is not registered error."
  }
]

This message implies that the bridgechain is not registered at all (it returns the same message when that is the case), while the issue it actually that the user is not the owner of the bridgechain.

Expected Behavior
Return a more accurate error message, describing that the account is not the owner of the bridgechain.

Your Environment
Devnet 2.6

Thanks for opening this issue! A maintainer will review this in the next few days and explicitly select labels so you know what's going on.

If no reviewer appears after a week, a reminder will be sent out.

This issue or pull request needs further investigation. Please wait for further information, thank you.

[KovacZan]

Do you want to change error message to be more accurate?

[Lemii]

Do you want to change error message to be more accurate?

Not sure if it's aimed at me, but I'll reply anyway :)

Let's imagine you're a business owner running one or more bridgechains. You want to update a bridgechain, but you made a small error by entering an incorrect ID.. when you send the update, you get an error message bridgechain is not registered.

I believe that this will be very confusing to the business owner, because in his experience his bridgechain is registered. After seeing such message, he might think something is wrong with the system or that he broke something, even though the issue is nothing to worry about and he just entered the incorrect ID.

So yeah, I believe it would be beneficial to the user experience to change the error message to something more accurate 👍

[faustbrian]

@Lemii the questions was more if you would like to fix the issue by submitting a PR for it.

[Lemii]

@faustbrian Sure, will do 👍

[faustbrian]

Great, assigned you to the issue.

This issue has been closed. If you wish to re-open it please provide additional information.