Skip to main content

Find solutions to common issues that you may face during app development.

Issues

I see TypeScript errors​

Confirm that your integration uses the package-manager and runtime versions declared by its own project. Package managers can be sensitive to dependency resolution, especially in a monorepo.

Please ensure you have installed the right version of pnpm on your machine and re-install dependencies with pnpm install.

To find the accurate pnpm version in your project, check the root package.json file and look for the packageManager field.

For example, "packageManager": "[email protected]" means the project expects that pnpm release. Reinstall dependencies after switching versions.

Client-side GraphQL requests are rejected due to CORS error​

In a managed BoxNCase workspace, you may encounter the following error when trying to make a GraphQL request from the client side:

Access to fetch at 'https://api.workspace.example/graphql/' from origin 'https://your-application.example' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource.

The issue may be caused by the allowed-origin policy in the BoxNCase Dashboard. Open the workspace's integration settings and check Allowed API origins. If Selected origins is enabled, you have two options:

  • Add your application URL to the list of allowed origins.
  • Ensure your application makes GraphQL requests from the server side only.

Inspecting webhook delivery​

You can query app logs to see webhooks' delivery attempts.

{
apps(first:2){
edges{
node{
type
identifier
webhooks{
eventDeliveries(first:10){
edges{
node{
attempts(first:10){
edges{
node{
responseStatusCode
response
responseHeaders
}
}
}
}
}
}
}
}
}
}
}

Alternatively, you can also see a log of webhook deliveries in the Dashboard -> Apps -> Your app -> Manage App section.

note

If your subscription requires permissions that are not granted to your app, delivery attempts will not be included in the results of this query.