Defold extension-facebook 2.6 crashed on login

#1

Example application from repo crashed on android when login button pressed.

To Reproduce (REQUIRED)
Steps to reproduce the behavior:

  1. Clone git repository for the latest 2.6 version.
  2. Compile and Build test application.
  3. Click on LoginFB button.

Expected behaviour (REQUIRED)
A clear and concise description of what you expected to happen.

  1. Logged in to Facebook and get user email

Defold version (REQUIRED):

  • Version [e.g. 1.2.173]
    FB extension: 2.6.0

Platforms (REQUIRED):

  • Platforms: [Android]
  • Device: [Honor 7C]

Logs (OPTIONAL):
Here is the log from android:
10-01 19:47:45.628 716 716 E BufferQueueProducer: [] Can not get hwsched service
10-01 19:47:45.684 14953 14953 E AndroidRuntime: FATAL EXCEPTION: main
10-01 19:47:45.684 14953 14953 E AndroidRuntime: Process: com.defold.facebook, PID: 14953
10-01 19:47:45.684 14953 14953 E AndroidRuntime: java.lang.RuntimeException: Unable to start activity ComponentInfo{com.defold.facebook/com.facebook.FacebookActivity}: android.content.res.Resources$NotFoundException: Resource ID #0x7f03001e
10-01 19:47:45.684 14953 14953 E AndroidRuntime: at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:3303)
10-01 19:47:45.684 14953 14953 E AndroidRuntime: at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:3411)
10-01 19:47:45.684 14953 14953 E AndroidRuntime: at android.app.ActivityThread.-wrap12(Unknown Source:0)
10-01 19:47:45.684 14953 14953 E AndroidRuntime: at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1994)
10-01 19:47:45.684 14953 14953 E AndroidRuntime: at android.os.Handler.dispatchMessage(Handler.java:108)
10-01 19:47:45.684 14953 14953 E AndroidRuntime: at android.os.Looper.loop(Looper.java:166)
10-01 19:47:45.684 14953 14953 E AndroidRuntime: at android.app.ActivityThread.main(ActivityThread.java:7529)
10-01 19:47:45.684 14953 14953 E AndroidRuntime: at java.lang.reflect.Method.invoke(Native Method)
10-01 19:47:45.684 14953 14953 E AndroidRuntime: at com.android.internal.os.Zygote$MethodAndArgsCaller.run(Zygote.java:245)
10-01 19:47:45.684 14953 14953 E AndroidRuntime: at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:921)
10-01 19:47:45.684 14953 14953 E AndroidRuntime: Caused by: android.content.res.Resources$NotFoundException: Resource ID #0x7f03001e
10-01 19:47:45.684 14953 14953 E AndroidRuntime: at android.content.res.ResourcesImpl.getValue(ResourcesImpl.java:279)
10-01 19:47:45.684 14953 14953 E AndroidRuntime: at android.content.res.Resources.loadXmlResourceParser(Resources.java:2310)
10-01 19:47:45.684 14953 14953 E AndroidRuntime: at android.content.res.Resources.getLayout(Resources.java:1293)
10-01 19:47:45.684 14953 14953 E AndroidRuntime: at android.view.LayoutInflater.inflate(LayoutInflater.java:421)
10-01 19:47:45.684 14953 14953 E AndroidRuntime: at android.view.LayoutInflater.inflate(LayoutInflater.java:374)
10-01 19:47:45.684 14953 14953 E AndroidRuntime: at com.android.internal.policy.PhoneWindow.setContentView(PhoneWindow.java:477)
10-01 19:47:45.684 14953 14953 E AndroidRuntime: at com.android.internal.policy.HwPhoneWindow.setContentView(HwPhoneWindow.java:321)
10-01 19:47:45.684 14953 14953 E AndroidRuntime: at android.app.Activity.setContentView(Activity.java:2850)
10-01 19:47:45.684 14953 14953 E AndroidRuntime: at com.facebook.FacebookActivity.onCreate(FacebookActivity.java:78)
10-01 19:47:45.684 14953 14953 E AndroidRuntime: at android.app.Activity.performCreate(Activity.java:7383)
10-01 19:47:45.684 14953 14953 E AndroidRuntime: at android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1218)
10-01 19:47:45.684 14953 14953 E AndroidRuntime: at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:3256)
10-01 19:47:45.684 14953 14953 E AndroidRuntime: … 9 more
10-01 19:47:45.684 859 3489 E iMonitor: FaultDetect: DUMPTOOL_PRINTF return.

0 Likes

#2

This is solved with the latest Defold 1.2.174 beta and build server. It will be released as a stable release hopefully late next week.

1 Like