-
Notifications
You must be signed in to change notification settings - Fork 1.9k
Main dispatcher missing on version 1.2.1 (android gradle plugin 3.5.0-beta02) #1213
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
Comments
Seems to work with agp version 3.5.0-beta01 as well. |
May I ask to report the bug to AGP then? |
I just reported it myself to bring awareness early to the Android Gradle plugin team: https://issuetracker.google.com/issues/133495912 |
Thanks, @LouisCAD! |
Could you provide a more detailed stacktrace to help us debug this issue, or even better, a sample project? Please post it at https://issuetracker.google.com/issues/133495912. |
Sure, will do a sample project and post it 👍 |
If anyone else stumbles across this, it seems to be that AGP 3.5.0 isn't including the |
@rabidaudio Are you seeing issues with coroutines and R8 after upgrading to AGP 3.5.0? Or are you just concerned that It is not necessarily an issue that @wojtek-kalicinski and @JakeWharton have been working on getting the coroutines library and R8 to work seamlessly together, and they might have more precise information in which versions work well together. (copied this to http://issuetracker.google.com/133495912 as well) |
FYI this doesn't seem to be related to any work I've been doing as my changes landed in AGP 3.6 canary 7 and coroutines 1.3.0. |
When upgrading our project to coroutines version 1.2.1 (from 1.2.0), we get a
Here are the relevant parts of our build.gradle:
root:
one of many library modules in our project module:
(all looking basically the same, there is no import of another version somewhere)
Gradle version: 5.4.1
Android gradle plugin: 3.5.0-beta02
The same configuration works using the older agp version 3.4.0 or the older coroutines version 1.2.0
The text was updated successfully, but these errors were encountered: