-
Notifications
You must be signed in to change notification settings - Fork 333
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
CodeQL breaks iOS builds #2347
Comments
Thanks for opening this issue. We rely on Rosetta 2 being installed on an arm-based macOS runners for CodeQL to work correctly. CodeQL should only be initialised as late as possible in your workflow (i.e. after all setup steps, but before the actual build starts), so putting it after your "Setup Git and iOS dependencies" step makes sense. If I understand correctly, with that ordering, Rosetta 2 gets installed successfully? We would probably need to see more of the logs to understand what's causing the issue in the fastlane step later on. If you can share more publicly here, then that would be great. Otherwise, you can open a support ticket referencing this issue and we can pick things up from there. |
@mbg Thank you, it might be easier via a support ticket - I have opened one (ID 2847745), however I was unable to provide complete logs with it as they were too big and the ticket form wouldn't accept them. Please let me know on that ticket what is the best way forward. |
If you don't mind, please share whatever solution you came up with in the support ticket publicly here as well if possible. I have very similar issues and have been following #2043 for a long time. @mbg do you think I'd be better off opening my own support ticket? Please let me know if you do not think my issue is related and I'll happily delete my comment to keep the issue clean and clear. Cross-posting my message from that ticket here for convenience:
And later these logs were attached:
|
@jakobholmgrenhiq: 👋 No worries for asking here -- since you have been able to share your logs already, I don't currently see any reason for you to open a support ticket. I have read through the discussion in #2043 as well. Currently, it's unclear what the issue that In the meantime, a few suggestions:
|
@mbg Hi, I have attached the logs to the support ticket (ID 2847745). Thanks! |
I see the zendesk ticket has been closed. Is this issue still relevant? |
@redsun82 I didn't manage to reply to the ticket in time and it auto-closed. I have replied and reopened it now. This issue is still relevant and we still don't have CodeQL working in our iOS repositories. |
👋 @ls-valentinas-bakaitis sorry to hear that! Sorry if I'm a bit confused about the error of the build, as sifting through this issue I see three different errors being mentioned:
The latter might be worked around by passing |
@redsun82 I am experiencing compile errors like this one:
There are more like it in the log, but they all look similar. Note that when I remove the I have attached the logs to the support ticket (ID 2847745) - these are private jobs in private repos so I don't want to share them publicly, but happy to share them privately. |
@redsun82 another log entry that appears in our workflow logs is this:
It doesn't seem to stop the run though, so I'm not sure if it's related or not 🤔 |
hi @ls-valentinas-bakaitis thanks for reaching back. It seems like there's a problem with injecting our tracer into some binaries (I see at least What I would check next, is
I'm afraid that if it's an |
both
I did try using the Thank you for your help confirming that it's not going to work at this time. I understand that there is no easy fix, but Apple discontinued intel based machines a little while ago and we need a way to run code-ql on Apple silicon. Once GitHub starts working on this problem - I would be more than happy to help do some beta testing. |
Hey 👋, I'm the product manager looking over Swift support. I just wanted to reach out to confirm that for the time CodeQL will continue to require Rosetta to work. We don’t have any very short term plans to support Apple silicon, but we will continue to track this internally and reach out when we start work on that project. |
@coadaflorin thank you! We have decided to use a third party tool for iOS scanning in the meantime, but would be very interested to try CodeQL for iOS again once it has support for Apple silicon. Let us know if you need beta testers. We have quite a few iOS repos and would love to try it out once it's ready. |
Hi,
I'm trying to roll out CodeQL scanning to some of our iOS (swift) repositories and I have issues with CodeQL breaking the build steps. The same steps that succeed by themselves will fail when CodeQL init is added before them.
If I run this workflow with CodeQL step commented out, it succeeds:
However once CodeQL init portion is uncommented I get this error in the "Setup Git and iOS dependencies" step:
If I try to move CodeQL init after the "Setup Git and iOS dependencies" step, then the next step breaks - there are too many log lines to post here, but this is the error that occurs at fastlane step when CodeQL init is included just before it:
It looks like CodeQL init is doing something that is making
Rosetta 2
installation and subsequentfastlane
compilation fail.The text was updated successfully, but these errors were encountered: