You may want to try invoking dx.jar directly on your extension's libraries to see if it outputs any errors. In App Inventor we use multidex and so in theory it should split up the code into more classes.dex files to accommodate larger libraries, but it could be an issue with how you compiled the library sources.
then you can see whatever errors dex generates for your extension.
If that doesn't yield any errors, consider running App Inventor locally using the dev server along with a local build server. You should be able to look at the raw console output to see if there are any other issues reported.
C:\Users\GOD\appinventor-sources\appinventor\lib\android\tools>java - jar dx.jar --dex C:\Users\GOD\appinventor-sources\appinventor\lib\nexcube\nexcube.jar
Unrecognized option: -
Error: Could not create the Java Virtual Machine.
Error: A fatal exception has occurred. Program will exit.
C:\Users\GOD\appinventor-sources\appinventor\lib\android\tools>java -jar dx.jar --dex C:\Users\GOD\appinventor-sources\appinventor\lib\nexcube\nexcube.jar
Picked up _JAVA_OPTIONS: -Xmx1024m
PARSE ERROR:
class name (cs/min2phase/CoordCube) does not match path (CoordCube.class)
...while parsing CoordCube.class
1 error; aborting
it says the error for the first java code file (i have 4 code file error coressponds to 1 of it) the file name is CoordCube the code file package name was
package cs.min2phase;
and the structure of the code will be
package cs.min2phase;
class CoordCube {
//code here i din't post code if required i will PM
}