update fluttertoast and connectivity_plus

[arifikhsan]

No description provided.

[gemini-code-assist]

Summary of Changes

Hello @arifikhsan, 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 primarily focuses on upgrading the fluttertoast and connectivity_plus packages to their latest major versions. To ensure the example applications build and run correctly with these updated dependencies, significant changes have been introduced to the iOS and macOS project configurations. These changes involve adding standard Podfiles and adjusting Xcode configuration files to properly integrate CocoaPods, thereby modernizing the build setup for the example projects.

Highlights

• Package Updates: The fluttertoast package has been updated from version ^8.2.12 to ^9.0.0, and the connectivity_plus package has been updated from ^6.1.5 to ^7.0.0.
• iOS Example Project Configuration: A new Podfile has been added to the example/ios directory, establishing CocoaPods dependency management for the iOS example project. Additionally, the Debug.xcconfig and Release.xcconfig files were modified to include the respective CocoaPods build configurations.
• macOS Example Project Configuration: A new Podfile has been added to the example/macos directory, setting up CocoaPods dependency management for the macOS example project. Similarly, the Flutter-Debug.xcconfig and Flutter-Release.xcconfig files were updated to include the CocoaPods build configurations.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

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 updates fluttertoast and connectivity_plus to new major versions and adds related iOS/macOS configuration. My main concern, which is critical, is that these dependency updates introduce breaking changes, but the necessary code migrations are missing. This will break the package. I've also left a few medium-severity suggestions to improve the iOS and macOS Podfile configurations for better maintainability and consistency.

[gemini-code-assist]

These dependency upgrades are major version bumps (fluttertoast from v8 to v9, connectivity_plus from v6 to v7), which introduce significant breaking changes. The pull request lacks the necessary code changes to accommodate these new versions. This will break the library. Please update the Dart code to align with the new APIs of these packages.

Breaking changes in connectivity_plus: ^7.0.0:

• Connectivity().checkConnectivity() now returns a List<ConnectivityResult>.
• onConnectivityChanged stream now emits a List<ConnectivityResult>.

Breaking changes in fluttertoast: ^9.0.0:

• toastLength now uses the Toast enum.
• gravity now uses the ToastGravity enum.
• backgroundColor and textColor are deprecated in favor of other styling methods.

[gemini-code-assist]

It is recommended to uncomment this line and set an explicit iOS deployment target. This improves build reproducibility and stability by not relying on a CocoaPods default version that could change over time. The suggested '13.0' is a reasonable choice, though you might want to align it with the minimum version your package supports.

platform :ios, '13.0'

[gemini-code-assist]

The error message contains an escaped double-quoted command \"flutter pub get\". For consistency with the iOS Podfile and for better readability, it's better to remove the quotes or use single quotes.

    raise "#{generated_xcode_build_settings_path} must exist. If you're running pod install manually, make sure flutter pub get is executed first"

[gemini-code-assist]

The error message contains an escaped double-quoted command \"flutter pub get\". For consistency with the iOS Podfile and for better readability, it's better to remove the quotes or use single quotes.

  raise "FLUTTER_ROOT not found in #{generated_xcode_build_settings_path}. Try deleting Flutter-Generated.xcconfig, then run flutter pub get"