[iOS] Tags not parsed on iOS below a certain string length

Open
#811 3 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 4 days

@hejsztynx is already working on this.

Since Oct 14, 2026.

  • #815 by @hejsztynx — open

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
42/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
ios, objective-c, react-native
Domain
mobile

Research direction

Start by reproducing with the snippet in the issue: render <p> strings of increasing length through the EnrichedText component on an iOS simulator and on Android to confirm the difference. The payload names no source files, so locate the iOS parsing path from the EnrichedText component. Done means <p> and other tags are parsed on iOS at every string length, matching Android, with the snippet rendering identically on both platforms.

Written by the indexing model from the issue text.

Description

bug

Describe the bug
Tags on iOS don't start being parsed until the string reaches a certain length, on Android this is not the case

To Reproduce
Run the code example below on iOS and Android

<View>
    {[...Array(10).keys()].map((_, i) =>
    {
        const html = `<p>${'a'.repeat(i)}</p>`;
        return (
            <View key={i}>
                <Text>Length: {html.length}</Text>
                <EnrichedText>{html}</EnrichedText>
            </View>
        )
    })}
</View>

Expected behavior

Tags should be parsed and not displayed within EnrichedText regardless of string length (as happens on android)

Device:

  • Device: iphone 16 pro simulator

  • OS: iOS 18.3.1

  • Version: 1.1.1

  • Device: iphone 6e

  • OS: iOS 15.8.5

  • Version: 1.1.1

Dominant language
C
Stars
1.4k
Forks
77
Avg merge
3d 14h
Merged PRs (30d)
24

Getting set up

  • No Dockerfile or Docker Compose file
  • Has a pull request template
  • No contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from software-mansion/react-native-enriched-html

All issues in software-mansion/react-native-enriched-html

Similar issues

More C issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.