Troubleshooting

Here are the problems that come up most often, with cause and solution. If a build itself fails, the Station usually already shows what’s going on above the log. That’s described in When a build fails.

First step for almost everything: Copy the displayed command from the Build tab and run it in the terminal in the project folder. If it fails there in the same way, the problem is the project or the toolchain, not the Station.

The app won’t start

macOS says the app is damaged or comes from an unidentified developer. The official DMG from the download page is signed and notarized and opens without this message. Download the app again from there and drag it into the Programme (Applications) folder.

Only an ad-hoc signed copy that doesn’t come from the official DMG, for example one passed on via AirDrop or zip, needs this once:

xattr -dr com.apple.quarantine "/Applications/iw Build Station.app"

The app still shows the old icon after an update. macOS caches icons. killall Dock in the terminal helps.

Tools aren’t found

fvm: command not found, fastlane: command not found or pod: command not found. An app launched from the Finder doesn’t inherit the PATH settings from ~/.zshrc. That’s why, by default, the Station starts through a login shell.

1. Open Einstellungen › Toolchain (Settings › Toolchain) and see what’s found.
2. Under Ausführung (execution), check that Shell-Modus (shell mode) is set to Login-Shell (/bin/zsh -lc) (login shell).
3. If a tool is still missing, add its folder under Zusätzliche PATH-Einträge (additional PATH entries). You can find the folder in the terminal with which fvm. Then Erneut prüfen (check again).

fvm isn’t installed. Install it with brew install fvm. Without fvm, the Station uses flutter from the PATH, but then projects can’t have different Flutter versions.

The project’s Flutter version is missing. The Station recognizes this in the log and offers fvm install.

Project folder not readable

If a project lives in iCloud Drive, on the Desktop or in Documents, macOS asks the first time it’s accessed. If you declined or the permissions are missing, the Station can’t find the folder or can’t write to it.

The fix: Systemeinstellungen › Datenschutz & Sicherheit › Festplattenvollzugriff (System Settings › Privacy & Security › Full Disk Access), add the iw Build Station there and switch it on. Then restart the app.

The project shows “Ordner fehlt” (folder missing). The folder was moved or renamed. Open Projekt bearbeiten (Edit project) and choose the new location under Projektordner (project folder) with Ändern … (change).

CocoaPods

„CocoaPods ist installiert, aber nicht lauffähig” (CocoaPods is installed but not working). Usually CocoaPods was installed with a different Ruby version than the one currently calling it. The Station suggests brew install cocoapods. With Beheben (fix), it runs through the queue.

Podfile.lock doesn’t match the installed state. Beheben runs pod install. If that doesn’t help, rebuilding the pods is available under Andere Wege (other ways).

The pod index is outdated. pod repo update && pod install fetches it again.

Without CocoaPods, iOS and macOS builds with plugins won’t work. You can install it with brew install cocoapods.

Builds

A build hangs, even after cancelling. Gradle and Dart daemons sometimes survive a cancel. Einstellungen › Wartung › Gradle-Daemons stoppen (Settings › Maintenance › stop Gradle daemons) ends them. If Xcode hangs, deleting DerivedData under Aufräumen › Xcode, Android und Flutter (Clean up › Xcode, Android and Flutter) helps.

No artifact detected, even though the build went through. With custom scripts, the script has to output a line BUILDSTATION_ARTIFACT=<pfad>, or the preset needs a matching pattern under artifactGlobs. See Custom scripts and web builds.

A failed build counts as successful. The script is missing set -euo pipefail. Without that line, subsequent lines mask the error and the script still ends with exit code 0.

The build is cancelled because the branch can’t be switched. The project is linked to a Git branch and there are uncommitted changes in the folder. Commit or discard them. See Adding projects.

“Unsupported class file major version …” or “Minimum supported Gradle version is …”. JDK, Gradle and Android Gradle Plugin don’t fit together. Versionen prüfen … (check versions) in the error strip or Versionen (Versions) in the Build tab shows what doesn’t fit and suggests the change. See Versions and updates.

The disk is full. The error strip offers Zwischenergebnisse leeren … (clear intermediate results). You can make more space as described in Freeing up space.

config.json contains errors. If you edited the file by hand, a banner at the top shows the faulty spot. Fix it and click Neu laden (Reload). The Station doesn’t overwrite the file in the meantime.

Upload

An upload fails. The most common error patterns are listed with their causes in the store chapters:

• Google Play
• App Store and TestFlight
• Microsoft Store
• fastlane

If a store rejects the credentials, the Station recognizes this and takes you back to the setup with Upload-Einrichtung prüfen … (check upload setup). There, Verbindung testen (test connection) helps narrow things down.

“Diese Build-Nummer ist schon hochgeladen” (this build number has already been uploaded). Each store accepts a build number only once. Increase it and rebuild. If Build-Nummer automatisch hochzählen (auto-increment build number) is on in the preset, this happens by itself from then on.

The upload went through, but TestFlight shows nothing. Apple’s processing takes a few more minutes after the upload.

The Transporter button is greyed out. Transporter isn’t installed. You can get it for free in the Mac App Store.

Drag and drop

Dragging out of the app doesn’t work. If the target window doesn’t accept the file, Im Finder (in Finder) and Pfad kopieren (copy path) still work as usual. The handle is a shortcut, not a replacement.

License and remote access

The license key is rejected. The Station gives the reason under Einstellungen › Lizenz (Settings › License). If the license server can’t check right now, try again later with Jetzt prüfen (check now). See License.

Remote access can’t be reached. Check that the app is running on the Mac, the license is valid and a password is set. If it says “Eingeschaltet, aber nicht erreichbar” (switched on, but not reachable), the port may already be in use, for example. Then try a different one. See Remote access in the browser.

Still not solved?

Send us the executed command and the log excerpt you get with Log kopieren (copy log) in the Verlauf (History). You’ll find contact details at inwendo.de.