Click the "Fix with AI" button or manually ask the AI to fix the issues via prompt.
Open the cloud workspace by clicking the "Edit code" button. Run the platform manually to check for errors.
List the apps in the workspace:
bit app list
Run the app:
bit run my-platform
Restarting the dev server might help resolve different issues that might occur in the development process.
Handling server or client GraphQL issues can be handled in the feature's hooks for the client requests and aspect's component for the server side schema.
Server errors
Look for the related aspect GraphQL file and follow the API implementation to the node runtime to debug or pinpoint backend issues.
Request errors
Look for the React hook responsible for the resource, and ensure the fields match the fields described in the aspect backend and values are correctly passed.
Check the schemas in the *.model.ts files of the corresponding aspect to identify and fix the issue.
Authentication is usually handled by the platform aspect. To debug failing authentication check the GraphQL requests and see the server response.
- Head to the
useAuthhook to handle frontend issues. - Head to the platform aspect to handle backend issues.
- Check for repeating registrations of slots.
- Debug the component associated with the route.
To start a new clean, instance of the Bit dev server, head to the cloud workspace and run:
bit start
Click the url shown in the output to jump open the workspace UI.
To debug a platform efficiently, it is recommended to use the lion the desert strategy: