-
Notifications
You must be signed in to change notification settings - Fork 479
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
xcodebuild fails on Xcode 12.1 (12A7403) with SwiftyBeaver as a dependency #434
Comments
|
thanks for the example and explanation. so it seems to be an |
|
@skreutzberger just wondering - were you able to reproduce it locally on your end? I tried on two different machines and given the steps above I could reproduce it. My conjecture also is that the problem lies with |
|
yes, I could reproduce it. I guess it is an SPM issue. |
|
I am closing the ticket for now until more people do report it |
|
hmm, is there any workaround with this? this is kind of important as it breaks CI pipelines... |
|
@skreutzberger just to update this - the issue still happens on 12.2 Xcode which was released recently; and is the latest version available. |
|
Hi @andylamp , did you manage to solve this issue? I'm having the same problem with SPM & SwiftyBeaver |
|
@delvinwidjaja as far as I can tell the issue is still present, @skreutzberger said he'd ignore it until it became a bigger issue (i.e.: more people reported it). Hope this helps. |
|
This project has been potentially breached and your app may be exposing private information. See issue #453 |
|
@IsaiahJTurner What a troll. WTF is just wrong with you abusing the Github notification system? I have reported you to Github for spam. If you want to advertise for a company or project then please do it the normal way and leave the SwiftyBeaver contributors alone. SWIFTYBEAVER HAS NOT BEEN BREACHED. SwiftyBeaver is an open-source framework and its used encryption is public, known and trusted since several years. Feel free to contribute source code which makes it safer from your point of view and the contributors and I will consider merging it. |
|
@skreutzberger dw mate, we all love the project; please keep up the good work! @IsaiahJTurner please stop harassing people with baseless claims stemming from ignorance. |
|
thank you @andylamp 🙏 |
|
@skreutzberger was broken in our CI environment for us too. Like @andylamp mentioned, all our other Swift Packages work fine, so I suspect there might be some package setting that causes this? (A bug in SPM surely, but maybe it can be mitigated.) Unfortunately we had to remove SwiftyBeaver 😦 in the meantime, would love to switch back at some point. |
|
Problem still valid on Xcode 12.5.1 |
First of, thanks for the amazing package 😄! Now, installing
SwiftyBeaverusing the Swift Package manager, as is shown withinREADMEfails when invoked through the command line. However, if the project is compiled from within Xcode everything works as expected.The steps to reproduce this are fairly simple:
SwiftyBeaverusing the Swift Package Manager,@main- that's the only thing I changed in the whole code generated.If I compile within Xcode IDE (even the use of the simulator) everything works as expected; should I go to the command line and type in the directory of the project
xcodebuildthen it fails with:Removing
SwiftyBeaverand adding another dependency seems to not generate the same issue (I tried withAlamofire).Hope this helps to resolve the issue!
The text was updated successfully, but these errors were encountered: