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

[SEVERE] mockito:mockBuilder - The getter 'isDartCoreObject' was called on null #349

Closed
gmcdowell opened this issue Mar 8, 2021 · 4 comments
Labels
type-bug Incorrect behavior (everything from a crash to more subtle misbehavior)

Comments

@gmcdowell
Copy link

gmcdowell commented Mar 8, 2021

overview

  • unable to run flutter packages pub run build_runner build --delete-conflicting-outputs
  • isolated to use of loggy package [I have migrated this pkg to null-safety as part of trouble-shoot efforts - see pubspec.yaml]

how to replicate

  • i have put together a demo repo for ease of replication
  • once cloned & pub get, try running cmd flutter packages pub run build_runner build --delete-conflicting-outputs --verbose - output should point to package:mockito/src/builder.dart line737:26
  • from there i'm at a bit of a loss, so any guidance appreciated.

flutter doctor
`
Doctor summary (to see all details, run flutter doctor -v):
[✓] Flutter (Channel dev, 2.1.0-10.0.pre, on macOS 11.2.2 20D80 darwin-x64, locale en-NZ)
[✓] Android toolchain - develop for Android devices (Android SDK version 30.0.3)
[✓] Xcode - develop for iOS and macOS
[✓] Chrome - develop for the web
[✓] Android Studio (version 4.1)
[✓] IntelliJ IDEA Ultimate Edition (version 2020.3.2)
[✓] VS Code (version 1.53.2)
[✓] Connected device (2 available)

• No issues found!
`

@gmcdowell
Copy link
Author

reciprocal link to loggy repo issue to keep all in loop.

@srawlins
Copy link
Member

srawlins commented Mar 8, 2021

Thank so much for the repro! I'll investigate this in the next 24 hours.

@srawlins srawlins added the type-bug Incorrect behavior (everything from a crash to more subtle misbehavior) label Mar 8, 2021
@srawlins
Copy link
Member

srawlins commented Mar 8, 2021

I can reproduce this. It has to do with the superclass mixing in a mixin. I've mailed a fix internally. Hope to release a fix to pub soon.

@srawlins
Copy link
Member

Fixed in 5.0.1

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type-bug Incorrect behavior (everything from a crash to more subtle misbehavior)
Projects
None yet
Development

No branches or pull requests

2 participants