Good analysis and reasoning. It leads to identifying a specific version of 
the OS.

Let me add to the reasoning: If this was a bug in android-2.3.4_r1, 
wouldn't many other apps that call the same function also trigger this bug? 
Then the history would show a 2.3.4_r2 release with this bug fixed. I am 
guessing that since that may not be the history, then other app developers 
have found a way to avoid this bug. You need to find that method and add it 
to your code.

The problem may be that the specific stack trace you're looking at is 
showing where the problem is triggered, but it is not showing where the 
problem gets set up. Maybe android-2.3.4_r1 is the only OS version which 
allows a null string to be returned from a certain function call that 
you're making. Your code might rely on that string always being non-null, 
and passes it into this call stack. The other OS versions don't have the 
problem because they don't have the conditions that produce a null string.

Your code could test that string for null, and avoid making the call if it 
is. If you must make the function call, you could replace the null string 
with something else that won't cause the error. Emit a message, so you can 
track the problem. Enhance the later code to continue gracefully if the 
string was found to be null. This is defensive programming. You're right in 
thinking it should not be necessary, but you must also consider the reality 
that it is.

-- 
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en
--- 
You received this message because you are subscribed to the Google Groups 
"Android Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to android-developers+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to