Skip navigation

Just a quick tip: if you accidentally pass a data type to someTextView.setText() that cannot be implicitly coerced into a CharSequence representation (like, say, an int), logcat will display the error ‘fatal error: Resource$NotFoundException’ citing some weird hex String resource id that you probably don’t recognize. I have no idea why the Android framework does this in response to mismatched data types, but there you have it– if you see a contextually nonsensical error about some resource not being found around a TextView’s setText() method, check the data type of the argument you’re passing to setText().

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

%d bloggers like this: