Titanium JIRA Archive
Appcelerator Community (AC)

[AC-6362] LiveView breaks i18n string translations when reloads the app

GitHub Issuen/a
TypeBug
Priorityn/a
StatusOpen
ResolutionUnresolved
Affected Version/sAppcelerator Studio 4.5.0
Fix Version/sn/a
ComponentsAlloy, Titanium SDK & CLI
Labelsliveview
ReporterAndrea Vitale
AssigneeShak Hossain
Created2019-09-09T10:29:28.000+0000
Updated2019-10-08T06:11:32.000+0000

Description

I have an issue while running an app with LiveView enabled. In details, when the app reloads (after a file has been modified) the i18n translation function seems to be broken, i.e., instead of seeing the actual translation of the string, I see the translation key. E.g.: A string represented by L('key'), whose value is 'test' defined as follow:
<string name="my_string_key">Value</string>
- Expected behavior: 'Value' - Actual behavior: 'my_string_key'

Attachments

FileDateSize
info.txt2019-09-12T12:59:23.000+000017461

Comments

  1. Rene Pot 2019-09-09

    I tried this out but can't seem to reproduce. For me, the value always remains correct no matter how often I change things, even when changing keys the translations update accordingly. Can you share a reproducible project? My setup:
       Titanium SDK 8.0.0.GA and 8.1.0.GA
       CLI  7.1.0
       MacOS 10.14.6 
       Node 10.16.2
       
  2. Rene Pot 2019-09-12

    Unfortunately, there still hasn't been a reproducible situation here. So we'll need to know more before we can implement a fix. It must be something regarding your local machine configuration that causes a problem like this.
  3. Andrea Vitale 2019-09-12

    As I said to you on Slack I can't share a project my two projects with you. I know that this can't help you but the weird thing is that it also happens an at least other 3 users as you can see in our thread on Slack. If it is an issue with my configuration, I attach here what I get from _appc info_. [^info.txt]
  4. Rodolfo Perottoni 2019-10-08

    I have the same behavior on multiple apps that I maintain. There's no test case as it is pretty random - might happen after 2-3 reloads, then fixes itself, then breaks again, rinse, repeat.

JSON Source