Status Update
No update yet.
Comments
ea...@gmail.com
Information redacted by Android Beta Feedback.
bo...@gmail.com
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.
ad...@google.com
ad...@google.com
What
Feature request
Screen record attached. Lock button appears whenever a new notification comes in or briefly when you expand on current notifications.
Where
Build and device data
- Build Number: google/raven_beta/raven:VanillaIceCream/AP31.240426.023/11830707:user/release-keys
(Note: It is the build when sending this report. For exact build reference, please see the attached bugreport.)
Debugging information
Google Play services
com.google.android.gms
Version 241718038 (24.17.18 (190400-633711484))
System App (Updated)
Android System WebView
com.google.android.webview
Version 636758231 (124.0.6367.82)
System App (Updated)
Network operator: Google Fi
SIM operator: Google Fi
Filed by Android Beta Feedback. Version (Updated): 2.42-betterbug.external_20240410_RC03 (DOGFOOD)
To learn more about our feedback process, please visit
il...@google.com
il...@google.com
jb...@google.com
What
Feature request
X
Where
Build and device data
- Build Number: google/bluejay_beta/bluejay:VanillaIceCream/AP31.240426.023/11830707:user/release-keys
(Note: It is the build when sending this report. For exact build reference, please see the attached bugreport.)
Debugging information
Google Play services
com.google.android.gms
Version 242013038 (24.20.13 (190400-633713831))
System App (Updated)
Android System WebView
com.google.android.webview
Version 636758231 (124.0.6367.82)
System App (Updated)
Network operator: Not available
SIM operator: Boost Mobile
Filed by Android Beta Feedback. Version (Updated): 2.43-betterbug.external_20240522_RC03 (DOGFOOD)
To learn more about our feedback process, please visit
Description
Steps to reproduce the behaviour:
import android.view.View;
import androidx.appcompat.app.AppCompatActivity;
import androidx.fragment.app.Fragment;
import androidx.fragment.app.FragmentManager;
import androidx.fragment.app.FragmentTransaction;
[...]
public class AppActivity extends AppCompatActivity
myFragment1.setSharedElementReturnTransition(new MyNewTransition());
myFragment1.setSharedElementEnterTransition(new MyNewTransition());
[...]
a) getSupportFragmentManager().beginTransaction()
.addSharedElement(myImage, "mytransition")
.replace(R.id.recycler_view_container, myFragment2)
.commit();
b) getSupportFragmentManager().beginTransaction()
.addSharedElement(myImage, "mytransition")
.add(R.id.recycler_view_container, myFragment2)
.hide(myFragment1)
commit();
In the (a) code, the image transition is correct and animation occurs perfectly between the shared elements, but I don't need this.
In the (b) code, the only difference is that myFragment1 is being hidden and the myFragment2 is added, in this case both the enter transition and the return transition are broken and no animation occurs.
I need the (b) code because "replace"-ing the fragments will destroy the myFragment1 and rebuilding it is a heavy-load process.
I think this is a bug with androidx libraries