Steven Arzt

FlowDroid always performs intra-app analysis unless you combine it with tools such as APKCombiner. This has nothing to do with the selection of sources and sinks. The sources and sinks...

FlowDroid can run on apps as well as normal Java code. The data flow tracker has different modules: - ``soot-infoflow`` contains the Java-based data flow analysis - ``soot-infoflow-android`` extends the...

Your ``ISourceSinkManager`` always returns ``null``. So whenever FlowDroid asks whether a given statement is a source or a sink, you always reply with "no". That's why FlowDroid tells you that...

You're currently marking every statement in the whole code as a sink. This may lead to funny results, e.g., when a method is a source and a sink at the...

There is no assignment from ``packageName`` to ``identity.packageName`` in this method. I would have to look into the implementation of ``fromBinderUnsafe`` to see whether there is an assignment somewhere in...

I think we don't have a summary for ``stream()`` yet. Maybe you can extend the StubDroid summaries and open a merge request for your changes? You can find examples in...

Soot, on which FlowDroid is based, cannot write out Java source files as far as I know. However, you can write out Java class files. You can use FlowDroid`s ``SetupApplication``...

That's indeed a strange problem. Can you check whether the dummy main method is correct (and just large), or whether the generator is faulty and just generates a lot of...

FlowDroid supports JAR and class files. Have a look at the JUnit test cases inside ``soot-infoflow``, they are all based on pure Java.

The test case is actually broken. Note that ```Bundle.get()``` is implemented as follows: ``` return new String[] { key }; ``` The return value is then cast to type ```A[]```:...