So remember that other thread where I had a $100 bounty (along with Fleksy - and I forgot to add it in (because I thought nobody was getting the bounty anyway), but Next Keyboard was in on it too) for anyone that can find a consistent way to trigger a non-popup situation?

Well, I found one, and it's worked 9 out of 10 times so far, so I think I got it.

:::::::::::::::::::: Steps: :::::::::::::::::::::

Ingredients: we need Nintype, two apps that uses the keyboard (get some todo app, and use the Notes app as the second one)

First of all, enable developer mode on nintype (search options (the find icon at topright of options->more..) for "developer mode") edit: looks like you need to be on the latest nintype beta after all :/

1. open an app (call it APP_A) that uses a keyboard (notes, clear, most todo list apps)
2. bring up nintype on APP_A
3. open another one (call it APP_B) that also uses a keyboard
4. bring up nintype on APP_B
5. open the OPTIONS menu (either from holding spacebar / topleft button) -> OPTIONS, but don't go to "MORE.."
6. Slide left on that menu, then tap "SUDOKU"
7. Trigger the JETSAM crash by tapping the JETSAM button
8. wait 5 seconds, and jetsam will terminate nintype
9. bring up the keyboard again. a) If you have only nintype enabled, you have to press home button, then go back to the app b) If you have more than one keyboards enabled, just use the iOS globe button to switch back to nintype
10. Go back to the home screen (press the home button)
11. Now, go to APP_A through its app icon (don't use task switcher)
12. Repeat steps 5-10 (the jetsam sudoku and restarting) on APP_A
13. Finally, go back to APP_B and try to bring out the keyboard. It's gone, nothing comes up! note: if it still comes back up in APP_B, do steps 5-10 on APP_B and go back to APP_A and see the keyboard fail to popup

IMPORTANT: don't switch apps using the task switcher. Press the home button and open the apps from the home screen

Let me tell you, this is not supposed to be what happens. The iOS keyboard proxy should be reflecting nintype, as it is running on APP_A just a while back!

Somehow this doesn't happen when using the task switcher

So I guess I win? I won't be claiming the prize - I just want people on 9.3 to try the steps, and let me know if it still happens?

Regardless, I'm gonna file a radar report, and will be seeing if I can get the other developers to file a duplicate radar report. I'll then send this to Apple's Keyboard man.

Now what will I do with the $100 I set aside for the prize money? I think I'll buy alcohol, get drunk, and pretend I never went into iOS custom keyboard development.

TL;DR: I won my own contest, none of you won, I'm gonna get drunk with $100 of my own prize money. Those on 9.3 beta please try the steps and report back because I haven't installed 9.3 beta yet