Possible Strategy to use SwiftUI snapshots on a mac with ImageRenderer #888
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
assertSnapshot(of: Text("Hello"), as: .image)will not compile or give runtime crash due to missing frameSnapShotting. There the.imagefor a SwiftUI view only exists if the format is a UIImage, but on macOS that does not existI added a test that runs on macOS and IOS and produces a snapshot. It uses
ImageRendererwhich is only available as of iOS 16 and also on macOS it requires at least 13. So using it is not a general solution. It however solves/bypasses the issues I had with making a simple snaphot of a swiftUI view.I'm not sure this is a good solution or more of a workaround? But I think it might document a problem and could be a strategy for some?
Might relate to issue #428, #533