Obsolete
Status Update
Comments
jb...@gmail.com <jb...@gmail.com> #2
Howdy it's jb, who the fuck is this
ku...@google.com <ku...@google.com>
ku...@google.com <ku...@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.
ku...@google.com <ku...@google.com> #4
Please provide the information as requested in comment #3 , For us to further investigate this issue.
[Deleted User] <[Deleted User]> #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
[Deleted User] <[Deleted User]> #6
fyi, as noted in the first message, this bug happens on Android 7 and later
ku...@google.com <ku...@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.
wb...@gmail.com <wb...@gmail.com> #8
Any update?
[Deleted User] <[Deleted User]> #9
Any update?
ka...@sulekha.com <ka...@sulekha.com> #10
We couldn't proceed the dynamic feature implementation, bcz of this issue. kindly provide some update on this issue.
ad...@google.com <ad...@google.com>
[Deleted User] <[Deleted User]> #11
Now that you are deprecating the "feature" android gradle plugin, will you fix the bugs in the dynamic feature plugin?
[Deleted User] <[Deleted User]> #12
Anyone has a workaround (except not using dynamic features and putting everything again in one module?)
[Deleted User] <[Deleted User]> #13
Any update?
te...@google.com <te...@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?
vi...@google.com <vi...@google.com> #15
Please share the information requested comment #14 .
ti...@gmail.com <ti...@gmail.com> #16
There is a zipped project where one can easily reproduce the issue, what else would you want?
https://issuetracker.google.com/issues/123857941#comment5
wb...@gmail.com <wb...@gmail.com> #18
[ comment#17 ](https://issuetracker.google.com/issues/123857941#comment17 ) thanks for the workaround and explanation where the bug actually is.
@google: clearly it is not an application bug, but a android manifest merger problem. Can this issue be re-evaluated & hopefully fixed?
@google: clearly it is not an application bug, but a android manifest merger problem. Can this issue be re-evaluated & hopefully fixed?
vi...@google.com <vi...@google.com>
at...@google.com <at...@google.com> #19
Thank you for your feedback. We assure you that we are doing our best to address all issues reported. For now, we will be closing the issue as won't fix obsolete. If this issue currently still exists, we request that you log a new issue along with the bug report here
Description
- I'm trying to launch an activity using contex.startActivity(Intent) from an activity which resides in the app module. The target activity is located in a 'com.android.dynamic-feature'.
The dynamic feature config is as follows in its AndroidManifest.xml (so no instant or onDemand loading yet):
<dist:module
dist:instant="false"
dist:onDemand="false"
dist:title="All APP Features">
<dist:fusing dist:include="false" />
</dist:module>
The structure of the Intent I'm passing to context.startActivity is as follows:
new Intent(Intent.ACTION_VIEW, deeplinkUri) where deeplinkUri is something like myapp://dynamicfeature
Inside the AndroidManifest.xml from the dynamic feature I have my Feature activity with the following intent filter:
<activity
android:name="com.myfeature.MyFeatureActivity">
<intent-filter>
<action android:name="android.intent.action.VIEW" />
<category android:name="android.intent.category.DEFAULT" />
<category android:name="android.intent.category.BROWSABLE" />
<!-- Handle local url "joyn://login" -->
<data
android:host="dynamicfeature"
android:scheme="myapp" />
</intent-filter>
</activity>
Now what happens when the startActivity is called:
- the Android ResolverActivity is briefly shown
- the MyFeatureActive is launched
- the ResolverActivity is not displayed anymore.
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
Displayed android/com.android.internal.app.ResolverActivity: +119ms
/ActivityManager: START u0 {act=android.intent.action.VIEW dat=myapp://dynamicfeature flg=0x3000000 cmp=<applicationId>/com.myfeature.MyFeatureActivity} from uid 10079
2019-02-04 14:20:22.167 2037-2074/system_process I/ActivityManager: Displayed <applicationId>/com.myfeature.MyFeatureActivity: +498ms
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
I have no idea what is causing this issue. Before trying dynamic feature the same mechanism worked flawlessly. (eg. all Activities in one app module)