at_contacts_flutter 1.0.2

at_contacts_flutter: ^1.0.2 copied to clipboard

10/10 points: Provide a valid pubspec.yaml

5/5 points: Provide a valid README.md

5/5 points: Provide a valid CHANGELOG.md

10/10 points: Use an OSI-approved license

Detected license: BSD-3-Clause.

0/10 points: 20% or more of the public API has dartdoc comments

Dependency resolution failed, unable to run dartdoc.

10/10 points: Package has an example

0/20 points: Platform support detection failed

0/50 points: code has no errors, warnings, lints, or formatting issues

• Running flutter pub outdated failed with the following output:

The current Dart SDK version is 3.4.3.
Because at_contacts_flutter depends on at_lookup ^1.0.0+1 which doesn't support null safety, version solving failed.

0/10 points: All of the package dependencies are supported in the latest version

• Could not run flutter pub outdated: flutter pub get failed:

OUT:
Resolving dependencies...
ERR:
The current Dart SDK version is 3.4.3.

Because at_contacts_flutter depends on at_lookup ^1.0.0+1 which doesn't support null safety, version solving failed.

The lower bound of "sdk: '>=2.7.0 <3.0.0'" must be 2.12.0 or higher to enable null safety.
For details, see https://dart.dev/null-safety


You can try the following suggestion to make the pubspec resolve:
* Try an upgrade of your constraints: flutter pub upgrade --major-versions

10/10 points: Package supports latest stable Dart and Flutter SDKs

0/20 points: Compatible with dependency constraint lower bounds

flutter pub downgrade failed with:

OUT:
Resolving dependencies...
ERR:
The current Dart SDK version is 3.4.3.

Because at_contacts_flutter depends on at_lookup ^1.0.0+1 which doesn't support null safety, version solving failed.

The lower bound of "sdk: '>=2.7.0 <3.0.0'" must be 2.12.0 or higher to enable null safety.
For details, see https://dart.dev/null-safety


You can try the following suggestion to make the pubspec resolve:
* Try an upgrade of your constraints: flutter pub upgrade --major-versions

Run flutter pub downgrade and then flutter analyze to reproduce the above problem.

You may run dart pub upgrade --tighten to update your dependency constraints, see dart.dev/go/downgrade-testing for details.