Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Example APK not working with ARChon V1.0 on Chrome Stable 37.0.2062.120 m (64-bit) on Windows 8.1 64 bits OS #26

Closed
st6315 opened this issue Sep 21, 2014 · 3 comments

Comments

@st6315
Copy link

st6315 commented Sep 21, 2014

I test it on my 64 bits Windows 8.1 with Chrome Stable 37.0.2062.120 m (64-bit) using the example 2048 APK, it just shows up as an Android logo and nothing happens.

Below is the console message I got:

ARC onInstalled HTML5 FS init: 631.000ms main.js:370
ChildPlugin jsInstaller:0:dexopt(so_executable) Run: 2005.000ms main.js:370
timeout to spawn ChildPlugin process: dexopt(so_executable), dexopt --preopt /vendor/chromium/crx/com.uberspot.a2048.android.apk $auto v=r,o=v,m=y,u=n main.js:370
retry to spawn with timeout 4sec. main.js:370
ChildPlugin jsInstaller:0:dexopt(so_executable) Run: 1286.000ms main.js:370
Dexopt plugin terminated main.js:370
ARC Window Popup: 66.000ms main.js:370
the child process has been loaded: so_executable/umareporter main.js:370
ChildPlugin backgroundpage:0:umareporter(so_executable) Run: 340.000ms main.js:370
0x7318EB09 is not a valid instance ID. main.js:370
Received a crash main.js:370
prod: ARC main.js:370
arc_app_name: com.uberspot.a2048 main.js:370
ptime: 60937 main.js:370
crash_time: Sun Sep 21 2014 19:54:48 GMT+0800 main.js:370
ver: 38.4410.120.25 main.js:370
arc_build_tag: arc-runtime-38.4410.120.25 main.js:370
message: heartbeat ping timeout main.js:370
chrome_version: 37.0.2062.120 main.js:370
app_id: kdjbiekcidfncdnaocdfbeflnpomjabn main.js:370
app_version: 1337 main.js:370
width: 360 main.js:370
height: 672 main.js:370
is_minimized: false main.js:370
is_maximized: false main.js:370
is_fullscreen: false main.js:370
Attempting to report crash... main.js:370
FINISHED REPORTING CRASH

Originally I think the line "0x7318EB09 is not a valid instance ID" is the main error in this case, but since @Flytomars- points out this is normal, so I don't know what is the problem...

@PlasmaPower
Copy link
Contributor

The 0x7318EB09 is not a valid instance ID is perfectly normal.

@st6315
Copy link
Author

st6315 commented Sep 21, 2014

@Flytomars- OK, I know that now :)

@vladikoff
Copy link
Owner

Closing in favour of #17

Repository owner locked and limited conversation to collaborators Sep 22, 2014
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants