Revert "Revert "Merge pull request #1806 from firebase/nc/quickstarts""

[ncooke3]

Reverts #1811

[gemini-code-assist]

Summary of Changes

Hello @ncooke3, 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 reverts a revert, effectively reapplying the changes from an earlier pull request. It focuses on renaming targets within the project, updating scheme files, and removing a legacy project to streamline the codebase and project structure.

Highlights

• Reverts a previous revert: This PR undoes the changes made by Revert "Merge pull request #1806 from firebase/nc/quickstarts" #1811, which itself was a revert. This effectively reapplies the original changes from infra: Remove ObjC quickstarts #1806.
• Project file modifications: The core changes involve modifications to the project.pbxproj file, primarily updating target names and build configurations to remove the '(iOS)' suffix.
• Scheme file updates: Scheme files are renamed and updated to reflect the target name changes, ensuring the project builds and runs correctly with the new naming scheme.
• Removal of Legacy project: Removes the LegacyABTestingQuickstart project, cleaning up the project structure.

Ignored Files

• Ignored by pattern: .github/workflows/** (15)
  • .github/workflows/abtesting.yml
  • .github/workflows/analytics.yml
  • .github/workflows/authentication.yml
  • .github/workflows/check.yml
  • .github/workflows/config.yml
  • .github/workflows/crashlytics.yml
  • .github/workflows/database.yml
  • .github/workflows/firebaseai.yml
  • .github/workflows/firestore.yml
  • .github/workflows/functions.yml
  • .github/workflows/inappmessaging.yml
  • .github/workflows/installations.yml
  • .github/workflows/messaging.yml
  • .github/workflows/performance.yml
  • .github/workflows/storage.yml

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 reverts a previous revert, effectively re-applying a large set of modernization and cleanup changes across several quickstart examples. The key changes include the removal of legacy Objective-C and older Swift projects, a migration from Cocoapods to Swift Package Manager for dependency management, and a general cleanup of project, target, and scheme names for better consistency. Additionally, the codebase is updated with modern Swift features, such as using @main for the app entry point and @MainActor for UI-related code to ensure thread safety. A notable improvement is the replacement of a third-party reachability library with Apple's native Network framework in the Crashlytics example. Overall, these changes significantly improve the structure, maintainability, and modernity of the quickstart projects.