Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Allow flutter_fgbg 0.8.0

Open Beginner friendly
#212 0 comments 2 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
72/100
Issue type
Feature
Clarity
Clearly specified
Activity status
Quiet
Tech stack
dart
Domain
mobile

Research direction

Find the flutter_fgbg dependency declaration and inspect the repository's existing dependency or compatibility checks. Test package resolution with the current minimum Dart SDK and with Dart 3.8+; done means newer projects resolve flutter_fgbg 0.8.0 while older supported SDKs resolve a compatible 0.7.x release.

Written by the indexing model from the issue text.

Description

I’m targeting Flutter 3.44.9 with Dart 3.12.2 and Swift Package Manager enabled.
I understand that changing the dependency directly to:
flutter_fgbg: ^0.8.0
would require Dart 3.8+ and drop support for older Flutter versions.

Could the constraint instead be widened to support both releases?
flutter_fgbg: ">=0.7.1 <0.9.0"

Pub should then resolve:

  • flutter_fgbg 0.8.0 on Dart 3.8+, enabling SPM support.
  • A compatible 0.7.x release on older Dart SDKs, preserving existing Flutter support.

Verification

I tested the Segment SPM branch at commit 3b99cafd with:

dependency_overrides:
flutter_fgbg: 0.8.0

On Flutter 3.44.9:

  • flutter_fgbg disappeared from the SPM warning.
  • Both segment_analytics and flutter_fgbg were integrated through SwiftPM.

Requested outcome

Please consider widening the dependency range and testing resolution against both the current minimum Dart SDK and Dart 3.8+. This should allow newer applications to use SPM without requiring an immediate minimum Flutter version increase for all users.

Dominant language
Dart
Stars
33
Forks
57
PR merge metrics
No merged PRs in 30d

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from segmentio/analytics_flutter

All issues in segmentio/analytics_flutter

Similar issues

More Dart issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.