libs/armeabi/libcom_googlecode_android_scripting_Exec.so read problem about android-python27 HOT 9 OPEN

Have you tried re-extracting 
libs/armeabi/libcom_googlecode_android_scripting_Exec.so from 
script_for_android_template.zip, then refresh and clean the project in Eclipse?

I had this same exact issue with PerlAPK and that is how I solved it.

I solved the problem by remove it from the buildpath:
libcom_googlecode_android_scripting_Exec.so 

Looks an Eclipse(>= 3.7?) bug, try this: Java Compler->Building->Build path 
problems - set Incomplete build path: to Warning

To solve this, don't remove the 'libcom_googlecode_android_scripting_Exec.so ' 
from the build, it's needed. If you did remove it, then copy it back into your 
workspace: 'PythonAPK\libs\armeabi' and run 'Project->Clean', right click on 
the PythonAPK project and select 'Close Project', and then double click to open 
it again. Check that it shows up in the Package Explorer window under 
'PythonAPK\libs\armeabi'. Alternatively, you can just delete the project and 
import it back in again.

Next, as Anthony wrote, right click on the project and select 'Build 
Path->Configure Build Path', then under 'Java Compiler->Building' make sure 
'Enable Project Specific Settings' is checked. Under 'Build Path Problems' 
uncheck 'Abort build when build path errors occur' or change 'Incomplete build 
path' from Error to Warning. Click Apply and OK. 

The red 'X' icon appearing on the project in the Project Explorer window should 
change to a yellow '!' icon for warning instead of error. If it didn't, close 
and reopen the project (or restart Eclipse). On Windows, if you have a 
thumbnail file inside a build directory, you'll see a red X over that directory 
which will also prevent the build from occurring - just right click and delete 
the thumbnail file.

[deleted comment]

Since this seems to be a bug with Eclipse, this issue is considered "Done", 
however, I will leave the status set to "New" so that it's more easily visible. 
I'll also add this info to the Wiki tutorial.

Same problem without sloved. I'm using Eclipse IDE for Java Developers, Vession 
1.4.2

I can confirm this is an Eclipse bug, following instructions above would cure.

I had the same problem. For me, unchecking 'Abort build when build path errors 
occur' didn't work. Changing 'Incomplete build path' from Error to Warning 
worked. Can launch the app now.