I am trying to design a custom keyboard, but can’t get it to work in Fire. Attached is an example (universal app), just made from an empty Oxygene template, and I’ve added the keyboard extension. There are two in the folder, the first Oxygene, the second swift (which is the one currently attached to the project).
When you run the app, add the keyboard then try and select it, nothing happens on-screen but the following errors are generated:
2015-07-07 15:29:23.153 UniversalApp8[33281:7856778] Hub connection error Error Domain=NSCocoaErrorDomain Code=4099 “The operation couldn’t be completed. (Cocoa error 4099.)” (The connection to service named org.me.UniversalApp8.CustomKeyboard2 was invalidated.) UserInfo=0x7f830266ddf0 {NSDebugDescription=The connection to service named org.me.UniversalApp8.CustomKeyboard2 was invalidated.}
2015-07-07 15:29:23.154 UniversalApp8[33281:7856778] plugin org.me.UniversalApp8.CustomKeyboard2 invalidated
Does this one work for you? i literally just created a new app, added the keyboard project, let Fire connect the two, and ran. The keyboard shows fine on my iPhone.
No, same problem. How did you activate the keyboard then, since there wasn’t a text field in the attached storyboard. I added one, activated the keyboard in settings then tried again.
Note, I’m trying this on the simulator since I’m having trouble getting it to run on a device, due to some problems getting the certificates/profile stuff right. Will log another case for that, after I’ve tried Fire 8.2
Also, as a separate issue, once you’ve activated the keyboard there doesn’t seem an easy way to make a change to it, which makes debugging hard.
For example, with the app you created, run it so you see the keyboard (on a device), then close the app and change the text on the button and re-run, and it doesn’t show the change, and the only way I’ve found to make it work again is to delete the app and its keyboard then re-run but this isn’t good for a main app, as you lose everything of course.
ah, i only tested on device. i’ll check the Simulator in the morning. Did you get the provisioning issues sorted out?
i noticed that too— but i assume the same applies to Xcode? Does killing the app hard work? If not, i guess rebooting the device should. I agree it’s odd and very inconvenient.
[quote=“mh, post:6, topic:6511”]jeremy:
Also, as a separate issue, once you’ve activated the keyboard there doesn’t seem an easy way to make a change to it, which makes debugging hard.
i noticed that too— but i assume the same applies to Xcode? Does killing the app hard work? If not, i guess rebooting the device should. I agree it’s odd and very inconvenient.
[/quote]
Xcode works fine. In fact, it’s such a simple job, I had to give up trying to do it in Fire so did it in Xcode, the only thing I could get to allow a change was deleting the app, though I didn’t try rebooting. I did it in swift though, so maybe one day I can come back to it in Fire, though I did get an error trying to compile the Xcode swift (logged in Silver topic).