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

Version >=2 incompatible with integration_test #7

Open
jameshmread opened this issue May 8, 2021 · 2 comments
Open

Version >=2 incompatible with integration_test #7

jameshmread opened this issue May 8, 2021 · 2 comments

Comments

@jameshmread
Copy link

I have to use a fuzzy version (it reverts back to non-null safe) of this package as it conflicts with integration_test

Running "flutter pub get" in <my-repo>...               
Because every version of integration_test from sdk depends on crypto 2.1.5 and analyzer >=1.0.0 depends on crypto ^3.0.0, integration_test from sdk is incompatible with analyzer >=1.0.0.

And because network_image_mock >=2.0.0 depends on mockito ^5.0.0 which depends on analyzer ^1.0.0, integration_test from sdk is incompatible with network_image_mock >=2.0.0.
So, because <my-repo> depends on both network_image_mock ^2.0.0 and integration_test any from sdk, version solving failed.
pub get failed (1; So, because <my-repo> depends on both network_image_mock ^2.0.0 and integration_test any from sdk, version solving failed.)
exit code 1

Looks like its the Mockito dependency causing the issue, since it depends on a strict 1.0.0.

Flutter doctor

$ flutter doctor -v
[√] Flutter (Channel stable, 2.0.4, on Microsoft Windows [Version 10.0.19042.928], locale en-GB)
    • Flutter version 2.0.4 at D:\Flutter.io\flutter
    • Framework revision b1395592de (5 weeks ago), 2021-04-01 14:25:01 -0700
    • Engine revision 2dce47073a
    • Dart version 2.12.2

[√] Android toolchain - develop for Android devices (Android SDK version 30.0.2)
    • Android SDK at C:\Users\<>\AppData\Local\Android\sdk
    • Platform android-30, build-tools 30.0.2
    • Java binary at: C:\Program Files\Android\Android Studio\jre\bin\java
    • Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b01)
    • All Android licenses accepted.

[√] Chrome - develop for the web
    • Chrome at C:\Program Files (x86)\Google\Chrome\Application\chrome.exe

[√] Android Studio (version 4.0)
    • Android Studio at C:\Program Files\Android\Android Studio
    • Flutter plugin can be installed from:
       https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
       https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b01)

[√] VS Code, 64-bit edition (version 1.55.2)
    • VS Code at C:\Program Files\Microsoft VS Code
    • Flutter extension version 3.17.0

[√] Connected device (3 available)
    • Pixel 2 (mobile) • XX • android-arm64  • Android 10 (API 29)
    • Chrome (web)     • chrome       • web-javascript • Google Chrome 90.0.4430.85
    • Edge (web)       • edge         • web-javascript • Microsoft Edge 90.0.818.49

• No issues found!
@campovski
Copy link
Member

Thanks for filing the issue. I will try to look into it today.

Maybe moving on to support null-safety was a bit of a premature thing since a lot is happening in Flutter world these days. Nevertheless, there has to be something we can do.

@campovski
Copy link
Member

I have updated the dependencies and hopefully version 2.0.1 should now work. In case the same issue persists, you will need to stick with the not null safe version until other dependencies bump theirs. Hopefully this version conflict madness will soon cease to exist.

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

No branches or pull requests

2 participants