Comments (3)
OK I have prepared a new jar that contains the missing class. However the compiler emits an error because I'm defining a core class javax/security/auth/x500/X500PrivateCredential.class:
Ill-advised or mistaken usage of a core class (java.* or javax.*)
when not building a core library.
This is often due to inadvertently including a core library file
in your application's project, when using an IDE (such as
Eclipse). If you are sure you're not intentionally defining a
core class, then this is the most likely explanation of what's
going on.
However, you might actually be trying to define a class in a core
namespace, the source of which you may have taken, for example,
from a non-Android virtual machine project. This will most
assuredly not work. At a minimum, it jeopardizes the
compatibility of your app with future versions of the platform.
It is also often of questionable legality.
If you really intend to build a core library -- which is only
appropriate as part of creating a full virtual machine
distribution, as opposed to compiling an application -- then use
the "--core-library" option to suppress this error message.
If you go ahead and use "--core-library" but are in fact
building an application, then be forewarned that your application
will still fail to build or run, at some point. Please be
prepared for angry customers who find, for example, that your
application ceases to function once they upgrade their operating
system. You will be to blame for this problem.
If you are legitimately using some code that happens to be in a
core package, then the easiest safe alternative you have is to
repackage that code. That is, move the classes in question into
your own package namespace. This means that they will never be in
conflict with core system classes. JarJar is a tool that may help
you in this endeavor. If you find that you cannot do this, then
that is an indication that the path you are on will ultimately
lead to pain, suffering, grief, and lamentation.
from dexter.
OK I figured it out. java.util.jar.Manifest.java is behaving differently (Manifest-Version cf Signature-Version) on Android. ( See also the latest five commits with funny messages https://android.googlesource.com/platform/libcore/+log/master/luni/src/main/java/java/util/jar/Manifest.java). I see that you included the latest platform/libcore source in libdexter presumably for dex compiler. I think that version will work. Is it possible to refer to use this Manifest class in our code somehow?
from dexter.
Wow, that must have been terrible debugging...
Libcore is included but only the 'dex' subproject is being compiled and included in Dexter. So if I understand this correctly, the class in the framework is wrong and you want to replace with the newer version from AOSP? In that case, it should suffice to compile it from the libcore repo and include in the APK. We can try that tomorrow.
from dexter.
Related Issues (20)
- Invoke+TryEnd+MoveResult does not work
- Taint object assigned too late for external classes HOT 1
- InternalDataStructure handles inheritance wrong HOT 1
- Handling null HOT 2
- Taint interface method are too coarse HOT 1
- Type inference could be more precise for exceptions HOT 1
- MONITOR_EXIT instruction has slightly unusual throwing semantics HOT 1
- External static field taint not initialized
- How does FILL_ARRAY_DATA work? Is this a relevant piece of code? HOT 4
- Compiler constraint issue HOT 3
- CONST_STRING generates mutable Taint object
- Init done on a copy of THIS ref doesn't initialize the other copies
- APUT_OBJECT changed to APUT HOT 4
- FilledNewArray needs same TRY block treatment as Invoke
- Optimizer sometimes collapses simultaneously live registers HOT 2
- Simplify static field initialization
- Register colouring still producing invalid code HOT 7
- BinXml class name
- Taint object still created too late
- Taint object conversions during external calls
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from dexter.