Errors while building

[petele]

I'd love to help out, but am having trouble getting started. When I try to compile/run, I get the following error:

$ flutter run -d macos
Launching lib/main.dart on macOS in debug mode...
The following plugins do not support Swift Package Manager for macos:
  - auto_updater_macos
  - libdivecomputer_plugin
  - objectbox_flutter_libs
  - submersion_ocr
  - submersion_transcoder
This will become an error in a future version of Flutter. Please contact the plugin maintainers to request Swift Package Manager adoption.
warning: Run script build phase '[CP-User] Build libdivecomputer' will be run during every build because it does not specify any outputs. To address this issue, either add output dependencies to the script phase, or configure it to run in every build by unchecking "Based on dependency analysis" in the script phase. (in target 'libdivecomputer_plugin' from project 'Pods')
/Users/petele/Sites/submersion/macos/Runner.xcodeproj: error: No profiles for 'app.submersion' were found: Xcode couldn't find any Mac App Development provisioning profiles matching 'app.submersion'. Automatic signing is disabled and unable to generate a profile. To enable automatic signing, pass -allowProvisioningUpdates to xcodebuild. (in target 'Runner' from project 'Runner')
warning: Run script build phase 'Run Script' will be run during every build because it does not specify any outputs. To address this issue, either add output dependencies to the script phase, or configure it to run in every build by unchecking "Based on dependency analysis" in the script phase. (in target 'Flutter Assemble' from project 'Runner')
** BUILD FAILED **

Building macOS application...
Error: Build process failed

I'm running on macOS 27, XCode 27, Flutter 3.47.5, Dart 3.13.4.

I suspect I'm missing something easy/silly and would love a little help please.

Thanks,
PEte

[HariomAcharya17]

The build fails because Xcode doesn't have permission to sign the app with the name app.submersion. That name belongs to the project's owner. The other messages are just warnings, so you can ignore them.

Fix it in 5 steps:

1.In Terminal, run:
open macos/Runner.xcworkspace
2.In Xcode, click Runner in the left sidebar, then click the Runner target, then the Signing & Capabilities tab.
3.Tick Automatically manage signing, then pick your Team. If you don't see one, go to Xcode > Settings > Accounts and add your Apple ID (a free one works).
4.Change the Bundle Identifier to something unique to you, for example com.petele.submersion.
5.Go back to Terminal and run:
flutter run -d macos

if you find this helpfull please mark as answered

[ericgriffin]

Hi Pete, thanks for the report, and sorry for the slow follow-up. This was a gap in our docs rather than anything you did wrong. flutter run -d macos builds the Debug configuration, which was pinned to the maintainer's Apple Developer team, so nobody outside that team could get a provisioning profile for app.submersion.

#2186 (merged shortly after you posted) documents the way through: sign the debug build ad-hoc, which needs no Apple account at all. See Running a debug build without an Apple Developer account. In short:

1. In Xcode, select the Runner target, go to Signing & Capabilities > Debug, uncheck Automatically manage signing and set Team to None.
2. Replace macos/Runner/DebugProfile.entitlements with the account-free version shown in the README.

Then flutter run -d macos builds and runs with hot reload. iCloud sync, push notifications and Google Sign-In are unavailable in that build; everything else works. Please keep those two edited files out of your PRs. (#2944 also adds the camera permission to that README block, so camera scanning works in the ad-hoc build too.)

About picking your own team and changing the bundle ID: that usually fails as well, because the debug entitlements request the iCloud.app.submersion container and the group.submersion app group, which belong to the maintainer's team. The ad-hoc route sidesteps all of that.

Linux, Windows, Android and the iOS Simulator need no signing changes. Physical iPhone builds are still blocked, tracked in #2188. The Swift Package Manager and "Run script build phase" lines are only warnings and can be ignored.

Thanks for wanting to help, and let us know if you hit anything else.