Fix chrome debugging on android
Summary: Java loadApplicationScript changed, but the C++ code in the debug ProxyExecutor which called it did not. This fixes the fbjni method lookup. fixes #7659 Reviewed By: AaaChiuuu Differential Revision: D3331472 fbshipit-source-id: 33312dccc3c7687f51742e42f9e0397f9c925e76
This commit is contained in:
parent
81e4b4202a
commit
f7c4ed8926
|
@ -41,14 +41,15 @@ ProxyExecutor::~ProxyExecutor() {
|
|||
}
|
||||
|
||||
void ProxyExecutor::loadApplicationScript(
|
||||
const std::string& script,
|
||||
const std::string&,
|
||||
const std::string& sourceURL) {
|
||||
static auto loadApplicationScript =
|
||||
jni::findClassStatic(EXECUTOR_BASECLASS)->getMethod<void(jstring, jstring)>("loadApplicationScript");
|
||||
jni::findClassStatic(EXECUTOR_BASECLASS)->getMethod<void(jstring)>("loadApplicationScript");
|
||||
|
||||
// The proxy ignores the script data passed in.
|
||||
|
||||
loadApplicationScript(
|
||||
m_executor.get(),
|
||||
jni::make_jstring(script).get(),
|
||||
jni::make_jstring(sourceURL).get());
|
||||
}
|
||||
|
||||
|
|
Loading…
Reference in New Issue