...ote to current active(native) keyboard.
@ulion for a comment. Before we always received the trailing carriage return which gets send from the official remote app when "closing" the keyboard by hitting the "enter" key.
I think we never want that trailing carriage return (in my test case it prevents from inserting a valid new source for example cause the added path ends with "carriage" return and so the vfs will never be able to open it...).
[ios] - strip off trailing carriage return when inserting text frome …
…remote to current active(native) keyboard
fyi this also affects generic keyboard - its definitly gotham material and was introduced in f429754 i guess...
Ohh - ok - so it is a json issue? Or more a Remote issue?
let me check the remote app, keyboard code it's untouched since frodo times
Yes, the remote app sends the carriage return at the end of the string. It's superfluos send it, removed joethefox/Unofficial-Official-XBMC-Remote@74cf9c3
So as this change in the offical remote will make it to the appstore at some point (thx joethefox for the quick fix :o) ). Do we just close this PR? Or do we need to pay attention of trailing carriage return because those issues could come from other remote apps too? Any ideas?
The remote needn't send a carriage return. IMO close.