search

PocketByte / LocoLaser

Localization tool to import localized strings from external source to your project.
Apache License 2.0
31 stars 1 forks source link

Java 16 not supported #14

Closed ptunde closed 3 years ago

ptunde commented 3 years ago

Hi,

I was using this tool for a while in a native iOS app (version 1.2.4) and today it stopped getting my localisation files. I'm getting this in my Terminal window.

Artifact ru.pocketbyte.locolaser:core:2.0.0 already downloaded
Artifact ru.pocketbyte.locolaser:resource-mobile:2.0.0 already downloaded
Artifact ru.pocketbyte.locolaser:resource-googlesheet:2.0.0 already downloaded
ERROR: java.lang.RuntimeException: Failed to read list of execution jars
    at ru.pocketbyte.locolaser.ConfigParserFactory.getJarUrls(ConfigParserFactory.kt:67)
    at ru.pocketbyte.locolaser.ConfigParserFactory.getFromClassLoader(ConfigParserFactory.kt:26)
    at ru.pocketbyte.locolaser.ConfigParserFactory.get(ConfigParserFactory.kt:19)
    at ru.pocketbyte.locolaser.Main.main(Main.kt:20)
Caused by: java.lang.NoSuchFieldException: ucp
    at java.base/java.lang.Class.getDeclaredField(Class.java:2549)
    at ru.pocketbyte.locolaser.ConfigParserFactory.getJarUrls(ConfigParserFactory.kt:58)
    ... 3 more
Saving session...
...copying shared history...
...saving history...truncating history files...
...completed.

[Process completed]

The same error persisted after migrating to version 2.0.0. Also I'm getting the same error when run the localize.command from the iOS sample app.

Any help would be much appreciated.

KamiSempai commented 3 years ago

I found that LocoLaser doesn't working on Java 16 and above. For now try to use JDK 15 or lower. I will fix it soon.

ptunde commented 3 years ago

Thank you for the update. I will downgrade to Java 15.

KamiSempai commented 3 years ago

Fixed in version 2.1.0. Please note, that new version uploaded only in Maven Central. JCenter no more available.

ptunde commented 3 years ago

Sorry, but something is still wrong, after I run the .localize.command from Terminal it redirects me to the browser, where is an Authorisation error (401: invalid_client), however I'm logged into my account.

Screenshoots attached below Screenshot 2021-05-03 at 15 01 26 Screenshot 2021-05-03 at 15 06 28

KamiSempai commented 3 years ago

@ptunde this is a known issue #8 .See comments for correct solution.

ptunde commented 3 years ago

Oh right, thanks for the help.