-
-
Notifications
You must be signed in to change notification settings - Fork 128
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
Build fails on Xcode 15 #730
Comments
So I'm struggling right now on 15 with a number of build errors, SwiftFormatPlugin is producing errors about not being able to write caches, i'm getting errors from "Argument type 'ImageResource' does not conform to expected type 'Resource'" in IconView.swift, and a few others. Trying at least to get fastlane working locally so i can grab some screenshots for our next app release. |
Well here's the Kingfisher image issue, i'll post a PR shortly |
@digitaldan Apple has fixed the plugin sandbox, only command plugins are allowed to write now. Lmk when you have a PR for Kingfisher ready and I can fix the plugins on top of it. |
thanks! |
So FYI, fastlane runs for me, launches simulators and runs through the automated UI tests, but can not take screenshots, not sure if this is the sandboxing issue affecting the swiftformat plugin ? also that reminds me i have a fix for the UI tests not working with the main UI (not sure if there was a main UI dom change or what). I'll submit that soon too. |
@digitaldan looks like the UITests are failing because some element can't be found. Just try running without fastlane and you should see where it's failing:
|
So with my PR #733 , i'm not seeing those errors, at least not in the xcode console log (maybe somewhere else). Its strange b/c at the begining of the log it shows this:
But then at the end it shows everything passed, and there was no other failures listed in between
I'll keep looking at it, not sure what the deal is . |
New bug checklist
Describe the bug
Build fails on Xcode 15
Expected behavior
Build on latest platform
The text was updated successfully, but these errors were encountered: