Troubleshooting pub

Getting a “403” error when publishing a package

You receive the following error when running pub publish:

HTTP error 403: Forbidden
...
You aren't an uploader for package '<foo>'

This problem can occur if one of your accounts was granted permission to publish a package, but the pub client registers you with another account.

You can reset pub’s authentication process by removing the credentials file:

$ rm ~/.pub-cache/credentials.json

Getting an “UnauthorizedAccess” error when publishing a package

You receive the following error when running pub publish:

UnauthorizedAccess: Unauthorized user: <username> is not allowed to upload versions to package '<foo>'.

You will see this message if you are not on the list of people authorized to publish new versions of a package. See Uploaders.

Pub build fails with HttpException error

You receive an HttpException error similar to the following when running pub build:

Pub build failed, [1] IsolateSpawnException: 'HttpException: Connection closed while receiving data,
...
library handler failed
...

This can happen as a result of some antivirus software, such as the AVG 2013 Internet security suite. Check the manual for your security suite to see how to temporarily disable this feature. For example, see How to Disable AVG Components.

Pub get fails from behind a corporate firewall

From the command line, pub honors the http_proxy and https_proxy environment variables. You can set the proxy server environment variable as follows.

On Linux/macOS:

$ export https_proxy=hostname:port

On Windows Command Prompt:

$ set https_proxy=hostname:port

On Windows PowerShell:

$ $Env:https_proxy="hostname:port"

If the proxy requires credentials, you can set them as follows.

On Linux/macOS:

$ export https_proxy=username:password@hostname:port

On Windows Command Prompt:

$ set https_proxy=username:password@hostname:port

On Windows PowerShell:

$ $Env:https_proxy="username:password@hostname:port"

Localhost unreachable after sign-in

When you run pub publish in a container or over an SSH session, the localhost that pub is listening to might be different from the localhost that’s accessible in your browser. Although you can sign in using the browser, the browser then complains that http://localhost:<port>?code=... is not reachable.

Try this workaround, which uses the command line to complete sign-in:

1. In a terminal window, run pub publish.
2. In the browser window that comes up, sign in.
   The browser is redirected to a new localhost URL (http://localhost:<port>?code=...) but complains that the URL isn’t reachable.
3. Copy the new localhost URL from the browser.

4. In another terminal window in the same container or on the same host as the one where pub publish was called, use the curl command to complete sign-in using the new localhost URL:

   $ curl 'http://localhost:<port>?code=...'