Theme widgets (with unbound text) internationalization codes are the same for different texts

[TeferiHero]

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

I you create a theme widget with an unbound text. After exiting and reentering project, if I add a few instances of this theme widget with different text in editor, they have the same internationalization code (show the same text in run mode and built application).

Expected Behavior

If the text is unbound, the internationalization codes, and therefore text should be different.

Steps to Reproduce

1. Create a new project
2. Add languages
3. Create theme widget with an unbound text (e.g. text or button, click on the green chain)
4. Exit the project (to the page where you can see all your projects)
5. Go back to the project
6. Add two theme widget instances to page
7. Change one of the texts inside the theme widgets
8. Click on View Code and and observe that the internationalization codes are the same, but preview texts are different.
   OR Enter Run Mode, see the texts are the same, though they were different in the editor.

Reproducible from Blank

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

Bug Report Code (Required)

IT4Kz8r134t2pbwD1arqd/lanSQUKUQ1bYIoltVTawIaJZSvG7l3WvfObhJUOcOiS3xheEyGnn8X/Mr9v879GO0qJSWuRqo7yqgBVT3yeFy6aLXSPr63b0ZSQOlgCki5yqbYnBJTPrNvSXga7DqmG97ISjXsNbKwPnojBeaeXdeK2SrDX1iXc2URm05KZDPz

Context

I'm creating a multilingual app, and I want to be able to use theme widgets with different texts.

Visual documentation

Additional Info

No response

Environment

- FlutterFlow version: v3.1 released September 17, 2023
- Platform:
- Browser name and version:
- Operating system and version affected:

[wenkaifan0720]

Hi @TeferiHero. Thank you for the detailed report. I can reproduce this issue on my end. Working on a fix right now.

[wenkaifan0720]

This should be fixed in our next update!