Android Auto Instrumentor throws NameSpace Error
Trying this on a prospects Android app, the app is for Active.
I get the following error when trying to auto instrument.
ERROR: 'Namespace for prefix 'android' has not been declared.'
SEVERE: caa-jApkRecomp(1): Error saving the manifest file.
Throwable occurred: javax.xml.transform.TransformerException: java.lang.RuntimeException: Namespace for prefix 'android'
has not been declared.
at com.sun.org.apache.xalan.internal.xsltc.trax.TransformerImpl.transform(TransformerImpl.java:755)
at com.sun.org.apache.xalan.internal.xsltc.trax.TransformerImpl.transform(TransformerImpl.java:359)
at com.cpwr.apm.android.a.b.a(Unknown Source)
at com.cpwr.apm.android.a.b.a(Unknown Source)
at com.cpwr.apm.android.a.b.o(Unknown Source)
at com.cpwr.apm.android.adk.AdkInstrumentor.a(Unknown Source)
at com.cpwr.apm.android.adk.AdkInstrumentor.main(Unknown Source)
Caused by: java.lang.RuntimeException: Namespace for prefix 'android' has not been declared.
at com.sun.org.apache.xml.internal.serializer.SerializerBase.getNamespaceURI(SerializerBase.java:914)
at com.sun.org.apache.xml.internal.serializer.SerializerBase.addAttribute(SerializerBase.java:431)
at com.sun.org.apache.xalan.internal.xsltc.trax.DOM2TO.parse(DOM2TO.java:201)
at com.sun.org.apache.xalan.internal.xsltc.trax.DOM2TO.parse(DOM2TO.java:230)
at com.sun.org.apache.xalan.internal.xsltc.trax.DOM2TO.parse(DOM2TO.java:136)
at com.sun.org.apache.xalan.internal.xsltc.trax.DOM2TO.parse(DOM2TO.java:98)
at com.sun.org.apache.xalan.internal.xsltc.trax.TransformerImpl.transformIdentity(TransformerImpl.java:702)
at com.sun.org.apache.xalan.internal.xsltc.trax.TransformerImpl.transform(TransformerImpl.java:746)
... 6 more
---------
We've added an improvement to make it possible to instrument this type of applications in 6.0, a candidate release of which should be available soon in the near future.
Application developers can use manual instrumentation (because they have the source code) for now but at some point in the near future we'd like to understand the scenario better and see if we can support it. The developers can avoid manual instrumentation by switching to the 'android' namespace by changing one or a few XML files.
Thanks for the quick response. In this case it would require manual configuration of the Mobile ADK, got it.
It appears that the developers of this app use a user defined namespace for "http://schemas.android.com/apk/res/android" instead of the required 'android' namespace, hence the reported error.
At this time we don't have a solution or workaround for this scenario.
For some reason we can't fully decompile the AndroidManifest.xml file. We are looking into it ... will let you know as soon as we have some news.
Here is the link to it in the google play store, https://play.google.com/store/apps/details?id=com.active.fnd.mobile
the apk file is com.active.fnd.mobile.apk
Thanks,
Can you please indicate the exact app name (APK file) so we can take a look? What version of Android Auto Instrumentation are you using?
