error: Signing for "target" requires a development team. Select a development team in the Signing & Capabilities editor. (in target 'target' from project 'libtarget')

Question

error: Signing for "target" requires a development team. Select a development team in the Signing & Capabilities editor. (in target 'target' from project 'libtarget')

luca992 opened this issue 3 years ago · 9 comments

I'm trying to build this crypto library to a library for ios: https://github.com/dfoxfranke/libaes_siv

    cmake .. \
    -G Xcode -DCMAKE_TOOLCHAIN_FILE=../../ios-cmake/ios.toolchain.cmake -DPLATFORM=OS64
    cmake --build .

Is failing with:

error: Signing for "aes_siv" requires a development team. Select a development team in the Signing & Capabilities editor. (in target 'aes_siv' from project 'libaes_siv')
error: Bundle identifier is missing. demo doesn't have a bundle identifier. Add a value for PRODUCT_BUNDLE_IDENTIFIER in the build settings editor. (in target 'demo' from project 'libaes_siv')
error: Bundle identifier is missing. runtests doesn't have a bundle identifier. Add a value for PRODUCT_BUNDLE_IDENTIFIER in the build settings editor. (in target 'runtests' from project 'libaes_siv')

Any idea what I'm doing wrong?

Btw, I opened the generated the generated xcode project and theres not even an option to set the development team for the aes_siv target.

parcool commented 3 years ago

Mark

Answer 1 · 2022-04-20T17:48:03.000Z

Seems releated to this:

https://stackoverflow.com/questions/71320584/flutter-build-ios-got-error-requested-but-did-not-find-extension-point-with-ide/71503876#71503876

I'm going to try downgrading xcode 13.3.1, none of those workaround helped

Answer 2 · 2022-04-20T19:46:37.000Z

Downgrading to 13.2.1 worked.

Answer 3 · 2022-07-19T08:58:19.000Z

you can set project-wide development team with -DCMAKE_XCODE_ATTRIBUTE_DEVELOPMENT_TEAM=your_team

I opened the generated the generated xcode project and theres not even an option to set the development team

you must switch settings type on top from Basic to All

Answer 4 · 2023-03-03T10:40:58.000Z

I am running into the same issue. I just want to build a shared library for iOS and not sign anything.

The interesting part is building from Xcode itself works. But building via cmake or xcodebuild hits the issue.

Answer 5 · 2023-03-03T10:48:36.000Z

I am running into the same issue. I just want to build a shared library for iOS and not sign anything.

The interesting part is building from Xcode itself works. But building via cmake or xcodebuild hits the issue.

you can force no signing with CODE_SIGNING_ALLOWED=NO option to xcodebuild. If building with cmake, you'd pass it as cmake --build . -- CODE_SIGNING_ALLOWED=NO

Answer 6 · 2023-03-03T11:00:43.000Z

I am running into the same issue. I just want to build a shared library for iOS and not sign anything.
The interesting part is building from Xcode itself works. But building via cmake or xcodebuild hits the issue.

you can force no signing with CODE_SIGNING_ALLOWED=NO option to xcodebuild. If building with cmake, you'd pass it as cmake --build . -- CODE_SIGNING_ALLOWED=NO

Thanks! That solved the issue. Weirdly enough that property was already set inside Xcode itself. I wonder why that is the case.

Answer 7 · 2023-03-03T11:02:31.000Z

it might be a similar-looking property CODE_SIGNING_REQUIRED which doesn't have any effect I think

Answer 8 · 2023-03-03T11:03:39.000Z

it might be a similar-looking property CODE_SIGNING_REQUIRED which doesn't have any effect I think

I just checked and you are correct. Thanks a lot for the help. Xcode is confusing to work with at best and outright problematic at worst.