IssueTracker

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


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.

How frequently does this issue occur? (e.g 100% of the time, 10% of the time)

Steps to reproduce
What steps are needed to reproduce this issue?

What is the expected output?

What is the current output?

If relevant, share 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

Screen record of the issue
Please capture screen record or video of the issue using following steps:
adb shell screenrecord /sdcard/video.mp4
Subsequently use following command to pull the recorded file:
adb pull /sdcard/video.mp4
Attach the file to this issue.

Note: Please avoid uploading directly to the issue using attachments. Please upload to google drive and share the folder to android-bugreport@google.com, then share the link here.

Attached is the sample project:
Steps to reproduce:
- Launch the sample app
- on MainActivity.. Click on Home Button of device or swipe up navigation
- the Activity comes in PIP Mode, Now Click on the PIP to Expand back to MainActivity.
- No click the "Click Me" Button, Sample Activity takes 7-8 seconds to open.

Expected:
The Activity should open directly even after coming back from pip to normal state.

However without going to pip, Sample Activity opens flawlessly.

100% reproducible.

Attached is the Sample Project and Video

Thank you for reporting this issue. We’ve shared this with our product and engineering teams and will continue to provide updates as more information becomes available.

I have the same issue except that my setup is a little bit different. I have Activity A and Activity B. Activity B enters pip mode, leaves pip mode and navigates back to Activity A and now Activity A is not able to open any Activities at all unless minimizing and maximizing Activity A. Sometimes it works without minimizing but the activity opens only after a very long delay.

Hi..This behaviour of new activity not opening starts happening throughout the app once app goes into the pip mode and expanded back to normal state. Seems to be a Android platform issue.

I also have the same issue. One hint is that log cat complains something about not allowing start activity from background while my MainActivity is in foreground?

Update log from logcat:

Background activity start [callingPackage: com.abc.zyx; callingUid: 10003; appSwitchAllowed: false; isCallingUidForeground: true; callingUidHasAnyVisibleWindow: true; callingUidProcState: TOP; isCallingUidPersistentSystemProcess: false; realCallingUid: 10003; isRealCallingUidForeground: true; realCallingUidHasAnyVisibleWindow: true; realCallingUidProcState: TOP; isRealCallingUidPersistentSystemProcess: false; originatingPendingIntent: null; allowBackgroundActivityStart: false; intent: Intent { cmp=com.abc.zyx/.FullScreenActivity (has extras) }; callerApp: ProcessRecord{27db025 29047:com.abc.zyx/u0a3}; inVisibleTask: true]

#10 What is the cause of this bug, any workaround we can apply for Android 12?

bumping this.. will this be available as a patch or with Android 13 SDK update ?  Any workaround for A12 as this is impacting million of users

Does anyone have a good solution on Android 12?

still waiting for the fix for android 12

I found this repo -> https://github.com/limdale/PipTest

This commit in particular seems to have a fix for Android 12, definitely a hack, but it could be a viable workaround -> https://github.com/limdale/PipTest/commit/ed49df5f8730946da472d85da76468687606692c

I tested this hack out on my project and the issue seems to be resolved for Android 12.  I hope this helps everyone who is suffering from this issue like I have been!

the error stills persists