Fixed
Status Update
Comments
ju...@google.com <ju...@google.com>
nj...@google.com <nj...@google.com>
ap...@google.com <ap...@google.com> #2
Howdy it's jb, who the fuck is this
ap...@google.com <ap...@google.com> #3
Can you provide the below requested information to better understand the issue:
Steps to reproduce
Please provide a sample application or apk to reproduce the issue.
Also kindly mention the steps to be followed for reproducing the issue with the given sample application.
Expected output
Could you please explain the expected behavior.
Current output
Could you please explain the current behavior.
Steps to reproduce
Please provide a sample application or apk to reproduce the issue.
Also kindly mention the steps to be followed for reproducing the issue with the given sample application.
Expected output
Could you please explain the expected behavior.
Current output
Could you please explain the current behavior.
ap...@google.com <ap...@google.com> #4
Please provide the information as requested in comment #3 , For us to further investigate this issue.
ap...@google.com <ap...@google.com> #5
Please find attached a simple testcase.
Steps to reproduce:
- Run the application
- Click on the Button
Expected output
- The Feature 1 activity is shown
Current output
- The Chooser activity is briefly shown
- The Feature 1 activity is shown
Steps to reproduce:
- Run the application
- Click on the Button
Expected output
- The Feature 1 activity is shown
Current output
- The Chooser activity is briefly shown
- The Feature 1 activity is shown
ap...@google.com <ap...@google.com> #6
fyi, as noted in the first message, this bug happens on Android 7 and later
ap...@google.com <ap...@google.com> #7
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.
ap...@google.com <ap...@google.com> #8
Any update?
nj...@google.com <nj...@google.com>
ap...@google.com <ap...@google.com> #9
Any update?
pr...@google.com <pr...@google.com> #10
We couldn't proceed the dynamic feature implementation, bcz of this issue. kindly provide some update on this issue.
tj...@gmail.com <tj...@gmail.com> #11
Now that you are deprecating the "feature" android gradle plugin, will you fix the bugs in the dynamic feature plugin?
tj...@gmail.com <tj...@gmail.com> #12
Anyone has a workaround (except not using dynamic features and putting everything again in one module?)
ap...@google.com <ap...@google.com> #13
Any update?
na...@google.com <na...@google.com> #14
Below is the response from our engineering team -
--------------------------------------------------------------------------------
This is an application bug. in both cases [android 6 and android 7], the resolver is starting. only the resolver must be slightly different in android 6 such that it winds up starting your activity without actually showing. but, in neither version are you actually directly launching your activity.
from the initial description:
Looking at the Logcat output I see:
START u0 {act=android.intent.action.VIEW dat=myapp://dynamicfeature cmp=android/com.android.internal.app.ResolverActivity} from uid 10079
On Android 6 with the same code it works correclty, and I don't see the ResolverActivity appearing.
START u0 {act=android.intent.action.VIEW dat=myapp://dynamicfeature cmp=android/com.android.internal.app.ResolverActivity} from uid 10079
What is the intent you're using to start the activity?
--------------------------------------------------------------------------------
This is an application bug. in both cases [android 6 and android 7], the resolver is starting. only the resolver must be slightly different in android 6 such that it winds up starting your activity without actually showing. but, in neither version are you actually directly launching your activity.
from the initial description:
Looking at the Logcat output I see:
START u0 {act=android.intent.action.VIEW dat=myapp://dynamicfeature cmp=android/com.android.internal.app.ResolverActivity} from uid 10079
On Android 6 with the same code it works correclty, and I don't see the ResolverActivity appearing.
START u0 {act=android.intent.action.VIEW dat=myapp://dynamicfeature cmp=android/com.android.internal.app.ResolverActivity} from uid 10079
What is the intent you're using to start the activity?
Description
Per Nader's suggestion, `OwnedLayer` is already being used for handling drawing and is in commonMain. If we expose a subset of functionalities of `OwnedLayer`, shared element will be able to leverage their existing layer and render it elsewhere.