Troubleshooting

Troubleshooting

macOS says the app cannot be opened

Early releases may not be notarized. If macOS blocks the app on first launch, this is usually Gatekeeper reacting to an unsigned or non-notarized build.

For broader distribution, the project should move to Developer ID signing and notarization.

Xcode shows multiple macOS destinations

This warning is usually harmless:

Using the first of multiple matching destinations

The build can still succeed.

AppIntents metadata warning

This warning is expected because InfraCanvas does not currently use AppIntents:

Metadata extraction skipped. No AppIntents.framework dependency found.

Swift test cannot write module caches

If running in a restricted environment, Swift may fail because it cannot write module caches. Run tests from a normal terminal session or allow Swift to write to the user cache directories.

Dragging feels wrong after connecting components

After creating a connector, InfraCanvas should return to Select mode. If dragging starts another connector instead, make sure you are on a current release.