Debugging the extension #27
-
Hi there! Wasn't sure whether I should start a discussion or create an issue, but as it's probably the "operator's" fault and not yours guys, I thought this place is gonna be more appropriate :D So, I've pretty much set up the SDK with my application which multiplies two integers. Keyboard is there, all nice and shiny, but I wanted to debug one of the callbacks in the examples (https://github.com/FleksySDK/fleksy/blob/main/keyboardsdk-integrations/keyboard-ios/FleksyKeyboardSDKApp/keyboard/KeyboardViewController.swift) (in fact, any of the functions there: when it asks which app I want to run, I select mine. Does not stop at any of the breakpoints though :( is it too late (when I open my app and select an input field, default keyboard shows up and only then I switch it to Fleksy's keyboard), or I've not enabled something somewhere? I can debug my application just fine, as well as the accompanying library of mine. An additional smaller question: is this expression from the examples:
supposed to change the bar with suggestions? Tried looking through the reference, but there's no crawler/quick search available anyway so was hard to look for info with only such keyword in mind :( Additionally, maybe it'd be good to have some template for the issues/discussions as well (okay, maybe for the issues is enough :D) - I've got Xcode 14.2, Mac M1 Pro, simulating iPhone 14 Pro, not sure if that's enough for the environment? Sorry for bothering and have a great day! Cheers, |
Beta Was this translation helpful? Give feedback.
Replies: 3 comments 2 replies
-
Beta Was this translation helpful? Give feedback.
-
Hey @xevifar , nice thanks for such a quick response. Yeah so this is exactly what I've been doing, unfortunately. I did select the extension, then it asks through which app I want to debug: does not stop at any of the breakpoints though. Let me do some more reading about debugging keyboard extensions in general first though, because it might not be related to Fleksy itself but rather Xcode debugging itself. Apart from that (or maybe it's somehow related?? maybe an out-dated binary being loaded, not sure...), the Cheers, |
Beta Was this translation helpful? Give feedback.
-
So, one of the replies within this discussion could be an answer, but I wasn't sure how to mark it as an actual answer: |
Beta Was this translation helpful? Give feedback.
hi @xevifar, thanks for getting back to me 🙌
so, debugging wasn't that simple. It was a broader problem of extensions debugging - I tried with out-of-the-box keyboard extension first and debugging hadn't worked either. This answer in particular helped me: https://stackoverflow.com/a/27352955/5430833.
This step was critical:
One more thing was that the
KeyboardViewController.swift
file was not added to target (and this is by default when adding keyboard extensions in Xcode it seems):Eventually, it…