![]() Gah I’m so torn on this, but wanted to throw my 2¢ at because I think this is an often overlooked yet super important part of note making on iOS. In case there’s nobody at ShinyFrog who’s actually invested as a TextExpander user on iOS/iPadOS, I suppose I can get around to relaying my perspective on their purposed replacement as someone who’s professional life will be profoundly impacted if/whenever this transition does occur…įor now, though, the most relevant argument I have to make to Bear 2’s development is: aside from the single announcement last year, nothing else has changed for TextExpander users on the release builds of the iOS/iPadOS apps, so if it would be at all possible, I would plead for you to carry Bear 1’s teSDK integration over to Bear 2 in order to maintain support for TextExpander users, going forward. The updated TextExpander will also no longer support fill-ins initiated from apps with SDK support. Later this year, when we release the updated keyboard, TextExpander will no longer support updating snippet data via the x-callback-url mechanism. I’m going to assume you devs haven’t been thinking much about the teSDK since its announced “sunsetting” last August and have probably been waiting to see… any further progress. ![]() (Let me know if you’d like me to move the above to # bug-reports.) Normally, the Enable TextExpander Snippets button causes the X-Callback-URL-powered integration flow to refresh snippets. Neither the toggle nor the Enable TextExpander Snippets button were responsive.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |