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
Hold the globe key and choose Clink. On Android, choose Clink from the keyboard picker. You can switch back to another keyboard at any time.
If the keyboard changes only in a password field or a particular app, check the password-fields answer below. Re-enabling Clink or reinstalling it will not override an app’s keyboard restrictions.
It disappears mid-sentence
Switch to another keyboard and back to Clink. If it keeps restarting, open Feedback and send a report. Include the app you were using, the approximate time, what you expected and the steps that caused it. Your report goes privately to the team.
During an ordinary memory warning, Clink keeps swipe typing ready while reducing other optional work. If memory remains tight, upcoming iOS builds wait for more space before reopening the sentence model. Typing continues with the available suggestions while it recovers. Under severe pressure, swipe typing may need a moment to become ready again. 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. With no recorded sessions, the graph shows a still line. Once sessions are recorded, it shows their memory readings and highlights recorded restarts. 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. After installing an update, run Test Lab again before sharing results: a saved run still describes the earlier test. Upcoming iOS and Android builds include the test’s own app version in newly saved results, and new Android Stability records retain the version used during each keyboard session. Older records keep their original date without being relabelled as tests of the current app. In the next iOS test build, a temporary connection failure keeps the previously available Send to the Team button visible. Pull down on Stability to refresh the record and retry checking report availability.
- Stability
In Android test builds, Test Lab also measures the installed sentence model. Its results show loading time, memory change and inference latency on your device. A missing or unsupported model is reported as skipped. These performance measurements use built-in test inputs and do not read your messages; they do not measure how often a suggestion is the word you intended.
The top of the iOS keyboard looks distorted
If the area above the first row looks clipped or distorted when Clink first opens in an app, switching to Apple’s keyboard and back may temporarily clear it. This has been reported on iOS 1.9.1 with Top Bar both on and off. You do not need to reset your layout to report it. In Feedback, include your iOS and Clink versions, the affected app, whether it happens on the first opening, and whether switching keyboards clears it. A screenshot of the keyboard area helps; crop out private messages.
The Android keyboard covers the message box
If Clink covers the message box in Telegram while your phone uses three-button navigation, switching Android to gesture navigation can help until you install the update. Current Android test builds keep the message box above the keyboard while leaving the bottom key row clear of the navigation buttons, including after the keyboard has been inactive. With gesture navigation, the keyboard also adjusts if Android's dismiss and keyboard-switch buttons appear after the keys, so the bottom row does not stay trimmed until you reopen it. Rotating the phone keeps the keys clear of navigation buttons at the bottom or side without adding an extra bottom gap. Upcoming Android test builds also recognize Xiaomi’s gesture-navigation preference. Space needed for Android’s own keyboard controls remains, even when the gesture indicator is hidden. If an unexpectedly large empty strip remains on HyperOS, include the HyperOS version and whether the gesture indicator is hidden in your report. If it still happens, send a report through Feedback with the app name, phone model, Android and Clink versions, and your navigation mode. Include whether closing and reopening restores the full keyboard. You do not need to share your messages. If folding or unfolding a Galaxy device bunches the key labels together, closing and reopening the keyboard is the reporter’s temporary workaround. An upcoming Android test build refreshes the keys for the keyboard’s new width. When reporting this, include your Galaxy model, Android/One UI and Clink versions, and which direction of the fold causes it.
The next Android test build also handles single-line fields that expect Enter as a key press rather than text, and lets Backspace reach a rich-text editor when a new paragraph exposes no preceding text. These changes address launcher search and paragraph boundaries without changing multiline Return behavior.
Password fields, and apps that refuse
iOS uses its own keyboard in fields marked as secure. Apps can also refuse custom keyboards entirely. A bank may display its own warning and block access while a custom keyboard is selected or enabled; that warning alone does not establish that Clink has collected data. If a bank asks you to switch keyboards, select the device’s built-in keyboard and reopen the bank app. If the warning remains, contact the bank through its official support channel and include the warning, device, operating system and app versions. Clink cannot override another app’s access policy. Do not include account details, passwords or one-time codes in a Clink feedback report.
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
If Clink disappears or another keyboard takes over when you switch apps, open Feedback > Stability and share a report with the team. Include the approximate time and whether you were switching apps, opening a text field or typing. App names can help reproduce the problem; you do not need to include your messages. An unexpected session ending alone does not confirm a crash, so the report helps the team distinguish a recorded crash from a possible memory-related restart.
Open FAQ for short answers and buttons that take you to the relevant setting. You can search in your app language or in English. Ask Clink matches your question to an answer in the FAQ on your device; it does not require Apple Intelligence or send the question to a server. The full guide is at anti.ltd/docs/clink. To report a bug or suggest an idea, open the sidebar, choose More, then Feedback. Feedback also has the public board, your pinned cards, Stability reports and Test Lab. Feedback pages scroll up and down within the screen; swipe across the filter rows on Board to see more filters. 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 Test Lab, Autocorrect test lets you report a sentence without running the performance tests. Type with the Clink keyboard in “What Clink typed” and leave unwanted corrections or missed typos as they are. In “What you meant”, enter the intended sentence. Both fields allow autocorrect when it is enabled in your keyboard settings, so check the intended sentence before sending. Each field accepts up to 1,000 characters; both are required. Tap “Submit test” to send the pair and device details privately. Avoid personal information. The original sentence stays separate while you edit the intended version. After a failed send, retry the same pair; “Sent to the Team” confirms receipt. Tap “Run again” to start another test. These sentences are not included in the automatic performance results, feedback attachments or Share results exports. 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. In the next Android build, sending feedback includes your phone model, Android API level and Clink version and build. For a visual problem, name the app where you saw it, describe what appeared and include the steps that led to it.
The ANTI feedback board separates iOS and Android issues. Android test builds open the Android board from Feedback under More in the sidebar and keep pins on the device, with no push notifications. The Feedback row in More 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 Feedback row 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 a request times out, Clink says so and keeps the report for retry. Try again with the same draft; a lost response does not require a new report. iOS also distinguishes a request timeout from a connection failure. 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
Android test builds show Android-specific update notices and announcements on Home. Open the sidebar → More → Updates to control automatic update and MOTD checks, or tap Check for updates to check manually. Tap anywhere on a toggle row to change it. In the next Android test build, each notice has a visible × button beside its text. Tap it to dismiss that notice independently; dismissing an announcement leaves any update notice visible. The same announcement stays dismissed after reopening Clink, while a new announcement can appear. Android never displays an iOS release announcement.
To see released changes on iOS or Android, open the sidebar → More → Updates and choose What’s New. The changelog opens the history for your platform. On iPad, More → Preferences opens a larger, scrollable panel so the controls remain reachable.
If correctly spelled Russian words are underlined red on Android, note the affected app and your phone’s spell-checker language. Clink’s next Android test build reports the active keyboard language to Android, which may help the system choose the right spelling dictionary. Apps can also use their own spell checker. If the underlines remain, include a non-private example word, your Clink version and your system spell-checker settings in Feedback.