-
Notifications
You must be signed in to change notification settings - Fork 159
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
Android dependency resolution issue #346
Comments
If accepting the change you suggested in #347 then there will be an issue with apps dependent on the For now I don't know any quick fix on this. The problem will ultimately resolved once the minimum version is updated to API 26 and the SDK start use |
Do you have an ETA for that? |
@Rexios80 unfortunately no |
Since you are in the process of making a new major version, would it make sense to include that change? If so, can I create a PR for that? Also, how do I open the project in Android Studio? I can't get the sdk folder to show up in the folder tree, and no dependencies resolve in those files. It seems like the sdk files should be in a separate module but they aren't. |
Duplicate class android.support.v4.app.INotificationSideChannel found in modules core-1.9.0-runtime (androidx.core:core:1.9.0) and support-compat-27.1.1-runtime (com.android.support:support-compat:27.1.1) Go to the documentation to learn how to Fix dependency resolution errors. |
That doesn't look like the same issue |
Platform on which you observed the bug:
Device on which you observed the bug:
Describe the bug
Another of our dependencies depends on https://github.com/dlew/joda-time-android which is incompatible with joda-time. Accoring to dlew/joda-time-android#184 (comment) you shouldn't use the raw joda-time dependency on Android, so maybe we should replace it?
How to Reproduce
Include a dependency that depends on joda-time-android
Expected behavior
No dependency resolution errors
Screenshots and logs
If applicable, add screenshots or logs to help explain your problem.
The text was updated successfully, but these errors were encountered: