Closed chrisonline closed 6 years ago
Mmmhhhh that really looks like a strange error. Can you give me some more details on what Android version or device this is happening on?
It can somehow only be a mistake in the implementation of ArrayAdapter, as the PickerSpinner constructs a new one in initAdapter() and then calls setAdapter() with it. A subsequent call to getCount() on the ArrayAdapter should never throw a NullPointerException.
Android versions are 7, 5 and 4! Models Huawei and Samsung.
I don't have implemented ArrayAdapter. I use the default entries. So it should use the libraries date_items.xml so far I know.
Mmhh so not a single android version to blame here...
The thing is, the crash happens in ArrayAdapter.getCount(). This can only happen if its internal mObjects List null, but this is never the case if one takes a look at the source here. At least I don't see any way this can happen with the current version of this. Might be that some different versions of the class exist in vendor modifications. That is what I meant with implementation of ArrayAdapter above. It also does not really matter how many items are in the List, mObjects should never be null in any case.
OK I understand. Really strange. At the moment I had only about 8 users with this crash. So not a huge impact.
I think we can close this. Never had more than a few users with this crash.
In my Crashlytics logs I get some reports with NullPointerException. See attaches crashlog. It happens at after
setContentView
: