Saturday, July 7, 2012

[android-developers] forceclose problem after startActivity()

We have an app on the market for a while now, mostly it works great. But recently we got a couple report that it force closes on some devices, since we don't have those devices to debug the problem, I hope I can ask the question here and maybe someone can share some lights about what we should do.

The basic problem is that we have an activity A, which has a button for people to configure some information. So, we have an Activity B which collects those information. So, user click the button and Activity B will pop up, after users finish the settings, they click finish button or cancel button there and Activity B closes and Activity A has a "onActivityResult" call which collect which button was clicked and will adjust some information. But this force closes on some devices after user click either button.

We added some debug code in "onActivityResult" but it finished the call to the end without crashing, so, we have no idea what other function should be called after that. We don't have onResume function in Activity A because we thought since we don't care about it, it should just use the default implementation. And we do have onSaveInstanceState function. So, one user who has this problem is willing to test anything or we can add debug code to anywhere, but since onActivityResult returns okay, we have no idea what to do next. 

Any suggestions about how to figure this out without the actual device to hook up the debugger?

Thanks

--
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+unsubscribe@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en

No comments:

Post a Comment