Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Create documentation on how to update JDK and Android SDK configurations
See original GitHub issueI in the initial setup didn’t give the correct JDK path, I tried setting the correct path in env with JAVA_HOME and in twa manifest via jdkPath. Both of the first guesses failed.
I had to dig in source code, I found gradlew ask to set the path in JAVA_HOME while the CLI updates the env JAVA_HOME from the llama config. So any env path setting is futile.
This can be included in README or can change the default behavior.
Issue Analytics
- State:
- Created 3 years ago
- Reactions:2
- Comments:9
Top Results From Across the Web
Configure Android Studio - Android Developers
In the left pane, navigate to Build, Execution, Deployment > Build Tools > Gradle. Under Gradle JDK, choose the Embedded JDK option. Click...
Read more >Update the IDE and SDK Tools - Android Developers
Click the SDK Update Sites tab. · Click Add at the bottom of the window. · Enter the name and URL of the...
Read more >Set up the Android 11 SDK
Click Tools > SDK Manager. · In the SDK Platforms tab, select Android 11. · In the SDK Tools tab, select Android SDK...
Read more >Set up the Android 13 SDK
Click Tools > SDK Manager. · In the SDK Platforms tab, select Android Tiramisu Preview. · In the SDK Tools tab, select Android...
Read more >Set up the Android 12 SDK
Install the SDK · Click Tools > SDK Manager. · In the SDK Platforms tab, select Android 12. · In the SDK Tools...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Had the same issue. If somebody has to reconfigure there PATHS the file is located at:
${USER_HOME}/.llama-pack/llama-pack-config.jsonCreated #133 . Let me know if that information is enough.