You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
iOS "Copy as Markdown" inserts "****" after the first character of bold text #29012
In the iOS app, selecting assistant text that contains a bold lead-in such as **What** and choosing Copy as Markdown puts **W****hat** on the clipboard. The bold span is split after its first character, every time.
Diagnosis
"Copy as Markdown" comes from the vendored react-native-enriched-markdown fork (apps/mobile/deps/react-native-enriched-markdown-1.2.0-t3.16-*.tgz). extractMarkdownFromAttributedString (ios/utils/MarkdownExtractor.m) wraps each attribute run in its own delimiters.
Runs also split on attributes with no inline meaning: ListItemRenderer.m anchors ListItemMarkerStartAttribute on the first grapheme of every list item, so - **What**: … arrives as W + hat and becomes **W****hat**. Links break the same way ([d](url)[ocs](url)).
Fix: pingdotgg/enriched-markdown#12 extends the previous span when the next run has identical inline delimiters. T3 Code then needs the vendored tgz bumped.
Steps to reproduce
In the iOS app, open a thread where an assistant reply has a bullet starting with bold text, e.g. - **What**: something.
Long-press to select text that includes the bold word.
Choose Copy as Markdown and paste anywhere.
Expected **What**. Actual **W****hat**.
Version
iOS app 2.2.0 (reported by the user). The extractor is unchanged on pingdotgg/enriched-markdown main (678a5a99) and t3code main (05c0ed7).
Environment
iOS app 2.2.0
react-native-enriched-markdown 1.2.0-t3.16
Evidence
Shipped MarkdownExtractor.m, compiled forthe iOS simulatorin a standalone harness:
FAIL split bold: got [**W****hat**] want [**What**]
FAIL list item bold: got [- **W****hat**: next] want [- **What**: next]
FAIL split link: got [see [d](https://x.y)[ocs](https://x.y) now] want [see [docs](https://x.y) now]
With the patch from pingdotgg/enriched-markdown#12, all cases pass.
Activity
juliusmarminge commentedon Nov 9, 2026
Fixed by #32180, which includes the extractor fix in 986a4f56a8. Thanks for the detailed report and fix!