iOS Auto Provisioning Step not working with Xcode 11 beta

code-signing
xcode
ios-auto-provision
#1

The current version 1.3.1 of the auto provisioning step doesn’t seem to work with the latest Xcode 11 beta 7. The xcodeproj file format is not supported or something like that.

1 Like

#2

Hi @matthias.buchetics! I believe what should be causing the problem is Apple changing the structure of the certificates in Xcode 11 and the latest step version isn’t ready to deal with those yet.

But just to be sure, can you send us a build URL to see what transpires? :slight_smile:

0 Likes

#3

I raised a similar issue here Xcode 11 b4 build fails when there are Swift Packages in the project

Nothing seems to have happened. I’ve removed the Swift Package manager dependencies, and now I get failures on [Xcodeproj] Unknown object version.

0 Likes

#4

Here’s the latest build log https://app.bitrise.io/build/bdfc907cda6fcc5a#?tab=log

0 Likes

#5

I’ve worked around it by setting the Xcode project format to Xcode 10 compatible.

0 Likes

#6

https://app.bitrise.io/build/6bacf18f6c145b70

We still have this issue.

0 Likes

#7

Hi, I’m having similar issues building with the Xcode 11.1 stack.
Here are the errors I got durring the auto provision step.

Do you know how I can fix this?
I have my projet format set to be compatible with Xcode 10.

±-----------------------------------------------------------------------------+

| (4) ios-auto-provision |
±-----------------------------------------------------------------------------+
| id: ios-auto-provision |
| version: 1.3.1 |
| collection: https://github.com/bitrise-io/bitrise-steplib.git |
| toolkit: bash |
| time: 2019-09-30T12:19:40Z |
±-----------------------------------------------------------------------------+
| |
$ bundle install
$ bundle exec ruby /var/folders/6q/wgy6jtp12w5gzgm9lzcglpqw0000gn/T/bitrise735519254/step_src/step.rb
[!] Xcodeproj doesn’t know about the following attributes {“productRef”=>“47D5C825233213E600EDB7C3”} for the ‘PBXBuildFile’ isa.
If this attribute was generated by Xcode please file an issue: https://github.com/CocoaPods/Xcodeproj/issues/new
[!] Xcodeproj doesn’t know about the following attributes {“productRef”=>“47D5C823233213E600EDB7C3”} for the ‘PBXBuildFile’ isa.
If this attribute was generated by Xcode please file an issue: https://github.com/CocoaPods/Xcodeproj/issues/new
[!] Xcodeproj doesn’t know about the following attributes {“packageProductDependencies”=>[“47D5C823233213E600EDB7C3”, “47D5C825233213E600EDB7C3”]} for the ‘PBXNativeTarget’ isa.
If this attribute was generated by Xcode please file an issue: https://github.com/CocoaPods/Xcodeproj/issues/new
[!] Xcodeproj doesn’t know about the following attributes {“packageReferences”=>[“47D5C822233213E600EDB7C3”]} for the ‘PBXProject’ isa.
If this attribute was generated by Xcode please file an issue: https://github.com/CocoaPods/Xcodeproj/issues/new
Params:
team_id: ******
certificate_urls: ***
min_profile_days_valid: 0
passphrases: ***
distribution_type: app-store
project_path: Cocorico.xcworkspace
scheme: Cocorico
configuration: Release
build_url: https://app.bitrise.io/build/e51f91abb57d9534
build_api_token: ***
keychain_path: /Users/vagrant/Library/Keychains/login.keychain
keychain_password: ***
verbose_log: no
generate_profiles: yes
Developer Portal authentication
Session loaded from environment variable is not valid. Continuing with normal login.
authenticated
Downloading Certificates
2 certificate files downloaded, 2 distinct codesign identities included
Identify Certificates on Developer Portal
iOS Development certificate found: iPhone Developer: publisher Lunabee (G4HQ57A7WP) [108801665197374252]
Analyzing project
Error:
[Xcodeproj] Unknown object version.
Stacktrace (for debugging):
/Users/vagrant/.rbenv/versions/2.6.3/lib/ruby/gems/2.6.0/gems/xcodeproj-1.7.0/lib/xcodeproj/project.rb:223:in initialize_from_file' /Users/vagrant/.rbenv/versions/2.6.3/lib/ruby/gems/2.6.0/gems/xcodeproj-1.7.0/lib/xcodeproj/project.rb:108:inopen’
/private/var/folders/6q/wgy6jtp12w5gzgm9lzcglpqw0000gn/T/bitrise735519254/step_src/lib/autoprovision/project_helper.rb:273:in block in archivable_target_and_container_project' /private/var/folders/6q/wgy6jtp12w5gzgm9lzcglpqw0000gn/T/bitrise735519254/step_src/lib/autoprovision/project_helper.rb:263:ineach’
/private/var/folders/6q/wgy6jtp12w5gzgm9lzcglpqw0000gn/T/bitrise735519254/step_src/lib/autoprovision/project_helper.rb:263:in archivable_target_and_container_project' /private/var/folders/6q/wgy6jtp12w5gzgm9lzcglpqw0000gn/T/bitrise735519254/step_src/lib/autoprovision/project_helper.rb:298:inblock in read_scheme_archivable_target_and_container_project’
/private/var/folders/6q/wgy6jtp12w5gzgm9lzcglpqw0000gn/T/bitrise735519254/step_src/lib/autoprovision/project_helper.rb:294:in each' /private/var/folders/6q/wgy6jtp12w5gzgm9lzcglpqw0000gn/T/bitrise735519254/step_src/lib/autoprovision/project_helper.rb:294:inread_scheme_archivable_target_and_container_project’
/private/var/folders/6q/wgy6jtp12w5gzgm9lzcglpqw0000gn/T/bitrise735519254/step_src/lib/autoprovision/project_helper.rb:24:in initialize' /var/folders/6q/wgy6jtp12w5gzgm9lzcglpqw0000gn/T/bitrise735519254/step_src/step.rb:43:innew’
/var/folders/6q/wgy6jtp12w5gzgm9lzcglpqw0000gn/T/bitrise735519254/step_src/step.rb:43:in `’
| |
±–±--------------------------------------------------------------±---------+
| x | ios-auto-provision (exit code: 1) | 35.18 sec|
±–±--------------------------------------------------------------±---------+
| Issue tracker: …github.com/bitrise-steplib/steps-ios-auto-provision/issues |
| Source: https://github.com/bitrise-steplib/steps-ios-auto-provision |
±–±--------------------------------------------------------------±---------+

0 Likes

#8

Hi!

Could you please try the newest version of the step 1.3.2?
We updated the Xcodeproj dependency, hopefully it solves the issue for you.

0 Likes

#9

I can’t see it in the versions list.
The last I can choose is 1.3.1.

0 Likes

#10

Hmm… It seems it was released 2 hours ago.
It could take some time to make it available in the Workflow editor.

Check it again a little later :upside_down_face:
If still not available, then try to clean the cache/use incognito/select always latest.

0 Likes

#11

Ok I’ll try later and let you know.
I’m already in always latest on all my steps.

Thanks a lot for your help.

0 Likes

#12

1m

Hi,

I tested the 1.3.2 version and it fixes the previous issue.
Now, I have this error but I have a Distribution profile defined in my app.

Error:

Selected distribution type: app-store, but forgot to provide a Distribution type certificate.

Don’t worry, it’s really simple to fix! :slight_smile:

Simply upload a Distribution type certificate (.p12) on the workflow editor’s CodeSign tab and we’ll be building in no time!

Stacktrace (for debugging):

/private/var/folders/6q/wgy6jtp12w5gzgm9lzcglpqw0000gn/T/bitrise326158526/step_src/lib/autoprovision/certificate_helper.rb:103:in `ensure_certificate’

/var/folders/6q/wgy6jtp12w5gzgm9lzcglpqw0000gn/T/bitrise326158526/step_src/step.rb:76:in `’

I think this step is not compatible with Xcode 11 certificates yet.
Do you know when it will be fixed? (there is also an issue with the Project Info step not being able to read the new marketing version format).

1 Like

#13

I’m having the exact same error

0 Likes

#14

I think this could happen because of the new type of Apple certificates. :thinking:
We are working on the fix for it, hopefully we will release a fix soon.

1 Like

#15

If it can helps, I’ve also this error message on a project which was created with Xcode 11 for iOS 13 only:


Developer Portal authentication
Session loaded from environment variable is not valid. Continuing with normal login.
authenticated
Downloading Certificates
1 certificate files downloaded, 1 distinct codesign identities included
Identify Certificates on Developer Portal
Error:
no development nor production certificate identified on development portal
Stacktrace (for debugging):
/private/var/folders/6q/wgy6jtp12w5gzgm9lzcglpqw0000gn/T/bitrise086423038/step_src/lib/autoprovision/certificate_helper.rb:166:in identify_certificate_infos' /private/var/folders/6q/wgy6jtp12w5gzgm9lzcglpqw0000gn/T/bitrise086423038/step_src/lib/autoprovision/certificate_helper.rb:43:indownload_and_identify’
/var/folders/6q/wgy6jtp12w5gzgm9lzcglpqw0000gn/T/bitrise086423038/step_src/step.rb:37:in `’
| |
±–±--------------------------------------------------------------±---------+
| x | ios-auto-provision (exit code: 1) | 40.18 sec|
±–±--------------------------------------------------------------±---------+
| Issue tracker: …github.com/bitrise-steplib/steps-ios-auto-provision/issues |
| Source: https://github.com/bitrise-steplib/steps-ios-auto-provision |
±–±--------------------------------------------------------------±---------+


I have a certificate in the signing settings for my workflows but it is a new Xcode 11 certificate (Apple Distribution) so I think this is linked to the issue currently being fixed.



Edit:
It is now working!!

Thanks a lot.

The last issue I now have due to Xcode 11 changes is with the Xcode Project Info step which is now giving me “$MARKETING_VERSION” in the $XPI_VERSION workflow env var instead of the version number.

2 Likes

#16

Thanks for the update!

And for everyone’s patience, just wanted to make sure we note here for everyone to see, that the step was updated last week and is able to deal with the new Xcode 11 type of certificates too, for version 1.4.0 and above :slight_smile:

0 Likes

#17

I am also experiencing this issue, with “$MARKETING_VERSION” appearing in $XPI_VERSON, instead of the version number. Xcode 11 moved the the actual version number from Info.plist into the project file, assigning the version number to the $MARKETING_VERSION variable, and putting a reference to $MARKETING_VERSION in the Info.plist, in place of the version number.

Is there a workaround for this issue? Can the Xcode Project Info step be updated to work with Apple’s new structure?

0 Likes