Troubleshooting
The handful of things that go wrong with a custom keyboard on iOS, what each one actually means, and what settles it.
Clink for iOSClink is not in the keyboard list
Enable Clink in iOS Keyboard settings, then hold the globe key. iOS uses its own keyboard in secure fields, and some apps block custom keyboards altogether. If Clink closes on its own, reopen it and check Stability.
- Open the Settings app.
- General → Keyboard → Keyboards → Add New Keyboard…
- Add Clink under Third-Party Keyboards.
Another keyboard keeps coming up
iOS remembers the last keyboard you used in each app, so you switch once per app.
Switch once in that app and it sticks there. No keyboard can be made the default for everything, which is iOS rather than Clink.
It disappears mid-sentence
A disappearance can follow memory pressure, a crash or a system interruption. Clink's Stability record combines memory readings, responsiveness and any captured crash marker to help distinguish them; an unfinished session alone does not prove the cause.
Search for Stability in the app to inspect or export the recent record. Dismissal readings are taken before delayed cleanup; when iOS lets the process keep running, an additional idle reading shows memory after cleanup. Test Lab checks individual features and cannot on its own establish whether repeated keyboard use is stable.
- Stability
Password fields, and apps that refuse
iOS puts its own keyboard in secure fields, so a password box is never Clink. A few apps turn custom keyboards off altogether, and nothing on your side changes that.
A tool is locked
Restore Purchases checks for existing access with the App Store, including lifetime purchases and active subscriptions. It does not charge you again.
No sound, or no haptics
Both need Full Access, and key sounds also follow the ring and silent switch. Check the switch on the side of the phone before anything else.
Still stuck
The FAQ inside the app answers more than these pages do, and Search finds a setting by what it does rather than what it is called. To report a bug or suggest an idea, tap the profile button and choose Feedback in its own menu section. Feedback also has the public board, your pinned cards, Stability reports and Test Lab. On iOS, open Board and select Complete to browse completed cards by release. Tap a release to expand or collapse its cards; the number beside it reflects your current search and filters. Cards without a release appear under “No release assigned”. Reports go privately to the team; a moderator decides what appears on the public board. Open a report under You sent to read private replies from ANTI and send more information, including when a report is not added to the board. Standalone diagnostic reports have conversations under Diagnostics. In the Android test build, open Stability or Test Lab and tap “Send to the Team” to send the report privately to ANTI. If sending fails, tap again to retry the same report. “Sent to the Team” confirms receipt. Share report and Share results still let you export files through Android’s share sheet. Private replies show an Updated indicator in Feedback; public replies appear in the board issue’s Updates. Turn on “Notify me when updates are available” in Feedback for optional reply alerts and pinned-issue status or release changes, then allow notifications when iOS asks. Tapping an alert opens its conversation or issue. Unpinning stops that issue’s alerts; turning the switch off stops all feedback push alerts. You can still read replies in the app with notifications off. Pinning alone does not enable notifications. Tap the Powered by AppBuddy badge at the bottom of Feedback to visit appbuddy.dev. You can also send us an email.
The ANTI feedback board separates iOS and Android issues. Android test builds open the Android board from Feedback in the profile menu and keep pins on the device, with no push notifications. The menu shows “Updated” when a pinned card has changed status; opening that card marks its current status as seen. Current Android test builds can send private bug reports and suggestions, and add or remove an “I have this too” vote on an Android board card. Open a report under You sent to read its private original, see ANTI’s replies and send more information. Standalone diagnostic conversations appear under Diagnostics. The profile menu also shows “Updated” for unread private replies; viewing a message marks it as read. You do not need an account to send feedback or vote. Your private history belongs to this installation, so simply browsing the board does not start a feedback history. Reports awaiting retry stay encrypted on this device and are excluded from backup. If the team publishes a report, its card is pinned once; you can unpin it. A reply awaiting retry stays encrypted on this device. Retry after a lost connection without retyping your message; Clink avoids sending the same reply twice. Replies remain private even when the report has a public board card. Diagnostic attachments and Android push alerts are still being ported. Email remains available.
- FAQ
- Search
- Feedback