Troubleshooting
If Bricoop Desktop is not behaving as expected, work through the topics below. Each section follows the same shape: a symptom, a likely cause, and a check to run.
Application not detected
Symptom: a supported application you have installed does not appear in Bricoop.
Likely cause: the application is not installed in a location Bricoop scans, or it is below the minimum supported version.
Check: confirm the application is installed and launches normally, update it to a current version, and reopen Bricoop so it can scan again.
Version unsupported
Symptom: Bricoop reports that an application or provider version is unsupported.
Likely cause: the installed version is older than the minimum version declared in the matching adapter manifest.
Check: update the application or provider client to a current version and reopen Bricoop. If the issue persists, confirm the minimum supported version on the integration’s detail page.
Provider authentication fails
Symptom: connecting a provider fails, or an existing connection shows an authentication error.
Likely cause: the credential or token is missing, expired, or lacks the required scope, or the provider’s authentication service is unreachable.
Check: re-enter the credential in Bricoop using a current value, confirm the account has the required access, and retry. If the provider’s authentication service is down, wait and retry.
Request failure
Symptom: a request from a supported application returns an error or no response.
Likely cause: the provider rejected the request (rate limit, quota, ineligible account, or unsupported model), or the network path between your device and the provider was interrupted.
Check: confirm the selected model is supported for the application, verify the provider account is within its limits, and retry. Provider-side errors keep their own message where the provider returns one.
Update and catalog connectivity
Symptom: Bricoop cannot fetch catalog updates or notify you of a new release.
Likely cause: the network connection to Bricoop’s public catalog or update service is blocked, or the installed Bricoop version is out of date.
Check: confirm your device can reach the network, check whether a firewall or proxy is blocking the catalog host, and update Bricoop to the current version.
Still stuck?
If none of the checks above resolves the issue, run the safe in-app diagnostics from Bricoop’s settings, then report what you observed through the GitHub issue link below.