Closed bjoernQ closed 5 years ago
@ligi thanks for letting me know - I created a new issue since the original one was closed. Will have to look into that. Any chance you could provide a simple standalone example (maybe based on the example in this repo) showing this behavior?
I tried to reproduce it without success - maybe this was a temporary problem?
If the problem persists please reopen with steps to reproduce (e.g. by changing the example to match your configuration)
@bjoernQ thanks for looking into it. I had trouble creating a isolated repo to reproduce the problem - seems there have to be multiple things to play together to create the problem (jetifier, gradle witness, unmock) Also it seems to be bound to (state) on one PC of mine - just tried on another machine and also do not see it. UPDATE: could solve the problem by deleting (or better moving - if it helps I still have this directory) the .gradle directory in my home
@ligi that's strange - only thing I could imagine is that the Gradle cache in ~/.gradle was somehow corrupted? I remember I had a similar issue once and experienced strange errors for my local builds
@bjoernQ I have just experienced this problem with 0.7.3 after updating to Kotlin 1.3.1:
Originally posted by @ligi in https://github.com/bjoernQ/unmock-plugin/issues/31#issuecomment-486773208