question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Theme used in the library conflicts with others

See original GitHub issue

If you use this library you get an error that the app theme is already defined (in my own project). To fix this, you can for example add tools:replace="android:icon, android:label, android:theme, android:name" in your application tag in the manifest. However, this causes instability with other libraries such as com.daimajia.slider:library:1.1.5.

Giving the error

Caused by: android.view.InflateException: Binary XML file line #83: Error inflating class com.daimajia.slider.library.SliderLayout

Is there a way to make them all work happily together?

Issue Analytics

  • State:closed
  • Created 8 years ago
  • Comments:5 (1 by maintainers)

github_iconTop GitHub Comments

1reaction
avluiscommented, Apr 3, 2016

@passy

Just wanted to update this.

The issue is simple: If your app and the library have anything that is incompatible by the merge tool, then you’ll get this error.

The merge tool is complaining about the theme attribute value (@style/AppTheme) but when I quickly scan the library, I don’t see it - so the error it throws is not helpful. What is helpful is the suggestion.

It literally means just that - to override the manifest merge (which should fix the issue), add 'tools:replace=“android:theme” to your <application> tag. That should let you compile. If you still cannot compile, make sure you don’t have any tools:ignore statements, that seems to break it - I’m referring to com.gu.option, even maven complains about it:

Not Found: /artifact/com.gu/option/1.3

0reactions
geeteshkcommented, Nov 23, 2016

Gentlemen I have found a workaround for those facing this issue. It seems to only show up when android:theme is set for the <application> tag. Remove it and add it to each of your activities separately. Worked fine for me.

Read more comments on GitHub >

github_iconTop Results From Across the Web

Conflict with a theme based on composer using a more recent ...
We're using Timber, a theme that allows integration of Twig and other libraries which are installed via Composer. Installing PublishPress plugins causes a ......
Read more >
How to Fix WordPress Plugin Conflicts - Visualmodo
If the problem is still there, it is either due to the theme conflicting with a plugin or installed plugins conflicting with each...
Read more >
Known Third Party Plugin & Theme Conflicts - Event Espresso
Other third party plugins have been known to cause issues with Event Espresso, due to varying reasons, so we have listed all known...
Read more >
Conflict with theme that use Bootstrap library.
Description. The conflict can be, if the theme is using Bootstrap library and version of Bootstrap is different then version in Booking Calendar....
Read more >
AJAX and Jquery Conflicts - Tribulant Documentation
It means that your theme is manually inserting the files on your website, in this case, if one of your plugins wants to...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found