NDK missing message in gradle should indicate expected version
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 58/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Active
- Domain
- build-system, mobile
Research direction
The error occurs while Gradle configures the :file_operations project, but the issue does not name the build file or test involved. Start by tracing that module's NDK configuration and find where the “NDK is not installed” message is produced. Done when the error identifies the expected NDK version; no test or verification command is specified.
Written by the indexing model from the issue text.
Description
The NDK not installed error message does not indicate what version is expected, but it will accept a single version. Error message:
A problem occurred configuring project ':file_operations'.
> NDK is not installed
* Try:
> Run with --stacktrace option to get the stack trace.
> Run with --info or --debug option to get more log output.
> Run with --scan to get full insights.
> Get more help at https://help.gradle.org.
Deprecated Gradle features were used in this build, making it incompatible with Gradle 9.0.
You can use '--warning-mode all' to show the individual deprecation warnings and determine if they come from your own scripts or plugins.
For more on this, please refer to https://docs.gradle.org/8.14.5/userguide/command_line_interface.html#sec:command_line_warnings in the Gradle documentation.
- Dominant language
- Kotlin
- Stars
- 6.4k
- Forks
- 1.7k
- Avg merge
- 3d 17h
- Merged PRs (30d)
- 2
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from TeamAmaze/AmazeFileManager
-
Copying or moving a folder into itself fails but leaves an empty subfolder behindPossibly taken @carrerasdarren-cell claimed this 5 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
TeamAmaze/AmazeFileManager#4731 ·
Maintainers usually reply within 1 day
-
Area-UIUX Issue-Bug
Difficulty 1/5 Under an hour Newbie friendliness 86/100
TeamAmaze/AmazeFileManager#4723 · 4 comments · 1 reaction ·
Maintainers usually reply within 1 day
-
Area-FileOperations Issue-Bug
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
TeamAmaze/AmazeFileManager#4131 · 1 reaction ·
Maintainers usually reply within 1 day
-
Difficulty 3/5 1-2 days Newbie friendliness 76/100
TeamAmaze/AmazeFileManager#4754 ·
Maintainers usually reply within 1 day
-
Difficulty 3/5 1-2 days Newbie friendliness 75/100
TeamAmaze/AmazeFileManager#4753 · 1 comment ·
Maintainers usually reply within 1 day
All issues in TeamAmaze/AmazeFileManager
Similar issues
-
[Request] 李跳跳Openrequest-adaption
Difficulty 2/5 Under an hour Newbie friendliness 78/100
BetterAndroid/android-notification-icon-project#799 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
ProdigyV21/ARVIO#832 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
Maintainers usually reply within 1 day
-
SIGSEGV in symex on __builtin_constant_p of a void expressionPossibly taken A pull request linked to this issue is open or already merged. Openbug goto-symex
Difficulty 2/5 1-3 hours Newbie friendliness 83/100
Maintainers usually reply within 1 day