Troubleshoot Blockchain App Builder Visual Studio Code Extension

Use the following information to troubleshoot system problems with the Blockchain App Builder Visual Studio Code extension.

Prerequisites issues
Errors can occur if you modify or upgrade any of the prerequisite software that is required by Blockchain App Builder. You can use the Installed Dependencies function to check that your installation of Blockchain App Builder still meets the prerequisites. On the Blockchain App Builder welcome page in Visual Studio Code, click Installed Dependencies. A table is displayed that shows you the required version and the actual installed version of components that Blockchain App Builder uses. Required components are indicated by an asterisk (*).
If the prerequisites check fails with errors and warnings when you attempt to install Blockchain App Builder, you might see an error similar to the following example in the output pane in Visual Studio Code:
Error:
Aborting installation. Error:
Found 1 error(s) in pre-requisites check, failed with following errors:
1. Golang version mismatch. Expected 1.21.x, but found 1.18.5.

Found 3 warning(s) in pre-requisites check.
1. Docker is not installed. Please install Docker >= 18.09.0. To deploy chaincodes in the local environment, 
please install the recommended version of Docker.
2. Docker Compose is not installed. Please install Docker Compose >= 1.23.0. To deploy chaincodes in the 
local environment, please install the recommended version of Docker Compose.
3. Git is not installed. To sync chaincodes, please install the Git according to the documentation.
Deployment failure
Due to deployment failure, corrupt deployment, a Docker peer container being full, or a Docker peer that was stopped in the local network, you may see an error similar to the following text:
============ Started instantiate Chaincode ============
[2028-19-01T19:25:lO.372] [ERROR] default - Error instantiating Chaincode GollGl on channel mychannel, detailed 
error: Error: error starting container: error starting container: Failed to generate platform-specific docker 
build: Failed to pull hyperledger/fabric-ccenv:latest : API error (404): manifest for hyperledger/ 
fabric-ccenv:latest not found: manifest unknown: manifest unknown [2020-19-01T19:25:10.372] (INFO) default -
============ Finished instantiate Chaincode ============
[2020-19-01119:25:10.372] [ERROR] default - Error: Error instantiating Chaincode Goll01 on channel mychannel, 
detailed error: Error: error starting container: error starting container: Failed to generate platfom-specific 
docker build: Failed to pull hyperledger/fabric-ccenv: latest : API error (404): manifest for hyperledger/ 
fabric-ccenv:lalest not found: manifest unknown: manifest unknown exited: signal: terminated 
INFO: exited: signal: terminated

ERROR: Error in Chaincode deployment
This is due to a peer container that is not able to start up properly again.
Solution: Rebuild your runtime by selecting your local environment in the Environments pane, right-clicking and selecting Rebuild Local Environment. Attempt to deploy again.
Resetting Extension Data
Blockchain App Builder user data can get corrupted. Resetting the extension data clears your data from Blockchain App Builder without affecting anything stored locally.
  1. Open the Command Palette from the View menu.
  2. In the Command Palette, type Reset Extension.
    Screen capture showing the Reset Extension Data command in the Command Palette.
  3. Select Oracle Blockchain Platform Reset Extension Data. Visual Studio Code clears the existing blockchain data and reloads the default installation data. This does not affect the files stored locally in your system, but you must import them back into Visual Studio Code and reconfigure any environments you had previously set up.
macOS: Xcode
After a macOS upgrade, or if Xcode is not installed, you might see an error similar to the following in the error log:
gyp: No Xcode or CLT version detected!
gyp ERR! configure error
gyp ERR! stack Error: `gyp` failed with exit code: 1
gyp ERR! stack     at
  • To work around this behavior, open a terminal window and run the following commands:
    sudo rm -rf $(xcode-select --print-path)
xcode-select --install