Skip to main content
All CollectionsKnowledge BaseGeneral issues
Inconsistent Danger configuration
Inconsistent Danger configuration
Updated over a week ago

Issue:

The Danger Step fails, even though the configuration (for example, the access token and the repository URL) seems correct.

Possible solutions:

Danger can be configured in two different ways on Bitrise:

  • Using our Workflow Editor to edit the Step's configuration values.

  • Using Environment Variables that configure the Danger tool directly.

If you see that your configuration is not applied at runtime correctly, check your Bitrise Environment Variables on the Env Vars tab. It's not recommended to mix the two configuration methods, as it results in conflicting values. You should either define everything in the Workflow Editor, or as Environment Variables directly.

Did this answer your question?