[Android Q Beta] Transition return issues when more than 1 level depth [137487202]

Fixed

Bug

Platform

[AOSP] assigned

Status Update

No update yet.

Description

to...@gmail.com

created issue #1

Jul 15, 2019 10:52AM

Android Q beta 5 on a pixel 3a. (Same behavior on emulators images).

Return transitions does not run after 2 level depth see attached video.

Transition from activity A to B with shared image -> Works
Transition from activity B to C with shared image -> Works
Transition back from activity C to B -> Works
Transition back from activity B to A -> No transition running.

It does work correctly on all previous non Q Android versions.

deleted

Restricted

0 B

Comments

ve...@google.com <ve...@google.com> Jul 16, 2019 08:07AM

Assigned to ve...@google.com.

ve...@google.com <ve...@google.com> #2Jul 16, 2019 12:06PM

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

Please provide app details to reproduce the issue. Also mention the steps to be followed for reproducing the issue with the given app.

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

Android bug report capturing
After reproducing the issue, press the volume up, volume down, and power button simultaneously. This will capture a bug report on your device in the “bug reports” directory. Attach the bug report file to this issue.

Alternate method
After reproducing the issue, navigate to “developer settings”, 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 : To avoid leaking private information, please share screenshots and bugreports only in Google Drive. Share files with android-bugreport@google.com and include only Google drive links in your bug. Bug report attachments should not be included directly in issue reports.

to...@gmail.com <to...@gmail.com> #3Jul 16, 2019 12:34PM

Arf :(

First level external contractor template :(

This is 100% reproductible with any app that does 2 levels transitions as described in OP.

All apps I know doing that require external things so can't give a simple repro step.

If Google team can't repro (I doubt it...) I can build a sample app but won't until this is affected to proper team to avoid loosing my time as quite a few times ;)

to...@gmail.com <to...@gmail.com> #4Jul 16, 2019 03:24PM

Actually the issue is worse and can be reproduced in another way.

Start activity A to B with transition
Return to home
Return to app from recent.
Press back, the transition does not runs.

Can be reproduced with plaid :

https://play.google.com/store/apps/details?id=io.plaidapp&hl=en

to...@gmail.com <to...@gmail.com> #5Jul 16, 2019 06:32PM

And another way to reproduce with plaid

Start Plaid, click any item with an image to have a transition, on the new activity press the image to open the customtab browser, press back, press back, the proper transition does not run too on Android Q Beta 5, work on previous versions.

ve...@google.com <ve...@google.com> #6Jul 18, 2019 12:22PM

Thank you for reporting this issue. We have shared this with our product and engineering team and will update this issue with more information as it becomes available.

to...@gmail.com <to...@gmail.com> #7Aug 7, 2019 06:36PM

Still present in Beta 6, this is a major issue as user experience is greatly reduced.

ar...@google.com <ar...@google.com> #8Sep 4, 2019 12:43AM

We've deferred this issue for consideration in a future release. Thank you for your time to make Android better. In case you want to provide more information with respect to this bug, please file a bug in AOSP via "

https://goo.gl/TbMiIO

an...@google.com <an...@google.com> Sep 4, 2019 01:04PM

Reassigned to an...@google.com.

de...@1010consulting.ca <de...@1010consulting.ca> #9Sep 4, 2019 05:58PM

Rolling back all androidx.transition.abc imports to android.transition.abc imports appears to have fixed shared element transitions for us.

to...@gmail.com <to...@gmail.com> #10Sep 4, 2019 06:06PM

I'm only using native stuff for the transitions and nothing from Androidx/Support libraries.

vi...@google.com <vi...@google.com> Dec 9, 2019 09:08AM

Reassigned to cc...@google.com.

to...@gmail.com <to...@gmail.com> #11Feb 19, 2020 06:18PM

And as expected this issue is still present in the first preview release of R :)

to...@gmail.com <to...@gmail.com> #12Apr 23, 2020 07:30PM

And now dev 3 and the issue is still present.

It really makes us feel good to see such implication on major bugs spanning on 2 Android release, we really know our efforts to try to have a good platform are useful.

to...@gmail.com <to...@gmail.com> #13May 6, 2020 07:00PM

And dev 4 still have the issue.

At some point someone should have the decency to say that you absolutely do not care about something as basic as activity transition or reports from devs :)

Remove them from doc and close this maybe?

ad...@google.com <ad...@google.com> #14May 29, 2020 10:52AM

Marked as fixed.

The issue has been fixed and it will be available in future.

to...@gmail.com <to...@gmail.com> #15Jun 11, 2020 07:59AM

Not fixed in 11 Beta 1 do you have more details about what future?

to...@gmail.com <to...@gmail.com> #16Jul 10, 2020 03:35PM

And as mostly predicted not fixed in beta 2 either :) I guess future release means S or T.

to...@gmail.com <to...@gmail.com> #17Aug 7, 2020 07:31AM

So as expected still broken in beta 3 :)

ad...@google.com <ad...@google.com> #18Aug 7, 2020 03:26PM

Status: Assigned (reopened)

This is not fixed yet. We will update this issue with more information as it becomes available.

to...@gmail.com <to...@gmail.com> #19Sep 8, 2020 08:41PM

And broken in final release :)

Congratulations, there's no better way to force devs to switch to single activity than breaking something as basic as activity transitions and not fixing for 2 major releases.

to...@gmail.com <to...@gmail.com> #20Feb 19, 2021 08:47AM

And here I am again as a new Android release cycle is starting :)

This is still an issue on Android S dev preview.

ad...@google.com <ad...@google.com> #21Apr 28, 2021 06:10PM