States, languages and diagnostics
Jianlai diagnostic record: separate the local diagnostic entry from an external reproduction card
Start with a three-character card in an ordinary note, retain confirmable information from the actual local diagnostic entry and write a separate manual reproduction card. Distinguish user observations, diagnostic-page text and proposed causes, without promising repair, automatic export, exhaustive host checks or report sending.
On this page
Start with a three-character card in an ordinary note, retain confirmable information from the actual local diagnostic entry and write a separate manual reproduction card. Distinguish user observations, diagnostic-page text and proposed causes, without promising repair, automatic export, exhaustive host checks or report sending.
1. Choose a genuinely observed phenomenon
Record an actually observed keyboard, candidate or return-from-settings difference; no fault needs to be manufactured. Normal input can form a clearly labelled normal baseline rather than a claimed reproduced error. Record version, device category, host, orientation, language and last relevant action, holding the observed theme and font. Use a new ordinary draft and preserve originals. The official settings image shows a Local diagnostics sidebar entry but does not enumerate its fields or error codes. Build your own observation record first instead of waiting for an unpromised automatic report to supply the origin.
2. Establish the action origin with three characters
Enter 岸40 in an identifiable ordinary field: one Han character and two ASCII digits, without spaces, period or newline. Confirm Jianlai, then observe entry and committed text, retaining actual results. A visible candidate 岸 with an empty document is another state. For incomplete entry, record the reached step and visible response rather than substitute the target string for observation. Three characters narrow the reproduction; they do not cover all schemes or provide an accuracy rate. A long existing document obscures the first changed step and makes diagnostic information harder to associate with user actions.
岸40
3. Find the actual page and copy existing fields
Preserve the card and state, return to Jianlai’s containing app and find an identifiable Local diagnostics entry using the installed flow. Do not substitute ordinary keyboard settings, system analytics or another app’s log. Record actual page name, visible fields and verbatim responses. Mark absent items not provided; the sidebar image does not imply memory, network, permission or host-event lists. Without the entry, retain version and stopping point while still completing the external card. Opening a page establishes entry only, not completed diagnostics, repair or universally passed checks. Record any real action control separately only after identifying it.
4. Separate diagnostic text from your interpretation
Preserve visible information as stated and put your interpretation in a separate column, without invented status codes. A normal item covers that identifiable scope only; it does not disprove a previous candidate issue, and no obvious warning is not all-host certification. “Possibly font-related” is a hypothesis, not a diagnosed corrupted font. Without an identifiable export action, manually retain necessary fields rather than invent automatic upload, complete-log copying or one-click repair. Keep timing explicit: the diagnostic page was opened after the event, not simultaneous evidence of the original state.
5. Link before and after states in a manual card
Fill the manual fields below in an external note you control: baseline, trigger, actual result, basis for expectation and stopping point. Expectations can come from the target 岸40, a confirmed prior baseline or cited public documentation, not an imagined button contract. Write each action once, such as entering one setting, changing one value, returning to the same draft and checking the same card. Leave unperformed actions blank rather than turn them into an executed script. This is a manual format, not an importable Jianlai diagnostic file. Attach specific diagnostic text separately so reviewers can trace each conclusion instead of treating the external table as app-generated.
manual reproduction card
version / device / host / language / original values
baseline / one trigger / actual result / expected-result source
local diagnostic text / observation timing / repeat / recovery / pending
6. Repeat one recoverable condition and preserve both rounds
If the original action is recoverable and a repeat is desired, restore the confirmed value and repeat only that condition, recording whether it recurs. Otherwise mark not repeated and preserve round one. Differing rounds retain their own host, orientation and origin. A normal baseline may simply repeat the card without disrupting settings to force a warning. Opening diagnostics may itself separate keyboard sessions, so retain it as a possible condition change; improvement does not establish a hidden repair. Do not claim unobserved stability duration, and two rounds are not statistical certification of all scenarios.
7. Fill evidence gaps instead of guessing internals
For a missing origin, recover the saved original value; for a missing result, inspect retained text; for an unexplained field, preserve its wording and uncertainty. None establishes an internal cause. No warning after opening diagnostics does not mean every network, dictionary or font was checked, and one screenshot cannot diagnose a defective host. A second host needs a separate condition, not a renamed replacement for round one. Invent no dictionary reset, cache clearing or log-sending repair. If ordinary input remains unavailable, deliver a specific stopping point and currently usable route rather than make repeated changes until the original scene is lost.
8. Restore values and deliver two traceable records
Restore settings actually changed in this round, then check 岸40 or a previously usable card in the ordinary draft before passing recovery. Deliver actual diagnostic scope, manual reproduction card, both results and unperformed items with source and timing. Retain target, original and corrected drafts. No record is automatically sent and no support ticket is claimed. One normal result is a current baseline, not future reliability; one recurring issue does not implicate every device. A new version or host needs new conditions rather than an old diagnostic image substituted for a new event. The outcome is reviewable evidence, not a guessed implementation.
Related guides and sources
Field and host checks; Recovering one changed setting at a time.
Checked on 18 November 2026: Apple’s Finland lookup and China lookup both list Jianlai 1.0.5, requiring iOS / iPadOS 16.0 or later. The official store describes themes, backgrounds, fonts and multilingual input. Use controls actually present in the installed version; system editing and host processing are distinguished separately. These are repeatable instructions and paper expectations, not claims of completed device input, host compatibility or format-parser tests.
Method references: Official Apple keyboard-settings image; Apple custom-keyboard documentation.