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.

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

Support web ^1.0.0 #982

Closed
RoarGronmo opened this issue Aug 14, 2024 · 7 comments · Fixed by #981 or #1002
Closed

Support web ^1.0.0 #982

RoarGronmo opened this issue Aug 14, 2024 · 7 comments · Fixed by #981 or #1002

Comments

@RoarGronmo
Copy link

Many libraries are going for web ^1.0.0 and we are now stuck because of this problem where we are trying to upgrade web dependency from web ^0.5.1 to web ^1.0.0:

PS C:\FlutterProjects\mWork> flutter pub get
Resolving dependencies... (3.9s)
Because no versions of location match >7.0.0 <8.0.0 and location 7.0.0 depends on location_web ^5.0.3, location ^7.0.0 requires location_web ^5.0.3.
Because location_web 5.0.3 depends on web ^0.5.1 and no versions of location_web match >5.0.3 <6.0.0, location_web ^5.0.3 requires web ^0.5.1.
Thus, location ^7.0.0 requires web ^0.5.1.
So, because mwork depends on both location ^7.0.0 and web ^1.0.0, version solving failed.


You can try the following suggestion to make the pubspec resolve:
* Consider downgrading your constraint on web: flutter pub add web:^0.5.1
PS C:\FlutterProjects\mWork> 

Could you please make an effort to make location and location_web compatible with web ^1.0.0 ?

@mulderpf
Copy link

I second this request. This is currently holding up some upgrades I need to do.

@RoarGronmo
Copy link
Author

@Lyokone The fact that location_web 5.0.3 is still dependent on web 0.5.1 renders this PR not to sort out the problem that it isn't compatible with web ^1.0.0

...so I am sorry to say that problem still persists at the moment.

@sergiomeneses
Copy link

@Lyokone The fact that location_web 5.0.3 is still dependent on web 0.5.1 renders this PR not to sort out the problem that it isn't compatible with web ^1.0.0

...so I am sorry to say that problem still persists at the moment.

Confirm this, re open the issue please

@sergiomeneses
Copy link

sergiomeneses commented Sep 29, 2024

Even the fix is wrong (see #981)

@mulderpf
Copy link

The fix didn't resolve the issue and I am still getting the same error.

@hugofpaiva
Copy link

@Lyokone If possible, please check this!

@danielmessi13
Copy link

Any updates?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
5 participants