NullPointerException in Lifecycle-Runtime-KTX Alpha5 when starting a AppCompatActivity [141536990]

Fixed

Bug

Status Update

No update yet.

Description

mg...@gtempaccount.com

created issue #1

Sep 24, 2019 07:25PM

Component used: androidx.lifecycle:lifecycle-runtime-ktx
Version used: 2.2.0-alpha05
Devices/Android versions reproduced on:
Device: Google Pixel 2 XL
Android version: 10
Android Security Patch level: September 5, 2019
Google Play System Update: 2019/09
Kernel version: 4.4.177-g83bee1dc48e8
Build Number: QP1A.190711.019

If this is a bug in the library, we would appreciate if you could attach:

Sample app:
Here is a link to a sample app that reproduces the issue, to trigger the issue just run the app it will happen immediately
NOTE: Some how the issue doesn't appear to be happening in some emulated device (Pixel 2 XL API 28)

https://github.com/migueledgracia/Sample-App-For-Bug-Validation.git

This is the error that prints out:
java.lang.NullPointerException: Attempt to invoke virtual method 'void androidx.lifecycle.ReportFragment.setProcessListener(androidx.lifecycle.ReportFragment$ActivityInitializationListener)' on a null object reference

when super.onCreate get's called
at com.example.sampleproject.MainActivity.onCreate(MainActivity.kt:9)

Comments

il...@google.com <il...@google.com> #2Sep 24, 2019 07:51PM

Status: Won't Fix (Intended Behavior)

Jeremy, is this still an issue? I think the problem was that you had two transitions targeting the same View for the same action (e.g. two Slide() transitions).

mg...@gtempaccount.com <mg...@gtempaccount.com> #3Sep 24, 2019 08:11PM

I have a similar issue with plain AnimatorSet:

set.start()
set.pause()
set.setCurrentPlayTime(100)
set.setCurrentPlayTime(0)
set.setCurrentPlayTime(100)
set.resume()

doesn't play animation in resume().

il...@google.com <il...@google.com> #4Sep 27, 2019 10:50PM

Accepted by il...@google.com.

Should clarify that if I filter out setCurrentPlayTime(0) (or replace it with setCurrentPlayTime(1)) it works well.

Also even with setCurrentPlayTime(0), onAnimationEnd is notified with correct delay (as if the animation has played).

ap...@google.com <ap...@google.com> #5Sep 30, 2019 06:19PM

@ #4:

I think that is intended for Animator. If you set the currentPlayTime to 0 or the total duration the animator completes. We do some special checks in fragments to handle it.

il...@google.com <il...@google.com> #6Sep 30, 2019 07:20PM

Marked as fixed.

Did some investigation on the Fragment side and it seems like the merged transition is targeting correctly.

Exiting Transition: Slide@aa9288e: tgts(android.widget.LinearLayout{f9add3d})
>>>>> ExitingViews <<<<<
View: android.widget.LinearLayout{f9add3d}
Entering Transition: Slide@35b8af: tgts(android.widget.LinearLayout{b7f24bc})
>>>>> EnteringViews <<<<<
View: android.widget.LinearLayout{b7f24bc}
Final merged transition: TransitionSet@7bc1c45: 
      TransitionSet@e133f9a: 
        Slide@aa9288e: tgts(android.widget.LinearLayout{f9add3d})
      Slide@35b8af: tgts(android.widget.LinearLayout{b7f24bc})
merged transition passed to controlDelayedTransition: TransitionSet@7bc1c45: 
      TransitionSet@e133f9a: 
        Slide@aa9288e: tgts(android.widget.LinearLayout{f9add3d})
      Slide@35b8af: tgts(android.widget.LinearLayout{b7f24bc})

Still digging.

Issue 141536990