bitrise-steplib / steps-ios-auto-provision-appstoreconnect

MIT License
15 stars 16 forks source link

Project Path input not used? #28

Closed sregg closed 3 years ago

sregg commented 3 years ago

Here's the error I get:

+------------------------------------------------------------------------------+
| (1) ios-auto-provision-appstoreconnect@0                                     |
+------------------------------------------------------------------------------+
| id: ios-auto-provision-appstoreconnect                                       |
| version: 0.1.1                                                               |
| collection: https://github.com/bitrise-io/bitrise-steplib.git                |
| toolkit: go                                                                  |
| time: 2020-11-25T22:01:57Z                                                   |
+------------------------------------------------------------------------------+
|                                                                              |
Config:
- BuildAPIToken: [REDACTED]
- BuildURL: https://app.bitrise.io/build/dafd7669b0e6adfe
- ProjectPath: ios/idvpoc.xcworkspace
- Scheme: idv
- Configuration: Release
- Distribution: ad-hoc
- MinProfileDaysValid: 0
- CertificateURLList: [REDACTED]
- CertificatePassphraseList: 
- KeychainPath: /Users/vagrant/Library/Keychains/login.keychain
- KeychainPassword: *****
- VerboseLog: false
Creating AppstoreConnectAPI client
the client created for https://api.appstoreconnect.apple.com/
Analyzing project
Failed to analyze project: failed to find build project: No file found at path: /Users/vagrant/git/ios/idv.xcodeproj/project.pbxproj

see ios/idv.xcodeproj is different than the input ProjectPath: ios/idvpoc.xcworkspace

bitce commented 3 years ago

Hi @sregg! Can you include an URL to a build where this happens please? If possible also turn on Support User access in the Settings. Thanks!

sregg commented 3 years ago

https://app.bitrise.io/build/dafd7669b0e6adfe Support User Access is ON I managed to workaround this issue by changing the name of the scheme to match the target/app

bitce commented 3 years ago

Thanks!

Can you please check the following?

  1. Is the scheme idv shared for actions?
  2. Could this scheme have project file provided instead of workspace file as a Containter? This could cause the step try to parse an xcodeproj file instead.
sregg commented 3 years ago

Hi Bence,

We realized the scheme was not properly setup. Feel free to close the issue.

github-actions[bot] commented 3 years ago

Hello there, I'm a bot. On behalf of the community I thank you for opening this issue.

To help our human contributors focus on the most relevant reports, I check up on old issues to see if they're still relevant. This issue has had no activity for 90 days, so I marked it as stale.

The community would appreciate if you could check if the issue still persists. If it isn't, please close it. If the issue persists, and you'd like to remove the stale label, you simply need to leave a comment. Your comment can be as simple as "still important to me".

If no comment left within 21 days, this issue will be closed.

github-actions[bot] commented 3 years ago

I'll close this issue as it doesn't seem to be relevant anymore. We believe an old issue probably has a bunch of context that's no longer relevant, therefore, if the problem still persists, please open a new issue.