Troubleshooting
This article suggests solutions to common issues encountered while developing custom PhariaAI applications .
1. Problems with the binary pharia-skill-cli when publishing a Skill
Issue: You may encounter errors when trying to publish a Skill using the pharia-skill-cli.
Solution:
Remove the directory ./skill/bin/ and execute the publishing command again. This ensures that any corrupted or outdated binaries are cleared, allowing for a fresh build.
2. Issues with Safari blocking local development due to HTTPS content
Issue: When developing locally, you may face issues with Safari blocking content due to HTTPS requirements.
Solution: It is recommended not to use Safari for local development. Instead, consider using other browsers like Chrome or Firefox. These browsers handle local development environments more gracefully.
3. Issues with Chrome blocking local development due to CORS
Issue: When opening your locally running application in PhariaAssistant in Chrome, you see a blank page and the console shows an error similar to the following:
Access to script at 'http://localhost:8080/ui/assets/usecase.js' from origin 'https://pharia-assistant.<your domain>' has been blocked by CORS policy: Permission was denied for this request to access the `unknown` address space.Solution: You need to explicitly allow the page to access your local network (you may have accidentally disallowed this by dismissing a popup when opening it before). To do this, open PhariaAssistant, click on the options symbol in Chrome’s search bar (to the left of the URL), and enable the "Local network access" option.