I see now that it's context dependent. However, when entering text for a search string in the browser, Swiftkey shows a "Send" key instead of "Enter/Return". When I have an Enter/Return key there, I can just press it and the browser starts my desired search immediately. With the "Send" key, I press it and nothing happens other than a space character appearing immediately after the search string! If I press it twice, the browser will finally start my search.
This is just the wrong context for Swiftkey to have a "Send" key in place of the "Enter/Return" key. In fact, I'd rather have it be an "Enter/Return" key all the time, that has always worked for me in all contexts. So I'm about ready to throw Swiftkey out of the boat, although I've happily used Swiftkey on Android for a couple of years...On Android Swiftkey, the "Enter/Return" key never changes to a "Send" key, so I think that this is just broken on iOS 8. I really don't like it when keys on a keyboard change depending on context, anyways, that just a badly designed user interface.
If they don't fix it soon I'll be dumping Swiftkey until they do fix it. I really did like Swiftkey on Android, but on the iPad not so much. Maybe I can find another keyboard, other than the Apple keyboard, that works well on the iPad. Bums me out, I was looking forward to being able to use Swiftkey on iOS 8 like I could on Android.