Search Unity

Question Localization Addressable assets not loaded

Discussion in 'Localization Tools' started by jyjy3, Jan 18, 2023.

  1. jyjy3

    jyjy3

    Joined:
    Jul 6, 2022
    Posts:
    10
    I followed Localization manual's quick start guide and tried to get string table addressable assets from AWS S3. I changed some entries at string table, updated addressables build, uploaded it to S3 and expected changed texts to be updated but only in the editor I can see updated texts not in the built program(both exe at windows and apk at android). Actually even before I upload addressable assets to S3 Localized texts are seen, so I think my app loads string table inside itself not from remote.

    Did I miss any step for using Addressable assets at Localization?
     
    jyjy3, Jan 18, 2023
    #1

  2. karl_jones

    karl_jones

    Unity Technologies

    Joined:
    May 5, 2015
    Posts:
    8,276
    karl_jones, Jan 18, 2023
    #2

  3. jyjy3

    jyjy3

    Joined:
    Jul 6, 2022
    Posts:
    10
    Thanks a lot for your reply! I've been reading the quick start guide again and found that I missed Localization Scene Controls step. However in my editor the string table icon at Scene Controls window doesn't look like addressable asset. Does this mean my Addressable assets setting is wrong somewhere?
     
    jyjy3, Jan 18, 2023
    #3

  4. karl_jones

    karl_jones

    Unity Technologies

    Joined:
    May 5, 2015
    Posts:
    8,276
    It seems unlikely that the issue you are experiencing is related to the icons changing. The Scene Controls window is used for content editing and preview, and would not affect the functionality of the player. Have you checked the log file for any error messages that might provide more information on the problem?
     
    karl_jones, Jan 18, 2023
    #4

  5. jyjy3

    jyjy3

    Joined:
    Jul 6, 2022
    Posts:
    10
    I tried playing my app without uploading addressable assets at remote. Editor player showed error log saying cannot find~~ at my AWS S3, and built exe file showed localized texts which I wrote before build. I checked every update string is Editor and Runtime. Could you let me know where I can check any more setting or log file?
     
    jyjy3, Jan 18, 2023
    #5

  6. karl_jones

    karl_jones

    Unity Technologies

    Joined:
    May 5, 2015
    Posts:
    8,276
    Try changing the addressable play mode to use existing build. Does it still work in the editor?
    https://docs.unity3d.com/Packages/com.unity.addressables@1.19/manual/Groups.html#play-mode-scripts
     
    karl_jones, Jan 18, 2023
    #6

  7. jyjy3

    jyjy3

    Joined:
    Jul 6, 2022
    Posts:
    10
    Play mode script is set use existing build, I first built addressables using default build script, built windows target exe file, changed string table entry and built addressables using Update a previous build. In this case running at editor showed updated texts and emited several UnityEditor.Localization.UI.LocalizedStringPropertyDrawer errors. But running exe file did not show updated texts so I am assuming my exe file loads localized texts inside itself.
     
    jyjy3, Jan 18, 2023
    #7

  8. karl_jones

    karl_jones

    Unity Technologies

    Joined:
    May 5, 2015
    Posts:
    8,276
    karl_jones, Jan 18, 2023
    #8

  9. jyjy3

    jyjy3

    Joined:
    Jul 6, 2022
    Posts:
    10
    No errors about remote addressables at editor, and no errors at player.log file about my exe file found.
     
    jyjy3, Jan 18, 2023
    #9

  10. jyjy3

    jyjy3

    Joined:
    Jul 6, 2022
    Posts:
    10
    Sorry I found something that my device's default locale name is not match and its parent locale. I will fix the locale name and try again. Thanks a lot for the kind guidelines.
     
    jyjy3, Jan 18, 2023
    #10

  11. jyjy3

    jyjy3

    Joined:
    Jul 6, 2022
    Posts:
    10
    I am still having same issue and found that it is because of the CRC Mismatch problem.
    The error starts with this sentence.
    Error while downloading Asset Bundle: CRC Mismatch.
    My Unity editor version is 2021.3.1f1, Localization version 1.0.5 and addressable version 1.19.19.
    Are there any know issue or any setting change I can make and have a test?
     
    jyjy3, Jan 19, 2023
    #11

  12. karl_jones

    karl_jones

    Unity Technologies

    Joined:
    May 5, 2015
    Posts:
    8,276
    Try updating to localization 1.4.2. Then rebuild the addressables. You may need to manually edit the manifest.json file in the Packages folder to upgrade if it's not showing in the package manager.
     
    karl_jones, Jan 19, 2023
    #12

  13. jyjy3

    jyjy3

    Joined:
    Jul 6, 2022
    Posts:
    10
    When I tried to use version 1.4.2, my string table and keys in there didn't show up in the inspector. So I had to click Add Table Entry button and type in entries. How can I make the Localize string event component find existing table and key?
     
    jyjy3, Jan 19, 2023
    #13

  14. karl_jones

    karl_jones

    Unity Technologies

    Joined:
    May 5, 2015
    Posts:
    8,276
    That's a bug with the search system. You need to start typing and they will start to appear. We have a fix in 1.4.3 which will be out soon.
     
    karl_jones, Jan 19, 2023
    #14

  15. jyjy3

    jyjy3

    Joined:
    Jul 6, 2022
    Posts:
    10
    I tried to use addressables updated at both Localization version 1.4.3, 1.4.2 and seems like same issue still exists. Can I just use my string table addressable assets option 'Asset Bundle CRC' disabled?
     
    Last edited: Jan 25, 2023
    jyjy3, Jan 25, 2023
    #15

  16. karl_jones

    karl_jones

    Unity Technologies

    Joined:
    May 5, 2015
    Posts:
    8,276
    Could you please file a bug report https://unity.com/releases/editor/qa/bug-reporting
    Im not familiar with the CRC option so can't really say if it would help.
     
    karl_jones, Jan 25, 2023
    #16

  17. SRao407

    SRao407

    Joined:
    Feb 14, 2023
    Posts:
    1
    ISSUE:
    Faced issue with Localization Addressable load.
    Unity: 2022.3.6f1
    Localization: 1.4.4
    Addressable: 1.21.12
    SOLUTION:
    Calling Addressables initialise manually before Localisation Init call fixed the issue.
     
    SRao407, Aug 14, 2023
    #17
    mhctseu likes this.

  18. karl_jones

    karl_jones

    Unity Technologies

    Joined:
    May 5, 2015
    Posts:
    8,276
    karl_jones, Aug 14, 2023
    #18

  19. mhctseu

    mhctseu

    Joined:
    Jan 21, 2020
    Posts:
    2
    This solution works for me, thank you!

    My environment:
    Unity: 2020.3.48f1
    Localization: 1.4.4
    Addressable: 1.21.15
    CCD Management: 2.2.2
     
    mhctseu, Aug 29, 2023
    #19
    karl_jones likes this.