Android SDK crashing on React Native app when using react-native-picker | Community
Skip to main content
Answered

Android SDK crashing on React Native app when using react-native-picker


Hi,

We upgraded the Intercom SDK on react-native to 5.1.1, however we found a very strange crash. On a screen we use https://github.com/react-native-picker/picker and when the picker is opened on Android the app will crash. We found that the Intercom upgrade from 4.0.1 to 5.1.1 was the culprit. I presume it’s something to do with the underlying Android SDK which was updated. Below is the stack trace from Sentry

 

java.lang.ClassNotFoundException: androidx.appcompat.widget.e0$a
    at androidx.appcompat.widget.e0.setSelector(DropDownListView.java:1)
    at android.widget.AbsListView.<init>(AbsListView.java:899)
    at android.widget.ListView.<init>(ListView.java:231)
    at android.widget.ListView.<init>(ListView.java:227)
    at androidx.appcompat.widget.e0.<init>(DropDownListView.java:1)
    at androidx.appcompat.widget.i0.s
    at androidx.appcompat.widget.i0.q(ListPopupWindow.java:4)
    at androidx.appcompat.widget.i0.a(ListPopupWindow.java:1)
    at androidx.appcompat.widget.w$e.l(AppCompatSpinner.java:4)
    at androidx.appcompat.widget.w.b
    at androidx.appcompat.widget.w.performClick(AppCompatSpinner.java:3)
    at com.reactnativecommunity.picker.h.performClick(ReactPicker.java:4)
    at android.view.View.performClickInternal(View.java:7418)
    at android.view.View.access$3700(View.java:835)
    at android.view.View$PerformClick.run(View.java:28681)
    at android.os.Handler.handleCallback(Handler.java:938)
    at android.os.Handler.dispatchMessage(Handler.java:99)
    at android.os.Looper.loopOnce(Looper.java:201)
    at android.os.Looper.loop(Looper.java:288)
    at android.app.ActivityThread.main(ActivityThread.java:7894)
    at java.lang.reflect.Method.invoke(Method.java)
    at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:548)
    at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1009)
java.lang.NoClassDefFoundError: Failed resolution of: Landroidx/appcompat/widget/e0$a;
    at androidx.appcompat.widget.e0.setSelector(DropDownListView.java:1)
    at android.widget.AbsListView.<init>(AbsListView.java:899)
    at android.widget.ListView.<init>(ListView.java:231)
    at android.widget.ListView.<init>(ListView.java:227)
    at androidx.appcompat.widget.e0.<init>(DropDownListView.java:1)
    at androidx.appcompat.widget.i0.s
    at androidx.appcompat.widget.i0.q(ListPopupWindow.java:4)
    at androidx.appcompat.widget.i0.a(ListPopupWindow.java:1)
    at androidx.appcompat.widget.w$e.l(AppCompatSpinner.java:4)
    at androidx.appcompat.widget.w.b
    at androidx.appcompat.widget.w.performClick(AppCompatSpinner.java:3)
    at com.reactnativecommunity.picker.h.performClick(ReactPicker.java:4)
    at android.view.View.performClickInternal(View.java:7418)
    at android.view.View.access$3700(View.java:835)
    at android.view.View$PerformClick.run(View.java:28681)
    at android.os.Handler.handleCallback(Handler.java:938)
    at android.os.Handler.dispatchMessage(Handler.java:99)
    at android.os.Looper.loopOnce(Looper.java:201)
    at android.os.Looper.loop(Looper.java:288)
    at android.app.ActivityThread.main(ActivityThread.java:7894)
    at java.lang.reflect.Method.invoke(Method.java)
    at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:548)
    at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1009)

 

Best answer by Racheal

Hey @Tech Team Racheal from the support engineer team here👋 

 

It looks like my teammate Ayk is helping you out with this. You’re in great hands!

View original
Did this topic help you find an answer to your question?

2 replies

Racheal
Intercom Team
Forum|alt.badge.img+5
  • Customer Support Engineer
  • 512 replies
  • Answer
  • June 16, 2023

Hey @Tech Team Racheal from the support engineer team here👋 

 

It looks like my teammate Ayk is helping you out with this. You’re in great hands!


  • Author
  • New Participant
  • 4 replies
  • June 18, 2023

@Racheal thanks for the reply, will he be replying here?


Reply