android 不尊重 trigger.io 的 tabs.openWithOptions 用于服务器端重定向

Question

我有一些基本的 trigger.io 代码来打开用于 oauth2 身份验证的模式对话框:

var url_auth = "http://10.0.0.70/oauth2/authorize";
var oauth_client_id = "123";
var oauth_redirect_uri = "http://done.com/oauth2/complete";

forge.tabs.openWithOptions({
    url: url_auth + "?response_type=token&client_id="+ oauth_client_id + "&redirect_url=" + oauth_redirect_uri,
    pattern: oauth_redirect_uri + "*",
    title: "Authorizing"
}, function(data) { ... });

当用户未通过身份验证时，服务器重定向到 http://10.0.0.70/users 以显示登录表单。

在 iOS6 模拟器中运行代码会产生正确的结果:

• 打开模态对话框
• 服务器重定向到登录表单，显示在对话框中
• 用户可以验证
• 服务器重定向到触发捕获并关闭对话框的 oauth_redirect_uri

当我在 Android 模拟器中运行时，初始页面已加载，但随后应用程序崩溃了。

• 我看到服务器上正在处理/oauth2/authorize url
• 我在调试对话框中看到的是“subView load http://10.0.0.70:3000/users”

有关错误的更多详细信息(日志中此后没有任何内容):

[DEBUG] Native call tabs.open with task.params: {"url":"http://10.0.0.70:3000/oauth2/authorize?response_type=token&client_id=123&redirect_url=http://www.diveboatbuddy.com/oauth2/complete","pattern":"^http://www.diveboatbuddy.com/oauth2/complete.*$","title":"Authorizing"}
[INFO] Displaying modal view.
[DEBUG] Returned: {"content":null,"callid":"0F7BA94D-08AD-439D-B44F-80BB22540CD4","status":"success"}
[DEBUG] Native call logging.log with task.params: {"message":"[FORGE] 'Successfully subscribed for push notifications'","level":20}
[INFO] [FORGE] 'Successfully subscribed for push notifications'
[DEBUG] Returned: {"content":null,"callid":"030EF36D-C17F-42E8-8F9E-0221A40153D1","status":"success"}
[INFO] subView load http://10.0.0.70:3000/users

看起来服务器已正确重定向，但 trigger.io 应用程序未呈现新的服务器页面。

问题的adb logcat输出:

D/Forge   (  394): Returned: {"content":null,"callid":"03F62CF7-8B33-425C-ABD5-2BA64565B789","status":"success"}
D/dalvikvm(  394): GC_EXTERNAL_ALLOC freed 349 objects / 24336 bytes in 41ms
I/Forge   (  394): subView load http://10.0.0.70:3000/users
D/AndroidRuntime(  394): Shutting down VM
W/dalvikvm(  394): threadid=1: thread exiting with uncaught exception (group=0x4001d800)
E/AndroidRuntime(  394): FATAL EXCEPTION: main
E/AndroidRuntime(  394): java.lang.NoSuchMethodError: android.webkit.WebView.removeJavascriptInterface
E/AndroidRuntime(  394):    at io.trigger.forge.android.modules.tabs.ModalView$2$3.shouldOverrideUrlLoading(ModalView.java:310)
E/AndroidRuntime(  394):    at android.webkit.CallbackProxy.uiOverrideUrlLoading(CallbackProxy.java:216)
E/AndroidRuntime(  394):    at android.webkit.CallbackProxy.handleMessage(CallbackProxy.java:323)
E/AndroidRuntime(  394):    at android.os.Handler.dispatchMessage(Handler.java:99)
E/AndroidRuntime(  394):    at android.os.Looper.loop(Looper.java:123)
E/AndroidRuntime(  394):    at  android.app.ActivityThread.main(ActivityThread.java:4627)
E/AndroidRuntime(  394):    at java.lang.reflect.Method.invokeNative(Native Method)
E/AndroidRuntime(  394):    at java.lang.reflect.Method.invoke(Method.java:521)
E/AndroidRuntime(  394):    at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:868)
E/AndroidRuntime(  394):    at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:626)
E/AndroidRuntime(  394):    at dalvik.system.NativeStart.main(Native Method)
W/ActivityManager(   59):   Force finishing activity io.trigger.forge1979a236289211e2bbe612313d31f141/io.trigger.forge.android.core.ForgeActivity
I/ARMAssembler(   59): generated scanline__00000077:03515104_00000000_00000000 [ 33 ipp] (47 ins) at [0x3446c0:0x34477c] in 5998000 ns
W/ActivityManager(   59): Activity pause timeout for HistoryRecord{43f928a8 io.trigger.forge1979a236289211e2bbe612313d31f141/io.trigger.forge.android.core.ForgeActivity}
I/Process (  394): Sending signal. PID: 394 SIG: 9
I/ActivityManager(   59): Process io.trigger.forge1979a236289211e2bbe612313d31f141 (pid 394) has died.
W/ActivityManager(   59): Scheduling restart of crashed service io.trigger.forge1979a236289211e2bbe612313d31f141/com.parse.PushService in 5000ms
I/WindowManager(   59): WIN DEATH: Window{44002988 io.trigger.forge1979a236289211e2bbe612313d31f141/io.trigger.forge.android.core.ForgeActivity paused=false}
I/ActivityManager(   59): Start proc io.trigger.forge1979a236289211e2bbe612313d31f141 for service io.trigger.forge1979a236289211e2bbe612313d31f141/com.parse.PushService: pid=422 uid=10036 gids={1015, 3003}

有没有人遇到过这个问题。是否有解决方法或错误？

Answer 1

这已在 Trigger.io 平台的 v1.4.34 中修复:http://docs.trigger.io/en/v1.4/release-notes.html#v1-4-34 .