-
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
[snapshot][examples] Fixed broken example project for trying out fastlane snapshot feature #18797
[snapshot][examples] Fixed broken example project for trying out fastlane snapshot feature #18797
Conversation
deprecated `XCUIDevice()` calls
recommended one
…ed one) for all targets
…lane snapshot init command
…with Snapfile like in documentation
We keep the old configuration settings to ensure compatibility with all further versions. This project must be unchanged she if something fails to compile I think we rather fix the issue than changing the whole project. |
@minuscorp This update is needed 😀👇 The project itself was super old and needed an upgrade. This seems like a good update so the project actually does run 😇 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
One thing that feels a little bit weird about this is the SnapshotHelper.swift
file being committed into the project because it could become out of date. But at the same time... the project works perfectly by just running fastlane snapshot
and it's super easy to update SnapshotHelper.swift
when running the example project again.
The upgrade to Swift 5 is also totally needed! This is 🔥 Thanks so much for fixing this!
Thanks @joshdholtz @minuscorp for feedback, really appreciate it! The deployment target is set to iOS 12 because that's what Xcode recommended. I can change it to some lower version, like iOS 9. However anything below iOS 9 is just... ridiculous 🙃 I'd not touch the Objective-C code since there is so much point of rewriting that part other than just getting rid of Objective-C for the sake of it. I'd like to keep the changes to |
Just for the record, in the fastlane Swift project we support down to Swift 4 settings, that's why I was afraid of bumping so much from Swift 3 (that we all know is deprecated), to avoid misalignment from the main project. Just as the SPM support stablishes as well, but we'd need to downgrade Xcode to a Swift 4 release and make the same changes that have been merged here. |
Hi, Thank you! |
Thanks, yes - that was my 1st PR :) Did I miss something then? |
Ahhh...no you did not miss anything but CI did not run unit-tests for this PR, CircleCI don't run unit-tests for 1st PR (maybe because of security issue 🤷♂️) Fastlane CI is running unit-tests with the old Xcode version too i.e |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Congratulations! 🎉 This was released as part of fastlane 2.185.0 🚀
Checklist
bundle exec rspec
from the root directory to see all new and existing tests passbundle exec rubocop -a
to ensure the code style is validMotivation and Context
Recently I decided to use
fastlane snapshot
for the first time. However I encounter the same issue as here: #18722I tried to use minimal environment to see if it's working with bare minimum and decided to use this documentation:
https://docs.fastlane.tools/getting-started/ios/screenshots/ and clone the test code:
However it doesn't even build because the sample code is simply outdated.
Description
snappy
lane and stick withSnapfile
Testing Steps
Just running
fastlane snapshot
like in documentation to see if I can get screenshots right.