ANTLR Tool version mismatch with Room build error [150106190]

Fixed

Bug

Status Update

No update yet.

Description

he...@gmail.com

created issue #1

Feb 24, 2020 03:33PM

I am using classpath 'com.android.tools.build:gradle:3.5.3', Room 2.2.3, Dagger 2.26 and AS 3.5.3. When I am building my project I get this error

ANTLR Tool version 4.5.3 used for code generation does not match the current runtime version 4.7.1ANTLR Runtime version 4.5.3 used for parser compilation does not match the current runtime version 4.7.1ANTLR Tool version 4.5.3 used for code generation does not match the current runtime version 4.7.1ANTLR Runtime version 4.5.3 used for parser compilation does not match the current runtime version 4.7.1error: cannot generate view binders java.lang.StackOverflowError

And then a list of calls that caused the java.lang.StackOverflowError
at android.databinding.tool.expr.Expr.resolveListeners(Expr.java:209)
at android.databinding.tool.expr.Expr.resolveListeners(Expr.java:211)
at android.databinding.tool.expr.Expr.resolveListeners(Expr.java:211)
at android.databinding.tool.expr.Expr.resolveListeners(Expr.java:211)
at android.databinding.tool.expr.Expr.resolveListeners(Expr.java:211)
at android.databinding.tool.expr.Expr.resolveListeners(Expr.java:211)
at android.databinding.tool.expr.Expr.resolveListeners(Expr.java:211)
at android.databinding.tool.expr.Expr.resolveListeners(Expr.java:211) (etc)

It seems that it is known issue with data binding and room mismatch from what I read online but the solution of forcing a particular version of antlr4 doesn't work for me.

When forcing a version of antlr4 like so

configurations.all() {
resolutionStrategy.force "org.antlr:antlr4-runtime:4.5.3"
resolutionStrategy.force "org.antlr:antlr4-tool:4.5.3"
}
I can;'t compile Room with error Caused by: java.lang.ClassNotFoundException: org.antlr.v4.runtime.CharStreams

when forcing it to 4.7.1 it does nothing. Same error with version mismatch. Downgrading Room does nothing.

Comments

vi...@google.com <vi...@google.com> Feb 26, 2020 04:58AM

Assigned to vi...@google.com.

vi...@google.com <vi...@google.com> Feb 26, 2020 07:19AM

Assigned to yb...@google.com.

yb...@google.com <yb...@google.com> #2Feb 27, 2020 06:19AM

Is there any updates? This is a big problem!

he...@gmail.com <he...@gmail.com> #3Feb 27, 2020 05:01PM

Hi there - could you provide more context on the issue & a sample project to reproduce? Database locked exceptions are quite difficult to pinpoint without a repro project. Thanks!

yb...@google.com <yb...@google.com> #4Feb 28, 2020 02:57AM

Hi. It is reproduceable on some users by using this code:

suspend fun <R> MyDatabase.workaroundWithTransaction(block: suspend TransactionScope<R>.() -> R) {
    useWriterConnection {
        it.immediateTransaction(block)
    }

    // TODO: Temporally fix https://issuetracker.google.com/issues/340606803#comment2
    // Manually triggers invalidation
    invalidationTracker.refreshAsync()
}

he...@gmail.com <he...@gmail.com> #5Feb 28, 2020 03:01PM

Maybe it is about this? https://android-review.googlesource.com/c/platform/frameworks/support/+/3114928

I am not sure.

ap...@google.com <ap...@google.com> #6Mar 23, 2020 07:54PM

Hi. Please merge the pull request. This is big problem!

ap...@google.com <ap...@google.com> #7Apr 6, 2020 11:15PM

Hi. Is there any updates on this problem?

ap...@google.com <ap...@google.com> #8Apr 6, 2020 11:15PM

Hi, I updated my version to alpha12 but still have these crashes. Please release a fix asap.

yb...@google.com <yb...@google.com> Apr 7, 2020 02:20AM

Marked as fixed.

it...@gmail.com <it...@gmail.com> #9Apr 7, 2020 01:59PM

Will there be fixes released this Wednesday?

yb...@google.com <yb...@google.com> #10Apr 7, 2020 03:42PM

Hey, there is no release on Wednesday (holiday in the USA)

We haven't found the root cause of this exception, it happens when SQLite can't commit the transaction because some other connection has a lock, we need more information, a sample project that reproduces the issue preferably, or more details on how the database is being used (is it from multiple process? is there heavy concurrency?).

You can also increase the time SQLite will wait before it error with 'database locked' by executing PRAGMA busy_timeout = <time in ms>, the current default is 3000