Crosswalk Integration Beta in Ionic CLI (v1.3.2)

Does remote debugging on Google Chrome work with ‘Crosswalked’ apps in Android versions below version 4.4? I thought I read about that somewhere but my app is not showing up in Chrome’s inspect devices window when connected via usb. My device runs Android version 4.1.2

Yes remote debugging through Chrome will work.
Since Crosswalk is a Chromium Browser, we can get Chrome V36 in Android 4.1-4.3.

Thanks for re-confirming that, it is currently not working for me however. What I’m I missing?

Hopefully this will help.

2 Likes

Thanks a bunch @mhartington. It works on restarting my system, can’t say what went wrong initially! Lol

You need not “wrap anything”. Crosswalk 10.X will work with cordova 4.x .

@jbavari1 Is there are cli build flag for this?
Ex : cordova build android -x86 or something like this

I updated to 1.3.0-beta1, and the ionic command is not available at the commandline anymore.

I am on Mac OS X Yosemite 10.10.1.

Ok, crosswalk is awesome. I made my own build of Ionic’s front-page HN sample app. It was horrible on my 4.1.2 device! I ported that same app to a Crosswalk build and it is performing really well.
Now here is the issue, apk size (37.4mb) and eventual app size (81mb) on the device are deal breakers! Would separating the arm and x86 builds really help to make things better? What architecture does most device come with? Please I would need someone to shed more light on this. Thanks

Without Crosswalk:

With Crosswalk:

I had the same error. My console stated that the minsdkversion (in my config.xml) was lower than some android manifest elsewhere in the project. Apparently they all have to be the same minimal version.

It seems that Crosswalk is downloaded again every time it is added to a project. Since the download is quite large, a possible improvement would be to do this only once if the crosswalk version hasn’t changed.

I’ve been using Crosswalk by copying manually the project. Really hope this goes smoothly - it will be a massive improvement.

  • Update -
    Well, it didn’t went smoothly. When I build after installing Crosswalk (using $ ionic browser add crosswalk ), it complains with The provided path [XYZ]/android is not an Android project..
    API was already 19, all the rest is up to date. Have to check with better eyes what’s the matter.

I have the same problem as well

Thanks for the feedback.

I’ll be researching and confirming that the two separate builds will be created. This should help keep the APK size down.

1 Like

@bale - I’ll be getting caching in 1.3.1, hang tight!

2 Likes

I’m using the 1.3.0 build. When I try to run in the Android emulator targeting 4.0.3, I consistently get a segfault. I know the SDK requires 19 or higher, but does that mean we should only expect it to run correctly on 4.4 or higher? It appears to work on 4.1, so I’m guessing no…

Note that the FATAL error seems to be related to OpenGL; I’ve tried this with both the “host GPU” emulation checked and unchecked.

F/chromium(  612): [FATAL:gl_surface_android.cc(58)] Check failed: kGLImplementationNone != GetGLImplementation() (0 vs. 0)
F/libc    (  612): Fatal signal 11 (SIGSEGV) at 0xdeadbaad (code=1)
I/Process (   77): Sending signal. PID: 612 SIG: 3
I/dalvikvm(  612): threadid=3: reacting to signal 3
I/dalvikvm(  612): Wrote stack traces to '/data/anr/traces.txt'
I/DEBUG   (   34): *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
I/DEBUG   (   34): Build fingerprint: 'generic/sdk/generic:4.0.4/MR1/302030:eng/test-keys'
I/DEBUG   (   34): pid: 612, tid: 642  >>> com.raccoonfink.cruisemonkey <<<
I/DEBUG   (   34): signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr deadbaad
I/DEBUG   (   34):  r0 deadbaad  r1 00000001  r2 40000000  r3 00000000
I/DEBUG   (   34):  r4 00000000  r5 00000027  r6 4db1a4f4  r7 4db1a928
I/DEBUG   (   34):  r8 4db1a950  r9 400535c8  10 00000000  fp 00000001
I/DEBUG   (   34):  ip ffffffff  sp 4db1a488  lr 4001f161  pc 4001b8c0  cpsr 60000030
I/DEBUG   (   34):  d0  4000000000000000  d1  3ff0000043a04000
I/DEBUG   (   34):  d2  000000003f000000  d3  000000003f000000
I/DEBUG   (   34):  d4  0000000000000000  d5  3fe999999999999a
I/DEBUG   (   34):  d6  43c0000000000000  d7  000000013f800000
I/DEBUG   (   34):  d8  0000000000000000  d9  0000000000000000
I/DEBUG   (   34):  d10 0000000000000000  d11 0000000000000000
I/DEBUG   (   34):  d12 0000000000000000  d13 0000000000000000
I/DEBUG   (   34):  d14 0000000000000000  d15 0000000000000000
I/DEBUG   (   34):  scr 60000012
I/DEBUG   (   34):
I/DEBUG   (   34):          #00  pc 000178c0  /system/lib/libc.so
I/DEBUG   (   34):          #01  lr 4001f161  /system/lib/libc.so
I/DEBUG   (   34):
I/DEBUG   (   34): code around pc:
I/DEBUG   (   34): 4001b8a0 4623b15c 2c006824 e026d1fb b12368db  \.#F$h.,..&..h#.
I/DEBUG   (   34): 4001b8b0 21014a17 6011447a 48124798 24002527  .J.!zD.`.G.H'%.$
I/DEBUG   (   34): 4001b8c0 f7f47005 2106ee50 eeecf7f5 460aa901  .p..P..!.......F
I/DEBUG   (   34): 4001b8d0 f04f2006 94015380 94029303 eaa8f7f5  . O..S..........
I/DEBUG   (   34): 4001b8e0 4622a905 f7f52002 f7f4eab2 2106ee3c  .."F. ......<..!
I/DEBUG   (   34):
I/DEBUG   (   34): code around lr:
I/DEBUG   (   34): 4001f140 41f0e92d 46804c0c 447c2600 68a56824  -..A.L.F.&|D$h.h
I/DEBUG   (   34): 4001f150 e0076867 300cf9b5 dd022b00 47c04628  gh.....0.+..(F.G
I/DEBUG   (   34): 4001f160 35544306 37fff117 6824d5f4 d1ee2c00  .CT5...7..$h.,..
I/DEBUG   (   34): 4001f170 e8bd4630 bf0081f0 0002839a 41f0e92d  0F..........-..A
I/DEBUG   (   34): 4001f180 fb01b086 9004f602 461f4815 4615460c  .........H.F.F.F
I/DEBUG   (   34): 
I/DEBUG   (   34): memory map around addr deadbaad:
I/DEBUG   (   34): be9cf000-be9e4000 [stack]
I/DEBUG   (   34): (no map for address)
I/DEBUG   (   34): (no map above)
I/DEBUG   (   34): 
I/DEBUG   (   34): stack:
I/DEBUG   (   34):     4db1a448  00004000  
I/DEBUG   (   34):     4db1a44c  00000000  
I/DEBUG   (   34):     4db1a450  0009e190  [heap]
I/DEBUG   (   34):     4db1a454  400476b0  /system/lib/libc.so

Another bug: if you have enabled the crosswalk browser, and do a ionic platform remove android followed by ionic platform android it tries installing cordova 3.6.4 still:

Failed to install 'org.apache.cordova.engine.crosswalk':CordovaError: Plugin doesn't support this project's cordova-android version. cordova-android: 3.6.4, failed version requirement: >=4.0.0-dev
    at checkEngines (/usr/local/lib/node_modules/cordova/node_modules/cordova-lib/src/plugman/install.js:116:29)
    at _fulfilled (/usr/local/lib/node_modules/cordova/node_modules/q/q.js:787:54)
    at self.promiseDispatch.done (/usr/local/lib/node_modules/cordova/node_modules/q/q.js:816:30)
    at Promise.promise.promiseDispatch (/usr/local/lib/node_modules/cordova/node_modules/q/q.js:749:13)
    at /usr/local/lib/node_modules/cordova/node_modules/q/q.js:557:44
    at flush (/usr/local/lib/node_modules/cordova/node_modules/q/q.js:108:17)
    at process._tickCallback (node.js:442:13)
Plugin doesn't support this project's cordova-android version. cordova-android: 3.6.4, failed version requirement: >=4.0.0-dev
1 Like

I got this error with my both mac. I already installed android version higher than 19.1.0. How can i get through of it?

FAILURE: Build failed with an exception.

* Where:
Script '/Users/cihadhoruzoglu/Desktop/IonicCrosswalk/platforms/android/cordova.gradle' line: 59

* What went wrong:
A problem occurred evaluating script.
> No installed build tools found. Please install the Android build tools version 19.1.0 or higher.

* Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get     more log output.

Please see the Minimum Android version in the first post.

Minimum Android SDK Version Needed - 19
Make sure you have the build tools for Android API level 19.
To install them:

  • Run android from the command line
$ android
# this will bring up the Android SDK Manager up. 
  • Select Android SDK Build Tools for API level 19, and install.
2 Likes

no it requires Minimum Android SDK Version Needed - 19

1 Like