NoteEditorIntentTest flaky test after the intent handling changes

[mikehardy]

          We have a new flaky test after the intent handling changes, this popped up on another PR recently as well and caused merge queue ejection

com.ichi2.anki.NoteEditorIntentTest > launchActivityWithIntent[emulator-5554 - 11] FAILED 
	java.lang.ArrayIndexOutOfBoundsException: length=0; index=0
	at com.ichi2.anki.NoteEditorIntentTest.launchActivityWithIntent$lambda$0(NoteEditorIntentTest.kt:54)

Originally posted by @mikehardy in #15692 (comment)

• step 1 mark flaky but not as resolving this issue
• step 2 determine why this is flaking on emulator tests, may require instrumentation (that is, logging and such) in the test so it can run on the CI runners to get their timing (they are slower than your local machine) and then download the logcat to see what your logs say about why it failed

[david-allison]

@criticalAY was this one which you added?

[criticalAY]

Yes, but it worked fine, would look into it

[criticalAY]

I suspect the field is accessed before the editor is properly set i.e. the progress bar is still there and field is tried to set text on, as when the intent is passed it takes a second (emulator is slow so its visible)

[github-actions]

Hello 👋, this issue has been opened for more than 3 months with no activity on it. If the issue is still here, please keep in mind that we need community support and help to fix it! Just comment something like still searching for solutions and if you found one, please open a pull request! You have 7 days until this gets closed automatically

[github-actions]

Hello 👋, this issue has been opened for more than 3 months with no activity on it. If the issue is still here, please keep in mind that we need community support and help to fix it! Just comment something like still searching for solutions and if you found one, please open a pull request! You have 7 days until this gets closed automatically