SOLVED: onActivityResult - requestCode is 0, not Activity.RESULT_OK

Android Programming (3rd Edition) 5. Your Second Activity
1

I added a few more Log.d statements, and after the code
if (resultCode != Activity.RESULT_OK) { - I have:
Log.d(TAG, "(notOK) - onActivityResult.resultCode = " + resultCode);

After rotating the screen twice and pressing back, I see the following in logcat (Two filters):
QuizActivity
onCreate(Bundle) called
onStart() called
onResume() called
onPause() called
onSaveInstanceState
onStop() called
onActivityResult() called
(notOK) - onActivityResult.resultCode = 0
onStart() called
onResume() called
checkAnswer.mIsCheater = false

CheatActivity
onCreate(Bundle) called
onCreate.mIsCheater = false
setAnswerShownResult.mIsCheater = true
onSaveInstanceState
onSaveInstanceState.mIsCheater = true
onCreate(Bundle) called
onCreate.mIsCheater = true
onSaveInstanceState
onSaveInstanceState.mIsCheater = true
onCreate(Bundle) called
onCreate.mIsCheater = true

It looks like the back button does not send resultCode=RESULT_OK, but a zero. I am running:
Android Studio 2.3.1
GenyMotion with Google Nexus 5X API 23.

Is the value of zero correct? Pressing the back (arrow that makes a U turn on right Panel on virtual device). Am I pressing the correct button?

Thank you,

Ken Lee

2

I believe I found the problem. When getting the value from savedInstanceState, just needed to call setAnswerSHownResult(true) if the save value for cheating was also true. Creating the intent to return each time the screen refreshes (if needed) was not the expected behavior. I can see it now as the Java class goes through onDestroy, then onCreate with each rotation.