Comments (11)
I'm also seeing this same issue, basically it fails after it registers a new device to Apple developer portal, but the device is added successfully at the portal. Rebuilding the build until all new devices are registered and the build will eventually work.
from steps-ios-auto-provision-appstoreconnect.
I created a workflow loop to work around this when it showed up for us one late Friday night:
brute-force-provision:
description: |-
Workaround [ios-auto-provision-appstoreconnect #13](https://github.com/bitrise-steplib/steps-ios-auto-provision-appstoreconnect/issues/13).
Attempts auto-provision with minimum setup, and on pipeline failure triggers the same workflow to be run again.
steps:
- [email protected]:
run_if: '{{getenv "SSH_RSA_PRIVATE_KEY" | ne ""}}'
- [email protected]: {}
- [email protected]:
inputs:
- verbose_log: 'yes'
- distribution_type: "ad-hoc"
- trigger-bitrise-workflow@0:
run_if: ".IsBuildFailed"
is_always_run: true
inputs:
- workflow_id: brute-force-provision
- api_token: "$BITRISE_TRIGGER_TOKEN"
Client verbose logs are turned off in the step, so I couldn't see what the Apple API was returning that would cause the step to fail in this way:
We don't use Bitrise test devices functionality anymore, so the register stage in this step was superfluous for us, but I couldn't disable it as-written with a config option either.
from steps-ios-auto-provision-appstoreconnect.
Hi @kndl22
Thank you for reaching out to Bitrise.
Can you please share the screenshot of the error that you are getting when adding a new test device?
Also, for reference here is the document that you can follow to add new test devices to your bitrise account.
Thank you
Chaitanya
from steps-ios-auto-provision-appstoreconnect.
After reading this article, next time I'll try adding new device while using "Safari" browser and see if it happens again.
Seems that when using Chrome the popup isn't showing (probably blocked by ad-blocker).
Will update the next time i register new device :)
from steps-ios-auto-provision-appstoreconnect.
Thank you @kndl22 for the update.
Yes, please do.
Let me know if you have any questions or concerns.
Thank you
Chaitanya
from steps-ios-auto-provision-appstoreconnect.
Hi @chaitanyatanna-bitrise, I can confirm that the issue repeats every time we add a new test device manually to Bitrise (without adding it at the Apple's developer portal).
As I mentioned before, it happens only at the first build after adding the device; the next builds will pass successfully
from steps-ios-auto-provision-appstoreconnect.
Hi @kndl22
Thank you for the update. I will let the team regarding this issue.
Thank you
Chaitanya
from steps-ios-auto-provision-appstoreconnect.
We just started seeing this error this morning but have not recently added any devices nor changed anything with the build process.
EDIT:
As of 13:52EST, this error has gone away with no intervention on my part.
from steps-ios-auto-provision-appstoreconnect.
Hey @chaitanyatanna-bitrise any news regarding the issue?
from steps-ios-auto-provision-appstoreconnect.
Hi,
There is still no update on the ticket from engineering.
I will update you as soon as I hear back from the team.
Thanks
Chaitanya
from steps-ios-auto-provision-appstoreconnect.
Hi @kndl22, PR #19 solves this issue. Please open a new issue if you still experience the problem.
from steps-ios-auto-provision-appstoreconnect.
Related Issues (20)
- Fails with App Clip target HOT 13
- Fails with app clip target HOT 1
- Apple Development are supported ? or only IOS_DEVELOPMENT ? HOT 5
- App clip provisioning failing HOT 8
- Project Path input not used? HOT 6
- Fail to match iCloud container when re-using existing provisioning profile HOT 8
- Step reformatting of "pbxproj" file is breaking ionic-archive step HOT 10
- This repo suffer the same issue with mac device id HOT 5
- ios-auto-provision-appstoreconnect breaks agvtool HOT 4
- 1.0.1 version step.zip file is not accessible HOT 1
- Not signing UITest Target HOT 2
- Difference between automatic and api_key connections HOT 7
- Fails with App Clip target HOT 7
- `apple-id` Option mismatch between config.go and step.yml HOT 2
- `Should the step manage UITest target's codesigning?` setting ignored HOT 2
- SignUITestTargets: false not respected HOT 1
- Distribution is not set based on Env Var distribution_type HOT 3
- Suddenly fails to parse provisioning profiles HOT 11
- Automatic code signing failed HOT 6
- Automatic code signing failed HOT 3
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from steps-ios-auto-provision-appstoreconnect.