3577
Official Telegram group of AndroidIDE to discuss issues, requests and suggestions. We use GitHub to manage requests, features and suggestions. GitHub: https://github.com/AndroidIDEOfficial/AndroidIDE Website: https://androidide.com/
Already did it in video and also did uninstall install
Читать полностью…
⭐ @Burnt-Circuit starred AndroidIDEOfficial/terminal-packages!
Читать полностью…
User Ad has 1/2 warnings; be careful!
Reason:
use English
Can i run this project on AndroidIDE. it says Application cannot be employed, no application module was found in the project
Читать полностью…
Para arreglarlo, revisé el archivo CMakeLists.txt para asegurarme de que esté bien escrito y que tenga las líneas básicas como cmake_minimum_required, project(), add_library() y target_link_libraries().
> También verifiqué que la versión de CMake que estoy usando (en mi caso era la 3.22.1) sea compatible con el proyecto. A veces conviene cambiar a la 3.18.1 porque funciona mejor con Android.
> Otro detalle importante es la ubicación del proyecto: si lo estás compilando desde la carpeta de almacenamiento del teléfono (como /storage/emulated/0/), puede fallar por permisos. Conviene mover el proyecto a una carpeta interna, como /data/user/0/..., o usar Termux con Linux para compilar sin trabas.
> Finalmente, también revisé que el NDK esté bien instalado y configurado en el archivo local.properties, con la ruta correcta.
https://github.com/itsaky/AndroidIDE/releases/tag/v2.7.1
Читать полностью…
Can anyone please give me stable version of Android Ide
Читать полностью…
Another one bites the dust...!
Banned 七分糖去冰.
⭐ @AlanTse1314 starred AndroidIDEOfficial/androidide-tools!
Читать полностью…
List of notes in AndroidIDE Discussions:
- cpaapt
- customgradle
- decreasexmx
- docs
- gradleplugin
- init_script_issue
- manualsetup
- reactnative
- setupcmdline
- setupndk
- setuproom
- specbuildtools
- upgradle
- usedev
- usepluginsblock
You can retrieve these notes by using /get notename, or #notename
I'm install androidide in my phone, but when i open it always force close
Читать полностью…
What's the issue I never face this issue it was working perfectly fine till yesterday anyone can you help
Читать полностью…
I have never faced this problem before. This is happening since this morning.
Читать полностью…
⭐ @Burnt-Circuit starred AndroidIDEOfficial/terminal-packages!
Читать полностью…
Let's send an e-mail to Google and ask them to develop an Android application. If we all want, Google can accept it. Let's make an Android IDE for Android phones.
Читать полностью…
⭐ @elocallurkk starred AndroidIDEOfficial/AndroidIDE!
Читать полностью…
https://github.com/itsaky/AndroidIDE/releases/tag/v2.7.1
Читать полностью…
Hi there , is anyone online , may I have stable version? Every recent beta is crashing
Читать полностью…
just sync the project and then restart the application
Читать полностью…
it just gives an error and says that no application modules were found in the project
btw a week ago everything worked fine without errors
is this important? which country should i choose then?
Читать полностью…
How i can fix this?
Execution failed for task ':module:configureCMakeRelWithDebInfo[arm64-v8a]'.
> [CXX1429] error when building with cmake using /storage/emulated/0/AndroidIDEProjects/Zygisk-Il2CppDumper/module/src/main/cpp/CMakeLists.txt: C++ build system [configure] failed while executing:
/data/user/0/com.itsaky.androidide/files/home/android-sdk/cmake/3.22.1/bin/cmake \
Always download APKs from the "dev" branch.
Читать полностью…
2.6.1 is fine not force close but 2.7.0+ is close automatic
Читать полностью…
1. Start of Gradle Daemon
A daemon process is started to speed up builds. The daemon log is saved in an internal system path.
2. Dependency Downloading
Gradle tries to download many dependencies from remote repositories (such as Maven Central, Google, and a snapshot repository from Sonatype).
3. "Resource missing" Errors
Many dependencies are not found in the specified repositories. This may be due to:
Unstable or snapshot versions that are no longer available.
Misconfigured or inaccessible repositories.
Obsolete or incorrectly defined dependencies in the build.gradle file.
4. Very Detailed Logging Level (debug)
The log shows a lot of technical information (debug level), which can make it hard to read and result in very large logs.
Recommendations for Improvement and Fixes
1. Adjust Gradle Logging Level
To avoid so much unnecessary information, you can configure a less detailed log level:
In the gradle.properties file, add or modify this line:
org.gradle.logging.level=info
Or when running Gradle, use:
./gradlew build --info
or for less output:
./gradlew build --quiet
This will make the logs more readable and shorter.
2. Review and Correct Dependencies and Repositories
Check that your build.gradle file has the repositories correctly configured:
repositories {
google()
mavenCentral()
// Avoid using snapshot repositories unless necessary
}
Replace snapshot or alpha versions with stable versions if possible. For example, avoid using versions like 7.0.0-alpha03 or 2.7.1-beta-f5231daa5-SNAPSHOT unless you really need those versions.
If you're using snapshot versions, make sure the remote repository is active and accessible.
3. Clean Old Daemon Logs
Gradle daemon logs can take up space. You can delete them manually from the path shown in the log:
/data/data/com.itsaky.androidide/files/home/.gradle/daemon/<version>/
Delete files like daemon-*.out.log that you no longer need.
4. Check Internet Connection and Repository Access
Make sure the device or environment where you're building has a stable internet connection and can access the Maven and Google repositories.
Summary
Adjust the log level to make it less verbose.
Use stable versions of dependencies and official repositories.
Clean up old logs to free space.
Check connection and repository configuration.