Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug] [Code: ATWxYRE] Not working after removing a language #101

Closed
guidev opened this issue Apr 29, 2023 · 3 comments
Closed

[Bug] [Code: ATWxYRE] Not working after removing a language #101

guidev opened this issue Apr 29, 2023 · 3 comments

Comments

@guidev
Copy link

guidev commented Apr 29, 2023

Steps to Reproduce:

I've removed a couple of localization language from project -> info -> localisations (see attachment)

After that, I cannot use Remafox as It errors out with:

A file was expected but did not exist at: /path/to/project/sv.lproj/Localizable.strings

Screenshot 2023-04-29 at 02 49 03

Expected Behavior:

Current Behavior:

Environment

ATWxYRE

Show environment details
  • App Version: 1.5.0 (Build 613)
  • System Version: 13.3.1 (Build 22E261)
  • System CPU: Intel(R) Core(TM) i9-9900K CPU @ 3.60GHz
  • Tier: Free
@Jeehut
Copy link
Member

Jeehut commented Apr 29, 2023

@guidev Thank you for reporting this issue. I'll take a look at it tomorrow and do my best to provide a fix as soon as possible.

@Jeehut
Copy link
Member

Jeehut commented Apr 29, 2023

I investigated and I think I found the issue, the Add Translation Window isn't automatically rescanning the Strings files on open to have up-to-date information about which files exist and which don't. I will fix that with a hotfix release 1.5.1 ASAP.

In the meantime, pressing the "Rescan Strings(dict) files" button in the Add Translation window should update the paths manually after removing some languages which should make this error disappear:
Bildschirmfoto 2023-04-29 um 12 45 46

I hope this helps!

@Jeehut
Copy link
Member

Jeehut commented Apr 30, 2023

@guidev I just made a change that should fix this issue and I'm uploading a new build with the fix right away. This issue should be resolved in version 1.5.1 which should be up on the App Store very soon.

Thanks again for reporting this issue! 👍

@Jeehut Jeehut closed this as completed Apr 30, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants