This repository has been archived by the owner on Jan 5, 2023. It is now read-only.
forked from CrossPT/flutter_plugin_pdf_viewer
-
Notifications
You must be signed in to change notification settings - Fork 147
version solving failed of path_provider #27
Comments
I hope they update soon |
1 similar comment
I hope they update soon |
Me too |
Is there any update on this? Do we have any workaround for this issue as of now ? I am completely blocked on this. |
On Mon, 12 Apr 2021 at 15:08, Devendra Singh ***@***.***> wrote:
Is there any update on this?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#27 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AGIXHM53W6FX7N75O4WYGV3TILPCLANCNFSM4ZRUGJUA>
.
Hello Devendra,
Regarding pdf_viewer plugin,
For my use case, I decided to use a plugin named native_pdf_viewer
Its dependencies uses latest versions
You may give it a try
https://pub.dev/packages/native_pdf_view
|
We are facing the same issue: Because shared_preferences >=2.0.0 depends on shared_preferences_windows ^2.0.0 which depends on path_provider_platform_interface ^2.0.0, shared_preferences >=2.0.0 requires path_provider_platform_interface ^2.0.0.
(1) So, because path_provider >=1.6.4 <2.0.0-nullsafety depends on path_provider_platform_interface ^1.0.1, shared_preferences >=2.0.0 is incompatible with path_provider >=1.6.4 <2.0.0-nullsafety.
Because advance_pdf_viewer >=1.2.0 <1.2.1 depends on path_provider ^1.6.11 and advance_pdf_viewer >=1.1.0 <1.2.0 depends on flutter_advanced_networkimage ^0.7.0, advance_pdf_viewer >=1.1.0 <1.2.1 requires path_provider ^1.6.11 or flutter_advanced_networkimage ^0.7.0.
And because advance_pdf_viewer <1.1.0 depends on flutter_advanced_networkimage ^0.5.0 and advance_pdf_viewer >=1.2.1 depends on path_provider ^1.6.24, every version of advance_pdf_viewer requires path_provider ^1.6.11 or flutter_advanced_networkimage ^0.5.0 or ^0.7.0.
And because shared_preferences >=2.0.0 is incompatible with path_provider >=1.6.4 <2.0.0-nullsafety (1), if shared_preferences >=2.0.0 and advance_pdf_viewer any then flutter_advanced_networkimage ^0.5.0 or ^0.7.0.
And because flutter_advanced_networkimage >=0.3.9 depends on http ^0.12.0, if shared_preferences >=2.0.0 and advance_pdf_viewer any then http ^0.12.0.
And because http >=0.11.3+17 <0.13.0-nullsafety.0 depends on http_parser >=0.0.1 <4.0.0 and firebase_auth_web >=1.0.0 depends on http_parser ^4.0.0, one of shared_preferences >=2.0.0 or advance_pdf_viewer any or firebase_auth_web >=1.0.0 must be false.
And because deltaebook depends on firebase_auth ^1.1.0 which depends on firebase_auth_web ^1.0.6, shared_preferences >=2.0.0 is incompatible with advance_pdf_viewer.
So, because deltaebook depends on both shared_preferences ^2.0.5 and advance_pdf_viewer any, version solving failed. |
A great guy placed a pull request but I don't know why it hasn't been merged.
|
Thanks, I'll check it out.
…On Wed, Apr 14, 2021 at 1:14 AM Daniel ***@***.***> wrote:
A great guy placed a merge but I don't know why it hasn't been merged.
Just add this:
git:
url: https://github.com/maxzod/pdf_viewer.git
ref: master```
and in dev dependencies bump flutter_launcher_icons to 0.9.0
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#27 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AGIXHM53X77RKO2RH45LBHTTIS65ZANCNFSM4ZRUGJUA>
.
|
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Hi can you please update path_provider latest version.
"Because no versions of google_fonts match >2.0.0 <3.0.0 and google_fonts 2.0.0 depends on path_provider ^2.0.0, google_fonts ^2.0.0 requires path_provider ^2.0.0.
And because advance_pdf_viewer >=1.2.1 depends on path_provider ^1.6.24, google_fonts ^2.0.0 is incompatible with advance_pdf_viewer >=1.2.1.
So, because depends on both google_fonts ^2.0.0 and advance_pdf_viewer ^1.2.1, version solving failed"
The text was updated successfully, but these errors were encountered: