Closed shpuntov closed 3 years ago
Hi @shpuntov,
Can you please share a build log and enable support access?
Hi @non-binary,
I've enabled support access for the app https://app.bitrise.io/app/b338271a50f1ffd0 And here's the build log: 69aae9b99fd24c0e.log
@shpuntov I see you have a green build. Are you still experiencing this?
@non-binary yes, problem is still there. My build is green because I have had to hack my .pbproj
to make it works. It's very dirty hack, and it's unstable: every change of my Xcode project removes this hack, and I have to add it again, otherwise build gets failed. I described this in details in the head post of this issue. And I even made an assumption why this could happen. 😄
@non-binary I have to add this block in my Xcode project file:
TargetAttributes = {
E3E19E43236C75B5004FC698 = {
};
E3E19E51236C75BE004FC698 = {
};
E3E19E5F236C75C7004FC698 = {
};
};
The step is failed if I don't do this. At the same time Xcode don't want to have this block in project file, and removes it each time I make changes in my project (e.g. add a file). Only you guys can help here and fix your step behaviour.
@shpuntov Ah, I see. Thanks for clarifying. I will share this with our tooling team.
Hi, i'm experiencing the same issue. did you find a workaround ?
Hi, i'm experiencing the same issue. did you find a workaround ?
I did. See my post above, it's mostly about workaround.
I have the same issue
I'm experiencing the same issue in a React Native project
@non-binary any updates on this?
Unfortunately no update yet.
Having the same issue, switched over because it was promoted to do so already so I hoped it would be stable release, but it's not working at all for me now
I managed to reproduce it, for example if you duplicate a target, Xcode will not generate TargetAttributes
for it.
@godrei I'm experiencing this issue with the project I've created on November 2019, with the most recent Xcode version at that moment, so I wouldn't say that this project is too old (as they say here).
I've just tried to switch project format from 9.3 to the most recent 12.0, and here is what I've got: So even on the most recent project format it still tries to remove this TargetAttributes
node.
I've tried to create a new project, but it does contain TargetAttributes
node. So I can't say exactly why my project removes this node on every change. I have no ideas, sorry about that.
Hi there.
ios-auto-provision-appstoreconnect
step failed with the following logs:When I add the following node into my
.pbproj
file (at pathobjects
/E3E19E12236C4564004FC698 /* Project object */
/attributes
), the step works without the issue.But each time I change something in the project, Xcode automatically removes this node, and the step get failed again.
This is happen with v2 version of my app, corresponding Xcode project has been created in October 2019, and obviously it uses a bit more modern
.pbproj
format, which doesn’t includeTargetAttributes
node. The old v1 project (which has been created in 2015) does contain this node, and Xcode keeps it on project changes saving (and even keeps some info inside a certain target node, likeSystemCapabilities
and so on). From my point it looks like the step relies on a project structure which a bit outdated at the moment. Interesting, that once the step is able to findTargetAttributes
and target identifier node inside, it thinks that everything is ok, so even emptyE3E19E43236C75B5004FC698
subnode works.Could you please update your step regarding this aspect, or let me know what I could do on my side. Obviously, I do want to use new
ios-auto-provision-appstoreconnect
step rather than the old oneios-auto-provision
. Thanks.