-
Notifications
You must be signed in to change notification settings - Fork 27
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
English doesn't appear as a language in 1.0.1 #3
Comments
Yep, this is a known issue, however what language are you trying to set the app too ? |
Should have fixed in latest release : https://github.com/c22dev/Geranium/releases/latest |
Still doesnt let me set the language to english. Tried through the debug method and it changed the language to japanese |
This is extremely strange. The app is literally setting it to "en", which is English by default Can you screen record it to me ? Try uninstalling the app then reinstalling it. |
Uninstalled and reinstalled the latest version (1.0.2) trim.2AD8BE91-A519-43E1-94C1-00362E77ED11.MOV |
Try latest release (1.0.3) please |
English shows up now, but when selecting it, it sets it to japanese again (defsult does the same) |
Btw are you sure you've included english when compiling the app?? Just checked the .app with filza and there is no en.lproj |
Still having the same issue even tho i updated |
Okay... I'll try with British English. However, can you please try setting using the button ? |
Tbh i've been trying all the methods i can think of every time (button, debug, switching to user app and changing it thru settings) I'd love to help, but I have school tmrw and it's 2am in my country. Good Night |
It's 2am here too. Good night tho |
Try 1.0.4 when you can. |
Tried 1.0.4 and it's working now. Thanks for the quick responses |
I updated to the latest version and still have the language issue. Funny thing is that i only have english set up as a language on my device, but have different keyboard languages that aren't english. I tried to switch to user registration and enable it through settings but that led to the same result.
The text was updated successfully, but these errors were encountered: