Error inflating class

[erva]

Hello!
I have found issue on Android 4.4.2 (Samsung Galaxy Note 2) when I tried to run sample

java.lang.RuntimeException: Unable to start activity ComponentInfo{MyActivity}: android.view.InflateException: Binary XML file line #98: Error inflating class com.farbod.labelledspinner.LabelledSpinner
...
Caused by: java.lang.NoSuchMethodError: android.widget.LinearLayout.<init>
at com.farbod.labelledspinner.LabelledSpinner.<init>(LabelledSpinner.java:117)
at com.farbod.labelledspinner.LabelledSpinner.<init>(LabelledSpinner.java:112)
at com.farbod.labelledspinner.LabelledSpinner.<init>(LabelledSpinner.java:108)

[farbodsz]

Hmm, thanks for letting me know @ervinmartirosyan .

I'll look into this issue during the next couple of days.

[ionull]

Same on Nexus 3 with Android 4.3

[legalimpurity]

Same on Samsung S Duos, Crashing the app, gotta remove this Widget, too bad

[farbodsz]

@legalimpurity Sorry for the delay in trying to fix the issue - I have been super-busy lately with exams, and also I have no idea why the sample is crashing in this way.

For now, you can use earlier versions of the LabelledSpinner library until the issue is fixed.

[farbodsz]

I have posted a Stack Overflow question here, for those who are interested.

I'm not sure why the error is occuring, to be honest, but if anyone does know, please let me know (by replying here or answering the Stack Overflow question).

Thanks.

[legalimpurity]

Hi,

I sat down to fix this, and i have realized that now that there is no issue. When i download your sample project and comment the line

// compile 'com.farbod.labelledspinner:labelledspinner:1.1.5'

and compile the project from your Git manually, it works perfectly.

compile project(':labelledspinner')  // Used when testing latest features of library module

Most probably, you have not pushed the latest changes to your Maven Repository

[farbodsz]

I forgot to reference this issue from the commit, but commit f2b76cb fixed this issue (with all missing updates pushed to Bintray). Thanks @legalimpurity for noticing the issue.

[ionull]

Maybe you can also update the document such as README

[farbodsz]

@ionull What a quick reply! :)

I've just updated the changelog and readme (29cc1e1).

[ionull]

@FarbodSalamat-Zadeh well done! thanks!!