Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

publish of shared_aws_api needed to use package http >= 1.0.0 #406

Open
cbatson opened this issue Jul 24, 2023 · 3 comments
Open

publish of shared_aws_api needed to use package http >= 1.0.0 #406

cbatson opened this issue Jul 24, 2023 · 3 comments

Comments

@cbatson
Copy link
Contributor

cbatson commented Jul 24, 2023

Using published shared_aws_api, package http versions 1 and higher cannot be used:

Because no versions of aws_dynamodb_api match >2.0.0 <3.0.0 and aws_dynamodb_api 2.0.0 depends on shared_aws_api ^2.0.0, aws_dynamodb_api ^2.0.0 requires shared_aws_api ^2.0.0.
And because shared_aws_api >=1.0.0 depends on http ^0.13.1, aws_dynamodb_api ^2.0.0 requires http ^0.13.1.
So, because XXX depends on both aws_dynamodb_api ^2.0.0 and http ^1.1.0, version solving failed.

The code to enable this was already added in #396 (here), so just a publish is needed.
@akriese
Copy link

akriese commented Aug 4, 2023

I need to update to http>=1.0.0, so this is also an issue for me!

@isoos
Copy link
Contributor

isoos commented Aug 4, 2023

Note: you may override the dependency in your pubspec.yaml:
https://dart.dev/tools/pub/dependencies#dependency-overrides

In this case it is safe to override http to 1.0.0 as there was no API change.

akriese added a commit to ActivityRadar/app that referenced this issue Aug 4, 2023
@akriese
chore: migrate to flutter_map v5.0.0
42bda0c 
this brings some dependency changes with it:
http needs to be updated to 1.1.0, but aws_s3_api uses an old version of
that. According to the discussion in
agilord/aws_client#406, this can be overridden
in the pubspec.yaml

Also, flutter_map_marker_cluster hasnt officially migrated to using
flutter_map v5 yet, so we need to manually use the git ref dee9902, like
explained here: lpongetti/flutter_map_marker_cluster#173

The migration itself only brings some changes in the implementation of
flutter_map_animations, which were quickly fixed :)
@cbatson
Copy link
Contributor Author

cbatson commented Aug 4, 2023 •
edited
Loading

@isoos Thanks for the workaround tip. It hadn't occurred to me to use a dependency override to move ahead in versions.

akriese added a commit to ActivityRadar/app that referenced this issue Aug 7, 2023
@akriese
chore: migrate to flutter_map v5.0.0
027e6ce 
this brings some dependency changes with it:
http needs to be updated to 1.1.0, but aws_s3_api uses an old version of
that. According to the discussion in
agilord/aws_client#406, this can be overridden
in the pubspec.yaml

Also, flutter_map_marker_cluster hasnt officially migrated to using
flutter_map v5 yet, so we need to manually use the git ref dee9902, like
explained here: lpongetti/flutter_map_marker_cluster#173

The migration itself only brings some changes in the implementation of
flutter_map_animations, which were quickly fixed :)
@stevenmetzger stevenmetzger mentioned this issue Jan 4, 2024
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@isoos @cbatson @akriese