Skip to main content

CLI Errors

Token Errors​

Error: no personal access token found. To learn how to obtain and configure a token, visit https://ionic.io/docs/appflow/cli/overview#authentication

This error can occur when you fail to provide a TOKEN line in your config file, and also do not pass a
--token on the command line.

Argument Errors​

Error: invalid argument[s] ... for <command>, expected <#> arg(s) [from ...]

This error can occur in any circumstance where you provide either the wrong number of arguments to a command, or a value that is not one of the allowed values.

Error: open <filepath>: no such file or directory

This error occurs when either an input file is not found at a given filepath or the specified parent directory does not exist for a given output path.

Config Errors​

Error: Failed to load config <filepath>
While parsing config: yaml: line <#>: could not find expected ':'
Please visit https://ionic.io/docs/appflow/cli/overview#authentication to see examples of a valid config file

This error occurs when you have a line in your config file that is not well-formatted.

Error: Failed to load config <filepath>
While parsing config: yaml: unmarshal errors: line <#>: cannot unmarshal !!str <config> into map[string]interface
Please visit https://ionic.io/docs/appflow/cli/overview#authentication to see examples of a valid config file

This error occurs when you only have a single line in your config file and it is not well-formatted.

Environment Errors​

Error: Environment variables must have a name

This error occurs when an environment file contains lines like =VALUE with no variable name.

Error: Environment variable names cannot contain whitespace

This error occurs when an environment file contains lines like MY VAR NAME=VALUE.

Error: Environment file does not exist: <filepath>

This error can occur when the environment file is not found at the provided path. You should make sure the command is running in the expected directory.

Error: Permission denied trying to open environment file: <filepath>

This error can occur when the user executing the Appflow CLI command does not have read permissions for the specified environment file. You should run ls -al on the file and whoami to make sure the command is running as the right user, and that user has read permission.

Error: Max environment variable length exceeded reading environment file

While unlikely to occur, adding lines longer than 64kb to your environment file will make it fail to load.

Contents