-
Notifications
You must be signed in to change notification settings - Fork 5.6k
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
FastlaneRunner lane swiftServerPort 2000 Killed: 9 #18933
Comments
I have seen this report before but I'm unable to reproduce it because it seems to be related to M1 chip. |
There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Friendly reminder: contributions are always welcome! Check out CONTRIBUTING.md for more information on how to help with This issue will be auto-closed if there is no reply within 1 month. |
This issue will be auto-closed because there hasn't been any activity for a few months. Feel free to open a new one if you still experience this problem 👍 |
Is there any news on this? we are having a similar issue with M1 chips |
Still don't have an M1 machine to fix this |
I think this is the same problem as in #18502 |
There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Friendly reminder: contributions are always welcome! Check out CONTRIBUTING.md for more information on how to help with This issue will be auto-closed if there is no reply within 1 month. |
Hello, theoretically this issue has been solved in #19555 and should be available in fastlane 2.204.0, but I'm still reproducing the issue in my M1 laptop: [09:51:13]: $ set -o pipefail && xcodebuild -scheme FastlaneRunner -project ./fastlane/swift/FastlaneSwiftRunner/FastlaneSwiftRunner.xcodeproj -destination 'generic/platform=macOS' build | tee /Users/roisg/Library/Logs/gym/App-FastlaneRunner.log | xcpretty Anyone has been able to make it work now with the new version? Is there anything else that I should be updating? |
Looks like the FastlaneRunner Xcode project is still not updated. |
@kikeenrique I'm not sure if this can be related, but since I upgraded to 2.204.1 (also in 1.204.0) I keep seeing the message: |
@rserentill could you provide a |
@kikeenrique Sure, here is the logs until the message appears. Let me know if you require the logs after it also: [✔] 🚀 |
Same as @rserentill, I'm always being asked to upgrade the FastlaneSwiftRunner even if I click These are my logs after executing [✔] 🚀 |
I think I now why it's always asking for upgrade. I would consider a PR soon. @roisg Can you see a build phase in FastlaneSwiftRunner.xcodeproj named FastlaneRunnerCopySigned? |
@kikeenrique yes, I see that phase: |
I have just found out that just after restarting my laptop, the fastlane build works perfectly with the 2.204.2 version. Now, if the build fails, or even if it success, re-running the same fastlane build will throw the error:
And it will be thrown forever until I restart my computer again. So it seems something is not being properly freed between executions? |
That's what I meant with Signed binaries in macOS can give problems due to caching. I've read in an apple forums about this problems, check https://developer.apple.com/forums/thread/669145 or https://developer.apple.com/documentation/security/updating_mac_software. But, the Code Sign on copy shall prevent these problems, at least I didn't manage to reproduce them again. |
Yes, @kikeenrique, you're right. After removing the "run script" phase that was doing a |
+ fix upgrades checks to avoid false not up-to-date messages.
The pull request #19914 that closed this issue was merged and released as part of fastlane 2.204.3 🚀 |
New Issue Checklist
Issue Description
I use Fastlane with swift, on Mac intel and m1, on this both machines I have the same failure
Command executed
I just excuse my lane `bundle exec fastlane updateProvisioning
Complete output when running fastlane, including the stack trace and command used
✅ fastlane environment ✅
Stack
System Locale
fastlane files:
`./fastlane/Fastfile.swift`
No Appfile found
fastlane gems
Loaded fastlane plugins:
No plugins Loaded
Loaded gems
generated on: 2021-06-21
The text was updated successfully, but these errors were encountered: