-
Notifications
You must be signed in to change notification settings - Fork 1
Common mistakes
As in any IT domain, you can easily make some mistakes while using iExec. The problem here is that as you are not executing on your own machine and furthermore, as you are trying to get the highest level of privacy, debugging is nearly impossible.
This is why we try here to list some of the mistakes that can be the source of a blocked application.
The main mistake that can be done, when your application should be working but isn't, is some spelling mistakes inside the iexec.json file. For instance a small error in the multiaddr field due to a (too) quick copy/paste.
The the first thing to do when a task of yours is blocked is to open the iExec Explorer (on the right blockchain), and find your task and deal (using taskId). Then, just check the fields of your application and the ones of your dataset for some small mistakes, you should probably find something.
Correct the mistake locally in your iexec.json and re-deploy. Don't forget to re-deploy all the features that works on top of the one you changed. For example when changing the multiadrr of your application, you get a new application address, so you need to re-deploy the apporder. But don't forget to re-publish the datasetorder too as it was restricted to be used only by the old, not working, app.
Note:
-
This guide is based on the technical documentation available here:
docs.iex.ec Please refer to this link if you want more informations.
-
You can also check out the SDK documentation here
-
You can browse the blockchain for any information you pushed at any point using the iExec explorer website (explorer.iex.ec), just set it on the goerli testnet and enter the address you want to check (wallet, application, dataset…).