CodeScanner does not support provisioning profiles

Open
#97 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
swift

Research direction

Start by reviewing Package.swift and the CodeScanner_CodeScanner target referenced in the Xcode error, then compare its provisioning-profile settings with the consuming project and Pods-MyProject. Reproduce the Bamboo build failure and determine whether CodeScanner requires a project configuration change or a package change; done means the CI build succeeds without the provisioning-profile error.

Written by the indexing model from the issue text.

Description

bug

Hello for everyone,

I try to make CI by Bamboo and getting such error:

Users/mobosxbuilder/Library/Developer/Xcode/DerivedData/Tape-hiocgbvtxkwqzdasmpuzybalgako/SourcePackages/checkouts/CodeScanner/Package.swift: error: CodeScanner_CodeScanner does not support provisioning profiles. CodeScanner_CodeScanner does not support provisioning profiles, but provisioning profile MyProject has been manually specified. Set the provisioning profile value to "Automatic" in the build settings editor. (in target 'CodeScanner_CodeScanner' from project 'CodeScanner')

  /Volumes/Data/build-dir/AT-TTD-JOB1/MyProject/Pods/Pods.xcodeproj: error: Pods-MyProject does not support provisioning profiles. Pods-MyProject does not support provisioning profiles, but provisioning profile MyProject has been manually specified. Set the provisioning profile value to "Automatic" in the build settings editor. (in target 'Pods-MyProject' from project 'Pods')

But I use CodeScanner as SMP and do not know why this problem exist. Maybe I need to do another changes in my project?

Thank you!

Dominant language
Swift
Stars
1.2k
Forks
328
PR merge metrics
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from twostraws/CodeScanner

All issues in twostraws/CodeScanner

Similar issues

More Swift issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.