Custom Fonts in Rich Text WIdget do not display correctly in Mac app

[sgardoll]

Has your issue been reported?

• I have searched the existing issues and confirm it has not been reported.
• I give permission for members of the FlutterFlow team to access and test my project for the sole purpose of investigating this issue.

Current Behavior

1. Add Rich Text Widget
2. Create 3 TextSpan lines
3. Click A button next to any of the TextSpan lines
4. Change Font Family to a Custom Font
5. Font doesn't display

Expected Behavior

You would expect the font to display. It only shows in Run Mode (or Local Run)

Steps to Reproduce

Per current behavior

Reproducible from Blank

• The steps to reproduce above start from a blank project.

Bug Report Code (Required)

ITESh8/l5clgoekA+qnxLflAhQYgHGYlaJMvjuphcywaCJzrBu0MY8jRPxBVUumoaVNfMVKbrFsGpt7qi/H+UfoDNRCCGYR++JN2VALke2i5RpSsBqqsY3ZtN8RUf2qG1MONnCQlXclvSFoswF2MBO+WZD7DFOu/Zwh9f6PHaOI=

Context

Impossible to plan display text without being able to see the way it's going to display.

Visual documentation

Additional Info

No response

Environment

- FlutterFlow version: FlutterFlow v4.1.53 released May 21, 2024
Flutter version is 3.19.1
- Platform: 14.4.1 (23E224)
- Browser name and version: Version 125.0.6422.60 (Official Build) (arm64)
- Operating system and version affected: Mac OS

General

• I was collaborating with other users in the same project prior to data loss
• I navigated between different project views leading up to data loss
• The UI was running very slowly prior to data loss
• A crash or other bug occurred prior to data loss
• Data was not saved in a snapshot
• I was using flutterflow from multiple devices
• I was using flutterflow from multiple platforms (e.g. both web and MacOS Desktop app)

Relative to the time the changes were made, data was lost within

• 1 minute
• 1 hour
• 1 day
• 1 week

When following my steps to reproduce, data loss happens

• ~100% of the time
• ~50% of the time
• ~10% of the time
• ~1% of the time
• Very rarely or only encountered once

[msusviela]

I was able to reproduce the issue, I will send it to the ENG team so they can work on this!