[TIMOB-16551] Android: Third party Java library in a module fails to compile in App

GitHub Issue	n/a
Type	Bug
Priority	Low
Status	Open
Resolution	Unresolved
Affected Version/s	Release 3.1.3
Fix Version/s	n/a
Components	Android
Labels	supportTeam
Reporter	Marco Cota
Assignee	Ashraf Abu
Created	2014-03-04T23:46:43.000+0000
Updated	2016-06-30T04:35:05.000+0000

Description

Attachments

File	Date	Size
mfoundry.zip	2014-03-24T17:53:52.000+0000	3027497
moduleTestApp.zip	2014-03-04T23:46:43.000+0000	1359563

Comments

Ingo Muschenetz 2014-03-05

It is complaining about com.yodlee and a "Modern Compiler" Is it possible that in 3.2.0 we now compile with the latest Android SDK vs API level 10 (as we do in 3.1.3)? You can manually specify this in the tiapp.xml for earlier SDK version. See TIMOB-13983 for more information.
Marco Cota 2014-03-11

[~ingo] we have tried to manually specify the SDK as recommended without any success and the app keeps logging the error message.
Ingo Muschenetz 2014-03-11

[~mcota] Can you paste in how you specified this?

Marco Cota 2014-03-11

I have tried using different API levels (10, 15, 17 and 19) with SDK 3.1.3 and we keep receiving the error log

   <android xmlns:android="http://schemas.android.com/apk/res/android">
       <tool-api-level>17</tool-api-level>
       <manifest android:installLocation="preferExternal">
           <uses-sdk android:minSdkVersion="10"/>
       </manifest>
   </android>

Setting the same API levels on SDK 3.2.0 launches the app without any error log

   <android xmlns:android="http://schemas.android.com/apk/res/android">
       	<uses-sdk android:minSdkVersion="10" android:targetSdkVersion="10" android:maxSdkVersion="19"/>
   </android>

JSON Source