2016-11-02 50 views
1

爲了在Windows下調試我的Python Kivy應用程序,我下載了ARC焊接工具並將其安裝在Windows下的Chrome瀏覽器下。安裝工作正常,以及加載我的.apk文件,該文件是使用Buildozer工具在Boot2Docker,Docker和Ubuntu下構建的。 Chrome應用程式顯示Kivy標誌,然後告訴「加載」後跟一個「:-(」圖標。如何在ARC焊機下調試Kivy應用程序

我怎麼能啓動一個日誌文件,以顯示導致Kivy應用程序崩潰的運行時錯誤?

下面我發現在鍍鉻的控制檯顯示消息:

plugin not ready$ 
jscomp.scope.Plugin.postMessage @ plugin.js:336$ 
jscomp.scope.Plugin.onWindowStateChanged_ @ plugin.js:1579target.(anonymous function) @ 
extensions::SafeBuiltins:19EventImpl.dispatchToListener @ extensions::event_bindings:388target.(anonymous function) @ 
extensions::SafeBuiltins:19publicClassPrototype.(anonymous function) @ 
extensions::utils:151EventImpl.dispatch_ @ extensions::event_bindings:372EventImpl.dispatch @ 
extensions::event_bindings:394target.(anonymous function) @ 
extensions::SafeBuiltins:19publicClassPrototype.(anonymous function) @ 
extensions::utils:151dispatchEventIfExists @ extensions::app.window:335updateAppWindowProperties @ 
extensions::app.window:356 

背景檢查:

Delaying update install logic for 107 seconds 
filesystem_background.js:253 ARC HTML5 FS: Request FileSystem: 35ms 
main.js:354 ARC Window Popup: 97.5ms 
main.js:388 ARC appWindow Init: 0.35ms 
crash_reporter.js:298 prod: ARC 
crash_reporter.js:298 arc_app_name: CFEduPlayer 
crash_reporter.js:298 ptime: NaN 
crash_reporter.js:298 crash_time: Wed Nov 02 2016 13:54:07 GMT-0200 (Horário brasileiro de verão) 
crash_reporter.js:298 ver: 54.5021.629.0 
crash_reporter.js:298 arc_build_tag: arc-runtime-54.5021.629.0 
crash_reporter.js:298 message: plugin crash without minidump 
crash_reporter.js:298 chrome_version: 54.0.2840.87 
crash_reporter.js:298 app_id: cnlfghclafgbigiolhlbghjnenbaippl 
crash_reporter.js:298 app_version: 0.1 
crash_reporter.js:298 app_package_name: org.test.cfeduplay 
crash_reporter.js:298 runtime_name: App Runtime for Chrome (Beta) 
crash_reporter.js:298 runtime_update_url: https://clients2.google.com/service/update2/crx 
crash_reporter.js:298 arch: x86-32 
crash_reporter.js:298 nacl_arch: x86-64 
crash_reporter.js:298 os: win 
crash_reporter.js:298 target_arch: nacl_x86_64 
crash_reporter.js:298 width: 960 
crash_reporter.js:298 height: 632 
crash_reporter.js:298 is_minimized: false 
crash_reporter.js:298 is_maximized: false 
crash_reporter.js:298 is_fullscreen: false 
crash_reporter.js:298 runtime_updated_while_running: null 
crash_reporter.js:298 sig: exit() called 
crash_reporter.js:161 Crash reporting not enabled in Chrome. Please enable it. 
crash_reporter.js:318 FINISHED REPORTING CRASH 

應用檢查:

ARC JS Init: 222ms 
plugin.js:654 Compositor is enabled 
filesystem.js:97 File system is initialized. 
plugin.js:336 Plugin not ready$jscomp.scope.Plugin.postMessage @ plugin.js:336 
filesystem.js:227 ARC HTML5 FS: prefetchExtraFileMetadata_: 1.32e+03ms 
plugin.js:800 3.661s + 0.078s = 3.740s (+0.0M virt, +0.0M res): App instance started 

plugin.js:784 ARC Plugin Load: 3.45e+03ms 
filesystem.js:286 Sending 147 file system cache entries to the plugin 
plugin.js:800 3.661s + 0.080s = 3.742s (+0.0M virt, +0.0M res): Started renderer thread 

plugin.js:800 3.661s + 1.634s = 5.296s (+0.0M virt, +0.0M res): Starting System 

plugin.js:800 3.661s + 3.393s = 7.055s (+0.0M virt, +0.0M res): Android runtime initialized 

plugin.js:800 3.661s + 3.453s = 7.115s (+0.0M virt, +0.0M res): Started SurfaceFlinger 

plugin.js:800 3.661s + 3.668s = 7.330s (+0.0M virt, +0.0M res): Started native services 

plugin.js:800 3.661s + 5.141s = 8.802s (+0.0M virt, +0.0M res): Package dexopted 

plugin.js:800 3.661s + 6.548s = 10.209s (+0.0M virt, +0.0M res): System server started 

gen_index.min.html:1 Is the 'geolocation' permission appropriate? See http://developer.chrome.com/apps/declare_permissions.html. 
plugin.js:800 3.661s + 6.736s = 10.397s (+0.0M virt, +0.0M res): Activity onResume {org.test.cfeduplay/org.renpy.android.PythonActivity} (build 54.5021.629.0) 

plugin.js:800 3.661s + 8.528s = 12.189s (+0.0M virt, +0.0M res): Exiting 

gen_index.min.html:1 NativeClient: NaCl module crashed 
plugin.js:978 plugin crashed$jscomp.scope.Plugin.showCrash_ @ plugin.js:978 

問候,

指導有關Kivy調試程序上的電弧焊機是值得歡迎的。

回答

0

在最後一個出現「:-(」圖標的錯誤屏幕上,右鍵單擊鼠標並選擇「檢查」或「檢查背景」。我已經找到了錯誤的根本原因,這是錯誤的先決條件添加ffmpeg模塊和CODEC到buildozer環境我已經在Ubuntu 14系統映像中安裝了ffmpeg包,並使用以下語句將它添加到了buildozer.spec需求中:requirements = kivy,ffmpeg。 .apk開始播放媒體,無論是在ARC Welder瀏覽器平臺下,還是在Android 6下。滿意的解決方案和ARC Welder正在完美運作!

相關問題