Skip to content
This repository has been archived by the owner on Oct 18, 2024. It is now read-only.

Sometimes unable to build the project until you kill the IDE process #1911

Open
5 tasks done
RusJJ opened this issue Sep 22, 2024 · 3 comments
Open
5 tasks done

Sometimes unable to build the project until you kill the IDE process #1911

RusJJ opened this issue Sep 22, 2024 · 3 comments
Labels
bug Something isn't working

Comments

@RusJJ
Copy link

RusJJ commented Sep 22, 2024

Issue Checklist

  • I confirm that this issue is not a duplicate and hasn't been reported before.
  • I agree to follow the project's code of conduct.
  • I have checked and verified that I am using the latest version of AndroidIDE from GitHub or F-Droid.

Additional terms

  • I understand that providing incomplete or inaccurate information may result in the issue being closed.
  • I agree to provide all requested details promptly for a comprehensive bug report.

Issue explanation

Im using NDK. Sometimes IDE just stops building the project. You can try to switch to the another file and it may start building it. If it's not, you might think you can restart IDE! If you close it like a regular app by "swiping" it away in "Recent apps" menu, this will break IDE completely. It will start start showing you something about "Gradle Tools not started" if I'm not wrong.

To fix this, you just need to kill the process from the settings. It was happening on all latest versions that i got (Actions/Workflow or some latest releases, doesn't matter which one).

As a bonus: IDE doesn't save opened files... And it hurts.

Expected behavior

It should be able to build it. This is not a rare glitch at all.

Version name

Version : v2.7.1-beta (27102)
CI Build : true
Branch : dev
Commit : 8c48a0a
Variant : arm64-v8a (release)
Build type : OFFICIAL
F-Droid Build : false
F-Droid Version : null
F-Droid Version code : -1
SDK Version : 34
Supported ABIs : [arm64-v8a]
Manufacturer : OnePlus
Device : CPH2581

Download source

GitHub

Relevant log output

No response

@RusJJ RusJJ added the bug Something isn't working label Sep 22, 2024
@RusJJ
Copy link
Author

RusJJ commented Sep 22, 2024

If i can grab the log somehow related to this, please tell me

@RusJJ
Copy link
Author

RusJJ commented Sep 22, 2024

Not sure if it's NDK's problem but rarely it's also getting stuck on "Task :app:configureCMakeDebug[arm64-v8a]" or "Task :app:configureCMakeDebug[armeabi-v7a]"

UPD:

INFO [DefaultDispatcher-worker-7] ToolingServerRunner: Tooling API process exited with code : 137

22-09 15:08:22.771 INFO [DefaultDispatcher-worker-7] ToolingServerRunner: Destroying Tooling API process...

@RusJJ
Copy link
Author

RusJJ commented Sep 23, 2024

Restarted the phone and now it shows me this nonsense:

23-09 11:47:31.213  INFO [main] GradleBuildService:  Showing notification to user...
23-09 11:47:31.230  INFO [main] BaseEditorActivity:  Connected to Gradle build service
23-09 11:47:31.230  INFO [DefaultDispatcher-worker-7] ToolingServerRunner:  Starting tooling API server...
23-09 11:47:31.234 DEBUG [DefaultDispatcher-worker-7] BaseEditorActivity:  No variant selection information available. Default build variants will be selected.
23-09 11:47:31.234 DEBUG [DefaultDispatcher-worker-7] BaseEditorActivity:  Is project initialized: false
23-09 11:47:31.234 DEBUG [DefaultDispatcher-worker-7] BaseEditorActivity:  Sending init request to tooling server..
23-09 11:47:31.237 ERROR [DefaultDispatcher-worker-6] ToolingApiErrorStream:  Error: Invalid or corrupt jarfile /data/user/0/com.itsaky.androidide/files/home/.androidide/tooling-api/tooling-api-all.jar
23-09 11:47:31.238  INFO [DefaultDispatcher-worker-3] ToolingServerRunner:  Tooling API process exited with code : 1
23-09 11:47:31.238  INFO [DefaultDispatcher-worker-3] ToolingServerRunner:  Destroying Tooling API process...

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant