Once you have your app published for a while, you will see all kinds of weird crash reports. I, for example, cannot duplicate 80% of the crash reports I get. Of course, Google's refusal to actually share any info about the device, such as device type, OS version, etc, makes it extremely difficult to do anything.
On Oct 3, 9:12 am, NickL <[email protected]> wrote: > Hi - crash report is showing this: > > "Android.View.InputChannel.nativeReadFromParcel - Could not read input > channel file descriptors from parcel." this seems to occur when the > user pressed a button that inflates a dialog. Seems like standard > stuff. > > I googled this message and only see it in a Cyanogenmod code listing. > Is it possible this is a bug related only to Cyanogenmod users? > > Also - in the android.view.InputChannel source is has this comment: > "An input channel specifies the file descriptors used to send input > events to a window in another process. It is Parcelable so that it can > be sent to the process that is to receive events. Only one thread > should be reading from an InputChannel at a time.". > > Is it possible that somehow by opening a dialog (view) I am violating > the rule of only one thread reading from the input channel? Is there > maybe some cleanup I should be doing after opening a dialog? -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
