Falling AutoCompleteTextView in Android 7.0, for Samsung Phone model

I am using AutoCompleteTextView as input field for url, it works fine on Android 6.0 and below. But recently, when Samsung released an update to its Android system for android 7.0, we got a lot of crashes. Phone model contains: SM-N920V 422 SM-G955U 549 SM-G925F 685 SM-G920V 418 SM-G920F 1045

No other phone model found other than Samsung.

Log below:

03-14 15:57:54.973 E/AndroidRuntime(  564): java.lang.NullPointerException: Attempt to invoke virtual method 'void android.view.View.setOnClickListener(android.view.View$OnClickListener)' on a null object reference
03-14 15:57:54.973 E/AndroidRuntime(  564):     at android.widget.Editor$SuggestionsPopupWindow.initContentView(Editor.java:3714)
03-14 15:57:54.973 E/AndroidRuntime(  564):     at android.widget.Editor$PinnedPopupWindow.<init>(Editor.java:3375)
03-14 15:57:54.973 E/AndroidRuntime(  564):     at android.widget.Editor$SuggestionsPopupWindow.<init>(Editor.java:3660)
03-14 15:57:54.973 E/AndroidRuntime(  564):     at android.widget.Editor.replace(Editor.java:423)
03-14 15:57:54.973 E/AndroidRuntime(  564):     at android.widget.Editor$3.run(Editor.java:2340)
03-14 15:57:54.973 E/AndroidRuntime(  564):     at android.os.Handler.handleCallback(Handler.java:751)
03-14 15:57:54.973 E/AndroidRuntime(  564):     at android.os.Handler.dispatchMessage(Handler.java:95)
03-14 15:57:54.973 E/AndroidRuntime(  564):     at android.os.Looper.loop(Looper.java:154)
03-14 15:57:54.973 E/AndroidRuntime(  564):     at android.app.ActivityThread.main(ActivityThread.java:6724)
03-14 15:57:54.973 E/AndroidRuntime(  564):     at java.lang.reflect.Method.invoke(Native Method)
03-14 15:57:54.973 E/AndroidRuntime(  564):     at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:1520)
03-14 15:57:54.973 E/AndroidRuntime(  564):     at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1410)

      

So who can tell me what happened? Why is this crash only found in Samsung android 7.0 and what can we do to avoid it.

+3


source to share


1 answer


This is a Samsung bug. See this link



+1


source







All Articles