BalasoLocalizationResources/zh.lproj No such file or directory - Got this error on xcode build

[manelizzard]

Hello,

Can you please let me know which languages have you localized through the plugin? We've seen some issues with bealrusan and related languages.

Thanks

[Madaconda]

I'm having the same issue. I think it's to do with the build path - in XCode I see:

error: /Volumes/Users/Username/Documents/Project/Builds/iOS/C:/Users/Username/Documents/Project/Builds/iOS/BalasoLocalizationResources/zh.lproj: No such file or directory

where the file is at: /Volumes/Users/Username/Documents/Project/Builds/iOS/BalasoLocalizationResources/zh.lproj

[izainfarooqi]

Please let me know how to solve this issue, I m trying from days

On Sat, Jun 5, 2021, 4:59 AM Adam Bowles @.***> wrote:

I'm having the same issue. I think it's to do with the build path - in XCode I see:

error: /Volumes/Users/Username/Documents/Project/Builds/iOS/C:/Users/Username/Documents/Project/Builds/iOS/BalasoLocalizationResources/zh.lproj: No such file or directory

where the file is at:

/Volumes/Users/Username/Documents/Project/Builds/iOS/BalasoLocalizationResources/zh.lproj

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/Balaso-Software/app-tracking-transparency-for-unity/issues/31#issuecomment-855142133, or unsubscribe https://github.com/notifications/unsubscribe-auth/AUHZGYTEQKMJNIVPMADPP5LTRFSG5ANCNFSM45T5IW3A .

[robyBorelli]

Same issue. I found a work around: since the problem is due to absolute paths, you can just search in all files of your xcode project folder and look for all the occourences of the buggy absolute path. Once you have found all occourences just sobstitute all absolute paths with relatives ones.

You can do as follows:

• Save this code to a new file find.sh in your xcode project folder

FILES=`find * -type f`

for i in $FILES 
do
    v=`grep $1 $i`
    if [ "$v" = "" ]
    then
        v=""
    else
        echo "$i"
        echo "$v"
        echo "==================================="
        v=""
    fi
done

• open terminal and switch to bash

• Give the execution permission to the file. chmod 777 find.sh

• run ./find.sh <pattern>

  • for example responding to @Madaconda, you should do ./find.sh "C:/Users/Username/Documents/Project/Builds/iOS/"

• The script shows the files in which the pattern occours.

• Open them with a text editor and replace all absolute baths to relative paths.

  • So for example replace "C:/Users/Username/Documents/Project/Builds/iOS/" to ""

[robyBorelli]

Or another workaround is to not move your xcode project folder once unity has compiled so xcode will find all at the right places. But I see that your path begins with C so I think you have unity on windows so you can't not move the folder once unity has compiled it.

[EternalStudio]

Even easier fix than this is to find the messed up files in the XCode workspace (they're red), delete those and re-reference them.