-
Notifications
You must be signed in to change notification settings - Fork 39
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[TEALIUM SWIFT BUG]: xcodebuild timed out while trying to read ConsentManagerDemo.xcodeproj #133
Comments
Temporary workaround: Have opened the UPDATE: Any subsequent clean builds still fail to pass carthage builds. UPDATE No.2: Using SPM for Tealium seems to be reaping more success than using Carthage. |
@surpher just confirming that we've seen this and I've also spoken to the support team who are dealing with your ticket. Looking into it and will aim to get you an update soon. Glad you were able to get a temporary workaround with SPM. Carthage should not be building that project, since that's just one of the sample apps... not sure why that's happening in your CICD env. Thanks for all the info you've provided. |
@surpher Looking into this, I noticed something slightly strange about your environment, which I haven't got to the bottom of - wonder if you can help: My Xcode version is also 11.3.1, but build 11C504, whereas yours is 11C505. Your build number isn't on the Apple releases page: https://developer.apple.com/news/releases/ This exact issue appears to have happened previously for other SDKs using Carthage, and it seemed it was traced back to an xcode bug. See: Carthage/Carthage#2104 I also have a sneaking suspicion (may well be incorrect) that this may be related to a Carthage bug we found recently with binary framework dependencies (we had to use a binary framework dependency from our own repo to deal with some issues in PLCrashReporter... it's a shame Carthage doesn't allow you to exclude schemes to build, as this is an optional module, but Carthage forces you to build all schemes in a project). See: Carthage/Carthage#2940 Thanks for your patience; hopefully we'll get to the bottom of this soon. |
Hi there. Tried and got the following:
Edit: I’ll run it again with a bit more focus on what I’m running. Maybe it was still baked in through SPM. Not sure, so I’ll double check. |
@surpher it definitely builds ok for us. I'm curious about the log message |
Yeah, I'm struggling to find a time to test this properly. It might have been that Tealium was still in the project through SPM? Not sure. Need some more time to figure out how to confirm this properly. |
No problem @surpher. Whenever you get time. It's possible it was SPM interfering, but hard to say. |
Sorry guys but I have had no luck with I have even created a brand spanking new (and blank) Xcode iOS project (Xcode 11.3.1), copied the Running the following carthage command (to avoid unnecessary 30 minute builds of the ridiculously big
It kept failing due to dependency graph containing a cycle even when I removed each and every other dependency one by one:
Tried just a simple Carthage version 0.34.0 In the original project, I have also noticed that even when getting rid of the SPM package (tealium-swift in this case), it still persisted in the |
@surpher Could you possibly try editing your cartfile for me, and add the branch name "1.9.4"?
I was unable to reproduce your issue, running the exact same commands as you, but I believe switching to the binary dependency for the crash reporter module should solve the problem. Once you confirm it fixes your build issue, we'll publish this to master. Thanks for your patience. |
@surpher that's great. Sincere apologies that you've had this issue, but hopefully it's now closed once and for all, and we've added some steps to our Carthage testing process to hopefully catch these issues in future. Thanks for bearing with us. We'll get this put up as a full release today. |
Your Environment
Fill out as appropriate.
iOS Version(s) [e.g. 12.1]: 10...13.x
Xcode version [Xcode> About Xcode e.g. 10.1 (10B61)]: 13.1 (11C505)
Swift version [e.g. 4.2]: 5
Tealium Swift library version [e.g. 1.6.7]: 1.9.1
Dependency manager [None/Carthage/CocoaPods]: Carthage
Dependency manager version: 0.33.0
Describe the bug
When running builds on the CI machine the builds consistently fail at building the dependencies due to
xcodebuild timed out while trying to read ConsentManagerDemo.xcodeproj
.Even though we are using
carthage bootstrap ... --cache-builds
, the cache got invalidated and when trying to rebuild, we are hitting this issue.Does a workaround exist?
Not that we have found one. Also we do not want to check-in the dependencies.
Update: using SPM for Tealium dependency. (We're running two dependency managers for our project. Far from ideal.)
To Reproduce
Steps to reproduce the behavior. If applicable, please attach sample code showing how to reproduce the bug. Remember to keep your Tealium account details private, and only post generic code. Additional code or crash logs may be shared with us privately on [email protected].
carthage bootstrap ...
(see the log below)Expected behavior
Dependencies along with Tealium to build without timing out.
Screenshots
Additional context
Builds just fine on developer machines running 15" MacBook Pro.
The text was updated successfully, but these errors were encountered: