kotlin android.os.Handler removeCallbacks Runnable [376498180]

Fixed

Bug

Status Update

No update yet.

Description

al...@gmail.com

created issue #1

Oct 31, 2024 06:24AM

kotlin always let ()->Unit as Runnable. But android Handler cannot removeCallbacks. Ex:

    private val connectRunnable:()->Unit = {
        //xxxx
    }

    fun test() {
        handler.postDelayed(connectRunnable, 100)
        handler.removeCallbacks(connectRunnable)
    }

Above code will be compiled into:

   public final void test() {
      Function0 var1 = this.connectRunnable;
      this.handler.postDelayed(A::test$lambda$0, 100L);
      var1 = this.connectRunnable;
      this.handler.removeCallbacks(A::test$lambda$1); //diff from postDelay
   }

   private static final void test$lambda$0(Function0 $tmp0) {
      Intrinsics.checkNotNullParameter($tmp0, "$tmp0");
      $tmp0.invoke();
   }

   private static final void test$lambda$1(Function0 $tmp0) {
      Intrinsics.checkNotNullParameter($tmp0, "$tmp0");
      $tmp0.invoke();
   }

The ()->Unit function has be wrapped by diff lambda, it's not same one. So, the android Handler can't removeCallback.

We have to replace with Runnable statement.

Could you please add some warning message just like SharedPreferences' commit() to removeCallback when using kotlin?

deleted

Restricted

0 B

deleted

Restricted

0 B

Comments

gg...@google.com <gg...@google.com> #2Oct 31, 2024 11:23PM

Assigned to vi...@google.com.

Thank you for reporting this issue. For us to further investigate this issue, please provide the following additional information:

Which Android build are you using? (e.g. TQ3A.230705.001.A1)

Please provide a sample project or apk to reproduce the issue. Also mention the steps to be followed for reproducing the issue with the given sample project or apk.

Android bug report (to be captured after reproducing the issue)
For steps to capture a bug report, please refer: https://developer.android.com/studio/debug/bug-report#bugreportdevice

Alternate method
Navigate to “Developer options”, ensure “USB debugging” is enabled, then enable “Bug report shortcut”. Capture bug report by holding the power button and selecting the “Take bug report” option.

Note: Please upload the bug report and screenshot to google drive and share the folder to android-bugreport@google.com, then share the link here.

vi...@google.com <vi...@google.com> #3Nov 10, 2024 06:57AM

Please provide the requested information to proceed further. Unfortunately the issue will be closed within 7 days if there is no further update.

al...@gmail.com <al...@gmail.com> #4Nov 11, 2024 02:39AM

No need to provide other infos. Android Studio Ladybug | 2024.2.1 RC 1 No android studio version suppport this feature.

ra...@google.com <ra...@google.com> Nov 13, 2024 11:46PM

Reassigned to an...@google.com.

pa...@google.com <pa...@google.com> Nov 14, 2024 01:23PM

Status: New

tn...@google.com <tn...@google.com> #5Nov 19, 2024 12:58AM

Marked as fixed, reassigned to tn...@google.com.

Fixed by https://cs.android.com/android-studio/platform/tools/base/+/3f25ee8da840d3837a0d5c63f1216b19b24eedf9 and more broadly https://cs.android.com/android-studio/platform/tools/base/+/768a66aee53e23dda7abd48b0411d776d725b35f

an...@google.com <an...@google.com> #6Nov 22, 2024 12:04AM

Thank you for your patience while our engineering team worked to resolve this issue. A fix for this issue is now available in:

Android Studio Meerkat | 2024.3.1 Canary 3
Android Gradle Plugin 8.9.0-alpha03

We encourage you to try the latest update.

If you notice further issues or have questions, please file a new bug report.

Thank you for taking the time to submit feedback — we really appreciate it!