Troubleshoot fastlane launch_lite installation error

[jsonify]

The #Preview macro requires PreviewsMacros plugin which may not be available during SPM command-line builds, causing build failures on fresh Mac installations. Commented out the preview block to fix 'fastlane launch_lite' build errors.

Preview can be re-enabled when building in Xcode by uncommenting.

Fixes: error: external macro implementation type 'PreviewsMacros.SwiftUIView' could not be found for macro 'Preview(_:body:)'

[gemini-code-assist]

Summary of Changes

Hello @jsonify, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request addresses a critical build failure that occurred when using fastlane launch_lite on new Mac setups. The issue stemmed from the #Preview macro's reliance on a plugin that is not accessible during command-line builds via Swift Package Manager. By temporarily disabling the preview code, this change ensures successful builds for automated processes while providing clear guidance for developers to re-enable the feature when working within Xcode.

Highlights

• Build Error Resolution: This pull request resolves a build error encountered during fastlane launch_lite operations on fresh Mac installations, specifically related to the #Preview macro.
• Macro Plugin Dependency: The error was caused by the #Preview macro requiring the PreviewsMacros plugin, which is not available during Swift Package Manager (SPM) command-line builds.
• Preview Block Disablement: The #Preview block in SimplifiedMainView.swift has been commented out to prevent the build failure.
• Xcode Re-enablement: Instructions have been added to the code, noting that the preview functionality can be re-enabled by uncommenting the block when building within Xcode.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request addresses a build failure with fastlane launch_lite by commenting out the SwiftUI #Preview macro. While this is a functional workaround, I've suggested a more idiomatic and maintainable solution using the #if DEBUG conditional compilation flag. This ensures the preview is only compiled in debug builds (like in Xcode) and automatically excluded from release builds, which are common in CI/CD environments, thus preventing the build error without requiring manual code changes.