topic Paul, in Software Archive

Intel XDK Android Crosswalk app crashes on Facebook Connect plugin login function invoke

Joshua_R_ — Fri, 18 Sep 2015 21:45:55 GMT

I have been working with Intel XDK and Facebook Connect plugin for a few months now with no issues until last night when I compiled an Android Crosswalk version that built successfully, but crashed as soon as you invoke the Facebook login function. After several attempts to remove and re-add the plugin and recompile, the issue still resides between myself and two other developers. The strange thing is previous builds still had no issues while the newer ones crashed on FB login attempt. Error message returned is:

"Unfortunately, AppName has stopped."

Here is a link to the FB Connect GitHub repo:

https://github.com/Wizcorp/phonegap-facebook-plugin

Here is a list of things we tried with no success:

Uninstall and re-install FB Connect plugin.
Uninstall Intel XDK, restart machine, and reinstall XDK.
Created a separate project with only the FB Connect plugin installed and a link to invoke the login function.
Changed application name, package name, and versions.
Changed CLI version, currently working with 5.1.1. Tried 4.1.2 as well.
Installed plugin locally and Intel XDK option in Included Plugins section.

Other settings:

Android Crosswalk embedded v11
Min. Android API: 14
Max. Android API: 23
CLI Version 5.1.1
Install Location: auto

Other things to note:

It still compiles and runs fine in iOS.
It still compiles and runs fine when setup in a PhoneGap environment.
Building in Intel XDK with the regular Android version returns error saying that the FB Connect plugin could not be installed.

Here is a build log from Google:

java.lang.NoClassDefFoundError: Failed resolution of: Lcom/facebook/android/R$layout;
at com.facebook.LoginActivity.onCreate(LoginActivity.java:57)
at android.app.Activity.performCreate(Activity.java:6289)
at android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1119)
at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2665)
at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:2777)
at android.app.ActivityThread.access$900(ActivityThread.java:179)
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1462)
at android.os.Handler.dispatchMessage(Handler.java:102)
at android.os.Looper.loop(Looper.java:145)
at android.app.ActivityThread.main(ActivityThread.java:5972)
at java.lang.reflect.Method.invoke(Native Method)
at java.lang.reflect.Method.invoke(Method.java:372)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:1399)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1194)
Caused by: java.lang.ClassNotFoundException: Didn't find class "com.facebook.android.R$layout" on path: DexPathList[[zip file "/data/app/com.package.name-1/base.apk"],nativeLibraryDirectories=[/data/app/com.package.name-1/lib/arm, /vendor/lib, /system/lib]]
at dalvik.system.BaseDexClassLoader.findClass(BaseDexClassLoader.java:56)
at java.lang.ClassLoader.loadClass(ClassLoader.java:511)
at java.lang.ClassLoader.loadClass(ClassLoader.java:469)
... 14 more
Suppressed: java.lang.ClassNotFoundException: com.facebook.android.R$layout
at java.lang.Class.classForName(Native Method)
at java.lang.BootClassLoader.findClass(ClassLoader.java:781)
at java.lang.BootClassLoader.loadClass(ClassLoader.java:841)
at java.lang.ClassLoader.loadClass(ClassLoader.java:504)
... 15 more
Caused by: java.lang.NoClassDefFoundError: Class not found using the boot class loader; no stack available

Haven't received a response

Joshua_R_ — Sun, 20 Sep 2015 16:54:21 GMT

Haven't received a response yet, but I'm willing to bet it's an issue somewhere on their build server.

After updating xdk - same

Mathias_J_ — Wed, 23 Sep 2015 15:37:57 GMT

After updating xdk - same problem here.

Did someone find a solution?

Well, I am having general

Barry_Johnson — Wed, 23 Sep 2015 16:53:43 GMT

Well, I am having general problems with the new version and some other plugins, but my main goal this week was to integrate the facebook plugin you referenced here, so it looks like the week will be a total washout. Good times. Maybe best use of my time will be setting up an alternative build process and moving on. I would sincerely miss the excellent on-device debugging, but with some of the issues lately I feel like the XDK is becoming just one more thing to wrangle, rather than a tool in service of higher net productivity. :-(

Haven't tried since last week

Joshua_R_ — Wed, 23 Sep 2015 16:57:37 GMT

Haven't tried since last week, but it appears many others are having the same issue. Switched back to a PhoneGap environment in a few minutes without issues.

Same problem here.

Theo_v_ — Thu, 24 Sep 2015 12:21:17 GMT

Same problem here.
No use for Crosswalk if I can't use the facebook connect plugin....

Seems to be fixed with

Theo_v_ — Thu, 24 Sep 2015 12:58:11 GMT

Seems to be fixed with Facebook Connect plugin version 0.11.0 and Cordova CLI Version 5.1.1
:)

There is an issue with the

PaulF_IntelCorp — Fri, 25 Sep 2015 00:08:12 GMT

There is an issue with the Crosswalk 7, 10, 11, 12 and 14 builds that we may have fixed. Probably will go live tomorrow. In the meantime, use the CLI 5.1.1 option and build with Crosswalk 15 or use the Crosswalk shared mode option, those two versions are not affected by this problem (I am speculating that the problem being fixed affects the Facebook plugin, but Theo's last post provides some affirmation that I may be correct).

I am having the same problem

Andrea_C_ — Fri, 25 Sep 2015 13:12:00 GMT

I am having the same problem too, this is the crash log:

java.lang.NoClassDefFoundError: com.facebook.android.R$layout
	at com.facebook.LoginActivity.onCreate(LoginActivity.java:57)
	at android.app.Activity.performCreate(Activity.java:5231)
	at android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1087)
	at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2169)
	at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:2271)
	at android.app.ActivityThread.access$800(ActivityThread.java:144)
	at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1205)
	at android.os.Handler.dispatchMessage(Handler.java:102)
	at android.os.Looper.loop(Looper.java:136)
	at android.app.ActivityThread.main(ActivityThread.java:5146)
	at java.lang.reflect.Method.invokeNative(Native Method)
	at java.lang.reflect.Method.invoke(Method.java:515)
	at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:732)
	at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:566)
	at dalvik.system.NativeStart.main(Native Method)

Andrea -- do you see this

PaulF_IntelCorp — Fri, 25 Sep 2015 17:28:41 GMT

Andrea -- do you see this crash if you build the app against the shared mode or using CW15 in the CLI 5.1.1 build option?

This is The crash report seen

Andrea_C_ — Fri, 25 Sep 2015 19:02:20 GMT

This is The crash report seen in The play store using cw7. It's a serious issue for us.

I cannot at the moment

Andrea_C_ — Fri, 25 Sep 2015 19:04:40 GMT

I cannot at the moment upgrade to CLI 5.1.1 as git plugins are broken using The latest version of xdk.

Andrea, are your project

PaulF_IntelCorp — Fri, 25 Sep 2015 22:52:28 GMT

Andrea, are your project files located on a different drive than where you installed the XDK? In other words, is the XDK installed on C: and are your project files installed on D: ? If so, that is the problem behind that git pull bug. We have a fix in process (it is a bug in the underlying Cordova plugin code). In the meantime, if this is the case for you move your project directory to the same drive as the XDK install directory and the git pulls should work so you can try 5.1.1.

An alternative is to clone the git repo plugins you need locally (you can use the ZIP download option if you don't have git installed) onto the same drive as that which holds the XDK and then do a local import from those copies on your local drive.

Paul,

Andrea_C_ — Sat, 26 Sep 2015 07:04:00 GMT

Paul,

I decided to turn back to XDK-EA that worked better than the latest XDK, but the problem I mentioned happens with XDk-EA.

2 Weeks ago this problem with XDk-EA did not happen. I think something strange happened in the build system.

@Andrea -- are you still

PaulF_IntelCorp — Mon, 05 Oct 2015 17:14:00 GMT

@Andrea -- are you still experiencing build failures with the Facebook Connect plugin on CLI 5.1.1? Your last note indicated that you needed to use the additions.xml file to build with CLI 5.1.1, but that you could use the plugin manager when building for CLI 4.1.2. Is this still the case?

One of my colleagues put together a simple test app that performs a Facebook login using that plugin and was able to cover the full matrix of builds with success. Also, Barry found an odd problem associated with copy/paste of hidden characters into the plugin parameter fields (this is an odd problem, but could be something you're running into, here's a link to an explanation https://software.intel.com/en-us/forums/intel-xdk/topic/594985).

Hey @Paul, thanks for the

ILoza — Sun, 29 Nov 2015 19:58:53 GMT

Hey @Paul, thanks for the link, I had the problem with the extra characters when are hidden from view, because I have been copy/paste when I did the plugin installation,

Thanks a lot Paul ;)