Develop Reference

getting a NoClassDefFoundError on "PlusImageView"

Background
My app has a small PlusOne button in it (using Google-Play-Services rev. 21.0.2) , and recently I got the next crash report from one of the users
java.lang.NoClassDefFoundError: android.os.AsyncTask
at com.google.android.gms.plus.data.internal.PlusImageView.a(SourceFile:60)
at com.google.android.gms.plus.internal.bw.a(SourceFile:917)
at com.google.android.gms.common.internal.v.d(SourceFile:200)
at com.google.android.gms.common.internal.u.handleMessage(SourceFile:136)
at android.os.Handler.dispatchMessage(Handler.java:99)
at android.os.Looper.loop(Looper.java:130)
at android.app.ActivityThread.main(ActivityThread.java:3770)
at java.lang.reflect.Method.invokeNative(Native Method)
at java.lang.reflect.Method.invoke(Method.java:507)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:912)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:670)
at dalvik.system.NativeStart.main(Native Method)
The problem
I've followed all of the instructions of the Play Services for a very long time (including the Proguard part), and never had this issue before.
The weird thing is that I've succeeded running the app on multiple devices without any issue, and there are quite a lot of users out there that use my app . Many also uninstall, but this is the first time I get this crash.
The question
I'm not a Proguard expert, but is it maybe possible that this is the reason for it?
What could be the reason for this issue?
How can I fix this issue?
I've tried to search for this problem and there isn't even a single website that I've found regarding it.

java.lang.NullPointerException at android.webkit.WebViewClassic.setBaseLayer(WebViewClassic.java:5377)

I published an Android application that uses ACRA for crash reporting. Now I got a strange crash report:
java.lang.NullPointerException
at android.webkit.WebViewClassic.setBaseLayer(WebViewClassic.java:5377)
at android.webkit.WebViewClassic.setNewPicture(WebViewClassic.java:10781)
at android.webkit.WebViewClassic$PrivateHandler.handleMessage(WebViewClassic.java:10012)
at android.os.Handler.dispatchMessage(Handler.java:99)
at android.os.Looper.loop(Looper.java:137)
at android.app.ActivityThread.main(ActivityThread.java:4898)
at java.lang.reflect.Method.invokeNative(Native Method)
at java.lang.reflect.Method.invoke(Method.java:511)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:1006)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:773)
at dalvik.system.NativeStart.main(Native Method)
The report was sent from a Samsung Galaxy S3 (GT-I9300) running Android 4.1.1. The report is strange (from my point of view) because my app doesn't use a WebView (no display of web pages in the whole app, no HTML handling at all). Furthermore the stack trace doesn't include any of my packages. Certainly I cannot reproduce the crash.
Has anybody else encountered this (or a very similar) stack trace? Why is this exception thrown? And what can I do to avoid the exception? Any help is really appreciated.

This can be caused due to use of external ad networks that may use WebViews. This is a problem that needs to be addressed by the ad network maintainers. Apart from bringing it their attention, there is really nothing you can do about this short of removing the offending providers' ads from your application.

IndexOutOfBoundsException at android.graphics.Paint.native_measureText(Native Method)

I have an android app on Google Play and occasionally get the following error reported through the developer console / ACRA. The app runs fine on my test devices and on the various AVDs that I test it on.
The stack trace doesn't state where in the app the problem is. Is there anything I can do to narrow down where to look? What generally causes the error?
java.lang.IndexOutOfBoundsException
at android.graphics.Paint.native_measureText(Native Method)
at android.graphics.Paint.measureText(Paint.java:1020)
at android.graphics.Paint.measureText(Paint.java:1057)
at android.text.Styled.drawDirectionalRun(Styled.java:267)
at android.text.Styled.measureText(Styled.java:430)
at android.text.Layout.measureText(Layout.java:1518)
at android.text.Layout.getHorizontal(Layout.java:564)
at android.text.Layout.getHorizontal(Layout.java:548)
at android.text.Layout.getPrimaryHorizontal(Layout.java:533)
at android.widget.TextView$QuickAction.getBound(TextView.java:9550)
at android.widget.TextView$QuickAction.show(TextView.java:9604)
at android.widget.TextView$QuickActionController.show(TextView.java:8846)
at android.widget.TextView.performLongClick(TextView.java:8033)
at android.view.View$CheckForLongPress.run(View.java:9096)
at android.os.Handler.handleCallback(Handler.java:587)
at android.os.Handler.dispatchMessage(Handler.java:92)
at android.os.Looper.loop(Looper.java:130)
at android.app.ActivityThread.main(ActivityThread.java:3701)
at java.lang.reflect.Method.invokeNative(Native Method)
at java.lang.reflect.Method.invoke(Method.java:507)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller
.run(ZygoteInit.java:895)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:653)
at dalvik.system.NativeStart.main(Native Method)

From the look of this, you have a race in your application initialization block. Probably one of your text resources is not fully inflated before a draw is issued. (i know, the model of the android runtime should prevent this, but if this happens when the layout is calculated, it would be plausible).
Hope this is of some help in narrowing it down.

Any way to respond to Android users' force close messages?

I've published an Android live wallpaper for which I have recently started to get this strange force close error:
java.lang.RuntimeException: Failed to register input channel. Check logs for details.
at android.view.InputQueue.nativeRegisterInputChannel(Native Method)
at android.view.InputQueue.registerInputChannel(InputQueue.java:92)
at android.service.wallpaper.WallpaperService$Engine.updateSurface(WallpaperService.java:521)
at android.service.wallpaper.WallpaperService$Engine.attach(WallpaperService.java:651)
at android.service.wallpaper.WallpaperService$IWallpaperEngineWrapper.executeMessage(WallpaperService.java:875)
at com.android.internal.os.HandlerCaller$MyHandler.handleMessage(HandlerCaller.java:61)
at android.os.Handler.dispatchMessage(Handler.java:99)
at android.os.Looper.loop(Looper.java:130)
at android.app.ActivityThread.main(ActivityThread.java:3683)
at java.lang.reflect.Method.invokeNative(Native Method)
at java.lang.reflect.Method.invoke(Method.java:507)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:839)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:597)
at dalvik.system.NativeStart.main(Native Method)
According to this StackOverflow page the issue might be with Launcher Pro.
I want to avoid getting bad ratings for this. Is there any way to communicate with the users who send me this error report that it is not the fault of my program, and that they should run the wallpaper through their normal home screen?
I could post a note on the app's Android Market page, but that would seem to be a major distraction for an infrequent error.

You should push an update that checks for the installation of Launcher Pro and alert the user accordingly. Your market page should also have a small note somewhere that there are compatibility issues with Launcher Pro.
Check for Launcher Pro this way:
// this is the package name for Launcher Pro
String packName = "com.fede.launcher";
PackageManager packMan = getPackageManager();
// check if package exists
PackageInfo info = mPm.getPackageInfo(packName, 0);
// if info is not null, Launcher Pro is installed

java.lang.NullPointerException - AutoCompleteTextView - HoneyComb

I am getting a weird issue when using AutoCompleteTextView component on a device running on Honeycomb (Android 3.0) (using Motorola Xoom to test). I get a Nullpointer exception with the following stacktrace :
FATAL EXCEPTION: main
java.lang.NullPointerException at
android.widget.PopupWindow.getMaxAvailableHeight(PopupWindow.java:1152)
at
android.widget.ListPopupWindow.buildDropDown(ListPopupWindow.java:1054)
at
android.widget.ListPopupWindow.show(ListPopupWindow.java:516)
at
android.widget.AutoCompleteTextView.showDropDown(AutoCompleteTextView.java:1047)
at
android.widget.AutoCompleteTextView.updateDropDownForFilter(AutoCompleteTextView.java:931)
at
android.widget.AutoCompleteTextView.onFilterComplete(AutoCompleteTextView.java:914)
at
android.widget.Filter$ResultsHandler.handleMessage(Filter.java:285)
at
android.os.Handler.dispatchMessage(Handler.java:99)
at
android.os.Looper.loop(Looper.java:126)
at
android.app.ActivityThread.main(ActivityThread.java:3997)
at
java.lang.reflect.Method.invokeNative(Native
Method) at
java.lang.reflect.Method.invoke(Method.java:491)
at
com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:841)
at
com.android.internal.os.ZygoteInit.main(ZygoteInit.java:599)
at
dalvik.system.NativeStart.main(Native
Method)
Note that I do not get this exception on any other versions of Android including Gingerbread. Its really hard to debug since I do not have the original source code of Honeycomb code base. I would appreciate if anyone can help me out.
Thanks,
Torri.

I had the exact exception. Everything works in 2.*, but in 3.x there all thrown this exception, and simply try catch didn't work.
Finally I found that, if I remove the below line from the view, then it worked for me:
android:dropDownAnchor="#+id/searchField"

I am not sure if this can help but I had a similarly weird problem with a button. It worked fine on all versions except 3.0
So I did this:
try{
mButton.setOnClickListener(...
//code...
}catch(NullPointerException e){
}
After this no more errors and guess what? The button works fine now on 3.0 !