[Bug]: java.lang.IndexOutOfBoundsException: Index: 2, Size: 1

[FaultyxDx]

What happened?

I just saved the java file to exit from IDE as auto code completion for java isn't working. When i clicked on exit button and clicked yes of exit dialog that's when this happened

What's the expected behavior?

idk , maybe it should closed my project. And also there is some bugs in auto code completion

What version of AndroidIDE you're using?

v2.5.0 (debug builds)

Relevant log output

AndroidIDE crash report
Manufacturer: OPPO
Device: CPH2095
ABI: arm64-v8a
SDK version: 31
App version: v2.5.0-beta (250)

 Stacktrace: 
java.lang.IndexOutOfBoundsException: Index: 2, Size: 1
	at java.util.ArrayList.get(ArrayList.java:437)
	at com.itsaky.androidide.services.log.MultiLogSenderHandler.close(Unknown Source:20)
	at com.itsaky.androidide.services.log.LogReceiverImpl.close(Unknown Source:2)
	at com.itsaky.androidide.services.log.LogReceiverService.onDestroy(Unknown Source:5)
	at android.app.ActivityThread.handleStopService(ActivityThread.java:4837)
 Caused by: java.lang.RuntimeException: Unable to stop service com.itsaky.androidide.services.log.LogReceiverService@65f2b2d: java.lang.IndexOutOfBoundsException: Index: 2, Size: 1
	at android.app.ActivityThread.handleStopService(ActivityThread.java:4857)
	at android.app.ActivityThread.access$2200(ActivityThread.java:254)
	at android.app.ActivityThread$H.handleMessage(ActivityThread.java:2227)
	at android.os.Handler.dispatchMessage(Handler.java:106)
	at android.os.Looper.loopOnce(Looper.java:233)
	at android.os.Looper.loop(Looper.java:344)
	at android.app.ActivityThread.main(ActivityThread.java:8212)
	at java.lang.reflect.Method.invoke(Native Method)
	at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:584)
	at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1034)

Duplicate issues

• This issue has not been reported yet.

Code of Conduct

• I agree to follow this project's Code of Conduct

[itsaky]

Dude, why would you create a duplicate of your own issue #1110?

The issue has been fixed. Update to v2.5.1-beta.