Troubleshooting
Most problems come from something missing on your computer, not from your tests. Find what you see below, then follow the steps.
rbenv is not installed
What you see. The app opens a setup guide instead of the welcome screen, or says it cannot find rbenv or Ruby, so it cannot run tests.
What to do.
- In Terminal, install rbenv (this needs Homebrew):
brew install rbenv ruby-build && rbenv init - Follow what
rbenv initprints to add rbenv to your shell settings (.zshrcor.bash_profile). - Open a new Terminal window, install Ruby (see the next section), then restart Raider Desktop.
Ruby is too old
What you see. A message that your Ruby version is outdated and Ruby 3.2 or higher is needed.
What to do.
- In Terminal, install a newer Ruby and make it the default:
rbenv install 3.4.1 && rbenv global 3.4.1 - Install Ruby Raider for the new Ruby:
gem install ruby_raider. - Restart Raider Desktop.
Gems are missing
What you see. The setup guide says Ruby Raider is not installed, or a window titled "Missing gems" lists gems the project needs.
What to do.
- If Ruby Raider itself is missing, run
gem install ruby_raiderin Terminal, then restart the app. - If the window lists missing gems, click Install Now. Skip closes the window without installing.
Permission denied
What you see. An error that says "permission denied" when the app creates, saves or changes a file in your project.
What to do. Your user account does not own the project folder. Make yourself the owner in Terminal, replacing the path with your project's, then try again:
sudo chown -R $(whoami) /path/to/your/project/folder
macOS says the developer cannot be verified
What you see. "App cannot be opened because the developer cannot be verified" the first time you open Raider Desktop.
What to do.
- Open System Settings › Privacy & Security.
- Click Open Anyway next to the Ruby Raider message.
- Click Open in the window that follows.
You only do this once.
macOS says the app is damaged
What you see. "Ruby Raider is damaged and can't be opened." The app is not damaged: it is not yet signed with an Apple developer certificate.
What to do. In Terminal, run this once, changing the path if you put the app somewhere other than Applications:
xattr -cr /Applications/Ruby\ Raider.app
Ruby Raider is too old to create a project
What you see. On the Create page: "Raider needs Ruby Raider 4.0 or later installed."
What to do. In Terminal, run gem install ruby_raider, then come back to the page. It checks again when it opens.
This project needs ruby_raider 4.0
What you see. On the Tests tab: "This project needs ruby_raider 4.0". Run and recording refuse with the same reason.
What to do. Click Update ruby_raider and confirm. Raider pins the project to ~> 4.0, runs bundle update ruby_raider and reloads the project; see Projects.
Mobile projects are not supported
What you see. "Mobile projects are not supported" when you open a project.
What to do. This version of Raider Desktop works with web projects only. If you open an Appium project, click Open another project.
A scheduled run did not run
What you see. A schedule's next run went by with no new result, or its row in the Schedules panel shows a warning.
What to do. See When a scheduled run fails for what each warning means and what to press.
Still stuck
Report the problem on GitHub, with what you see and what you tried.