Assigned
Status Update
Comments
sc...@google.com <sc...@google.com>
sc...@google.com <sc...@google.com> #2
I see same issue and have been debugging it.
NOTE: It DOES NOT happen if not using support package, but use android level 14/15 library. I believe Honeycomb works well too.
My current workaround is to provide my own DialogFragment.show() method, like below:
public int show(FragmentTransaction transaction, String tag) {
return show(transaction, tag, false);
}
public int show(FragmentTransaction transaction, String tag, boolean allowStateLoss) {
transaction.add(this, tag);
mRemoved = false;
mBackStackId = allowStateLoss ? transaction.commitAllowingStateLoss() : transaction.commit();
return mBackStackId;
}
NOTE: It DOES NOT happen if not using support package, but use android level 14/15 library. I believe Honeycomb works well too.
My current workaround is to provide my own DialogFragment.show() method, like below:
public int show(FragmentTransaction transaction, String tag) {
return show(transaction, tag, false);
}
public int show(FragmentTransaction transaction, String tag, boolean allowStateLoss) {
transaction.add(this, tag);
mRemoved = false;
mBackStackId = allowStateLoss ? transaction.commitAllowingStateLoss() : transaction.commit();
return mBackStackId;
}
Description
The Maven group libraryversions.toml .
androidx.camera
is configured with multiple atomic group declarations inA Maven group should have a single atomic version to ensure consistent versioning across projects. We have started enforcing this in aosp/3528590, but we'd like to remove the need to bypass the check for certain groups.
Request
androidx.camera
inlibraryversions.toml
to ensure that only one declaration is usedALLOWED_ATOMIC_GROUP_EXCEPTIONS
field in