# Diagnose Jianlai by field type: ordinary text, secure input and host restrictions Language: en Canonical: [Diagnose Jianlai by field type: ordinary text, secure input and host restrictions]() 中文：[中文 HTML]() English: [English HTML]() Published: 2026-11-15T00:00:00+08:00 Modified: 2026-11-15T09:50:10+08:00 Author: Bison Start with a working ordinary note and identify platform boundaries without treating extra permissions as a universal repair. English translation of the [Chinese original](), translated on 2026-11-15. Original publication dates, attribution, code and version notes are retained. Start with a working ordinary note and identify platform boundaries without treating extra permissions as a universal repair. ## 1. Establish a working ordinary-text control In an ordinary saveable note, select Jianlai, enter a nonsensitive passage and verify candidate commitment and document text. Return to the system keyboard to confirm a fallback. Record system version, Jianlai version and host while preserving settings and text. If this baseline fails, revisit installation, enabling and selection first. This task compares a working control with different locations; it does not require testing every financial or work app, and real passwords are not test characters. ## 2. Identify the field’s purpose before diagnosing a defect Describe the affected location: ordinary document text, a password-labelled area, dedicated phone input, or a host showing only the system keyboard. Labels help identify purpose but do not prove internal implementation, so separate observation from technical explanation. Record visible keyboard and switching availability without entering real credentials, codes or payment data. If type is uncertain, mark it unchecked rather than claim Jianlai was blocked by a named app or imply you inspected that host’s source code. ## 3. Understand the secure-input replacement boundary Apple’s custom-keyboard documentation explains that secure text input temporarily uses the system keyboard, with ordinary input returning under system rules afterward. A password area displaying the system keyboard alone does not prove a Jianlai crash, lost theme or failed installation. This is a platform boundary, not a bypass exercise; additional access is not a tool for forcing a third-party keyboard into secure fields. You may simply observe an authorised empty field and leave, without creating or submitting a real account action. ## 4. Identify dedicated phone-pad behaviour separately Apple’s extension guide also describes dedicated phone-pad restrictions. Digits alone do not identify that field type: an ordinary note accepts digits too. Retain purpose and visible behaviour instead of excluding third-party keyboards from every numeric field. If already authorised to inspect a phone-entry area, observe the keyboard without entering a real number or initiating a call. Compare a nonsensitive digit in the ordinary note, distinguishing a system-selected phone pad from Jianlai’s own digits/symbols page. Unconfirmed field traits remain unknown. ## 5. Separate host-wide restrictions from one field Apple’s current developer API allows hosts to reject an extension type; its archived keyboard guide specifically discusses custom-keyboard restrictions. A host always using the system keyboard may therefore need host-boundary investigation, not a promise that reinstalling a theme will change it. Compare another ordinary editable area in the same host, then the working note, recording scope. Do not conclude an unverified policy for a named app or submit forms repeatedly. Host policy, field type and Jianlai enablement are separate layers. ## 6. Verify recovery in the ordinary note Return to the original note, identify the active keyboard, reselect Jianlai through the available control if needed, and enter a short marker. The system may retain or change current selection; automatic identical recovery across every host is not promised. Record the observed theme and Chinese layout. A special field not showing the theme is not evidence that configuration was deleted. Preserve before/after results and the system-keyboard fallback. Recovery does not require deleting documents, resetting the device or clearing every keyboard setting. ## 7. Choose the next check by failure scope If only a special location fails while the note works, retain field/host scope instead of changing every permission. If the note fails too, inspect enabled list, active selection, candidate confirmation and focus. For appearance-only differences with working input, use the theme or font lesson instead of a secure-field diagnosis. Change one condition and preserve exact errors and version. Use a self-made nonsensitive illustration for help, not credentials, full chats or managed data. Unknown causes do not establish a repair of all compatibility issues. ## 8. Deliver a diagnosis with explicit boundaries Restore everyday keyboard/settings and confirm the ordinary note still accepts and saves text. Deliver baseline, affected location, field purpose, visible keyboard, host comparison and recovery, separating observations, Apple platform guidance and unresolved causes. Acceptance means knowing which differences need enablement checks and which involve system boundaries, rather than forcing a third-party keyboard everywhere. Do not classify untested hosts as passed or failed, or describe this task as security certification, a permission audit or a physical-device compatibility guarantee across every input environment. ## Related tutorials and sources [First enablement](), [Switching across apps](). Checked on November 15, 2026 against [Apple public lookup]() and the [official App Store information and screenshots]() it lists: version 1.0.5, requiring iOS / iPadOS 16.0 or later, with identity and version cross-checked against China lookup. Tasks use published capabilities; identify actual controls in your installed version. External records are acceptable. Keep expectations separate from observations; no physical-device or universal input-environment test is claimed. [Apple archived guide: custom-keyboard boundaries](). [Apple current API: host permission for extension types](). [Official Apple screenshot: personal keyboard]().