Troubleshooting LINE Capture Feature
LINE's UI changes frequently across versions, platforms (iOS/Android), and locales (e.g., "Capture" in English vs "บันทึกภาพ" in Thai). Exact button positions, menu wording, and feature availability cannot be verified by Claude in real time and may not match what the user sees. This skill provides a general troubleshooting framework, not a pixel-accurate walkthrough. Always tell the user to compare against what's actually on their screen and adjust accordingly, and point them to LINE's official help center for version-specific screenshots when precision matters.
When a user asks "how do I capture a long LINE chat," respond with the general pattern, flagged as approximate:
- Long-press a message in the conversation → look for a Capture / บันทึกภาพ / long-press menu option
- If found: select it, then drag the top/bottom handles to cover the desired message range, then tap the save/checkmark icon
- If not found: walk through the diagnostic checklist below instead of guessing further
Always add: "Menu labels and icon positions vary by app version and language — if these exact words don't appear, tell me what you do see and I'll help interpret it."
Progress:
- Step 1: Confirm platform (iOS/Android) and rough app version if known
- Step 2: Confirm chat type (1-on-1, group, official account)
- Step 3: Ask what appears on long-press (not what should appear)
- Step 4: Match observed menu to known patterns
- Step 5: Give conditional next steps based on what's actually visible
- Step 6: Provide fallback (OS-level screenshot + stitching) if the feature is unavailable
Step 3-4: Interpret what the user sees
Instead of asserting fixed UI facts, ask and interpret:
| User reports seeing... | Likely meaning | Suggested action |
|---|---|---|
| Copy, Reply, Forward, Delete only — no capture-like option | Feature missing (old version, unsupported chat type, or regional variant) | Suggest updating LINE; if still missing, go to fallback |
| An option with a camera/frame icon, regardless of exact label | This is almost certainly the capture feature | Guide them to tap it, then describe the drag-handle pattern |
| A highlighted/dimmed region with two draggable handles after tapping something | They're already in capture-selection mode | Explain dragging handles to extend range, then locate the confirm icon (commonly top-right or a checkmark) |
| Nothing happens on long-press | Might be tapping timestamp/empty space instead of the bubble | Ask them to try long-pressing directly on the text/sticker bubble |
Step 6: Fallback when Capture is unavailable or unreliable
If the user's version/chat type doesn't support it, or troubleshooting stalls, give the guaranteed-to-work alternative:
- Take normal OS screenshots (Volume+Power on Android, Volume Up+Side button on iOS) of each screen of the conversation, scrolling between each
- Use a stitching tool (e.g., a scrolling-screenshot app, or free online image-stitching tool) to combine them into one long image
- This works regardless of LINE version, locale, or chat type
Example 1: Input: "I long-pressed a message in LINE and only see Copy, Forward, Delete — no Capture option." Output: "That suggests either your LINE version doesn't include this feature yet, or it's not supported in this chat type (e.g., some official account or bot chats restrict it). Try: (1) update LINE from your app store and retry, (2) test in a different 1-on-1 chat to isolate whether it's chat-specific. If it's still missing after that, use the fallback: take regular screenshots scrolling through the conversation, then stitch them with an image-merging app or tool."
Example 2: Input: "After long-pressing I see a dimmed area with two handles at the top and bottom of the screen — what now?" Output: "You're in selection mode. Drag the bottom handle down to include later messages, or the top handle up to include earlier ones — go slowly near the screen edges since it can auto-scroll fast. Once the highlighted area covers exactly the messages you want, look for a checkmark or save icon (often top-right on iOS, in a bottom toolbar on Android) and tap it to export as an image."
Example 3: Input: "Capture isn't giving me an option to select more than about 20 messages." Output: "That's a known length limit that varies by device/OS. Save what's selected as one image, then start a new Capture from the next message onward for a second image — you'll end up with two (or more) images covering the full range instead of one."
- Never assert an exact icon position or label as fact — phrase it as "commonly," "often," or "look for something like"
- Always ask what the user actually sees before giving the next instruction, rather than reciting a fixed script
- Offer the OS-screenshot-and-stitch fallback early if the user seems stuck, rather than looping on guesses about a specific UI
- Point to LINE's official in-app help or help.line.me for authoritative, version-correct visuals when precision matters
- Treat this as live troubleshooting dialogue, not a one-shot tutorial dump
- Stating UI details as guaranteed facts: Labels like "Capture" vs "บันทึกภาพ", icon positions, and even feature existence vary by version/platform/locale — hedge accordingly
- Ignoring chat-type restrictions: Group chats, official accounts, and certain message types (calls, some stickers) may not support this feature — check this before assuming user error
- Skipping the fallback: If troubleshooting stalls after 2-3 exchanges, move to the OS-screenshot-and-stitch method rather than continuing to guess at menu wording
- Assuming current knowledge is up to date: LINE updates its UI regularly; explicitly tell users this guidance may be outdated and to verify against their own screen