IssueTracker

Is this a dupe of the manifest merger issues?

It's either a dupe of b/134544230 or b/138502756. Can you try the following workaround and confirm whether it enables you to launch?

1. Open the AndroidManifest.xml file for the module corresponding to your run configuration.
2. Switch to the Merged Manifest tab and wait for it to load.
3. Try launching the app again.

I opened Merged Manifest but it say `Nothing to show`, I waited like 5 minutes, nothing changed.
I verified that it happens after branch change which has manifest change.

Thank you for the feedback. This is indeed a duplicate of b/138502756, but perhaps your logs will lead to more information.

Actually, I see some errors present in your logs that I don't see in the idea.log posted to b/138502756. The manifest merger encountered a cycle when parsing one of the elements below (in retrospect, it would have been helpful to log which element introduces the cycle). +kudasov@, this is the error which may have resulted in a StackOverflow before we added the additional logging in b/130315019. WDYT?

2019-08-22 14:39:01,160 [2356026]   WARN - .idea.model.MergedManifestInfo - getMergedManifestSupplier exception
com.android.manifmerger.ManifestMerger2$MergeFailureException: java.lang.RuntimeException: Circular dependency in XML <?xml version="1.0" encoding="utf-8"?>
<manifest package="de.is24.mobile.relocation.flow" xmlns:android="http://schemas.android.com/apk/res/android" xmlns:tools="http://schemas.android.com/tools"><uses-sdk android:minSdkVersion="21" android:targetSdkVersion="28"/>
<application android:supportsRtl="true">
    <activity android:configChanges="orientation|screenSize" android:name="de.is24.mobile.relocation.flow.FlowActivity" android:theme="@style/RelocationFlow.Theme.Translucent" android:windowSoftInputMode="adjustResize">
   
        at com.android.manifmerger.ManifestMerger2.loadLibraries(ManifestMerger2.java:1279)
        at com.android.manifmerger.ManifestMerger2.merge(ManifestMerger2.java:193)
        at com.android.manifmerger.ManifestMerger2.access$600(ManifestMerger2.java:71)
        at com.android.manifmerger.ManifestMerger2$Invoker.merge(ManifestMerger2.java:1941)
        at com.android.tools.idea.model.MergedManifestInfo.getMergedManifest(MergedManifestInfo.java:491)
        at com.android.tools.idea.model.MergedManifestInfo.mergeManifests(MergedManifestInfo.java:234)
        at com.android.tools.idea.model.MergedManifestInfo.create(MergedManifestInfo.java:202)
        at com.android.tools.idea.model.MergedManifestSupplier$getOrCreateSnapshot$$inlined$runReadAction$1.compute(actions.kt:78)
        at com.intellij.openapi.application.impl.ApplicationImpl.runReadAction(ApplicationImpl.java:917)
        at com.android.tools.idea.model.MergedManifestSupplier.getOrCreateSnapshot(MergedManifestManager.kt:340)
        at com.android.tools.idea.model.MergedManifestSupplier.getOrCreateSnapshotInCallingThread(MergedManifestManager.kt:142)
        at com.android.tools.idea.model.MergedManifestManager$Companion.getFreshSnapshot(MergedManifestManager.kt:332)
        at com.android.tools.idea.model.MergedManifestManager.getFreshSnapshot(MergedManifestManager.kt)
        at com.android.tools.idea.run.activity.DefaultActivityLocator.computeDefaultActivity(DefaultActivityLocator.java:96)
        ...
Caused by: java.lang.RuntimeException: Circular dependency in XML <?xml version="1.0" encoding="utf-8"?>
<manifest package="de.is24.mobile.relocation.flow" xmlns:android="http://schemas.android.com/apk/res/android" xmlns:tools="http://schemas.android.com/tools"><uses-sdk android:minSdkVersion="21" android:targetSdkVersion="28"/>
<application android:supportsRtl="true">
    <activity android:configChanges="orientation|screenSize" android:name="de.is24.mobile.relocation.flow.FlowActivity" android:theme="@style/RelocationFlow.Theme.Translucent" android:windowSoftInputMode="adjustResize">
   
        at com.android.utils.XmlUtils.append(XmlUtils.java:672)
        at com.android.utils.XmlUtils.append(XmlUtils.java:737)
        at com.android.utils.XmlUtils.append(XmlUtils.java:737)
        at com.android.utils.XmlUtils.append(XmlUtils.java:737)
        at com.android.utils.XmlUtils.append(XmlUtils.java:689)
        at com.android.utils.XmlUtils.toXml(XmlUtils.java:661)
        at com.android.utils.XmlUtils.toXml(XmlUtils.java:653)
        at com.android.tools.idea.model.MergedManifestInfo$1.getInputStream(MergedManifestInfo.java:436)
        at com.android.manifmerger.ManifestMerger2.loadLibraries(ManifestMerger2.java:1266)
        ... 49 more

and

2019-08-22 18:25:18,247 [6706776]   WARN - ea.model.MergedManifestManager - Could not read Manifest data
java.lang.IllegalArgumentException: Multiple entries with same key: de.is24.mobile.home.feed.HomeFeedActivity=com.android.tools.idea.model.ActivityAttributesSnapshot@450c88b5 and de.is24.mobile.home.feed.HomeFeedActivity=com.android.tools.idea.model.ActivityAttributesSnapshot@62420c8d
        at com.google.common.collect.ImmutableMap.conflictException(ImmutableMap.java:215)
        at com.google.common.collect.ImmutableMap.checkNoConflict(ImmutableMap.java:209)
        at com.google.common.collect.RegularImmutableMap.checkNoConflictInKeyBucket(RegularImmutableMap.java:147)
        at com.google.common.collect.RegularImmutableMap.fromEntryArray(RegularImmutableMap.java:110)
        at com.google.common.collect.ImmutableMap$Builder.build(ImmutableMap.java:393)
        at com.android.tools.idea.model.MergedManifestSnapshotFactory.createMergedManifestSnapshot(MergedManifestSnapshotFactory.java:305)
        at com.android.tools.idea.model.MergedManifestSupplier$getOrCreateSnapshot$$inlined$runReadAction$1.compute(actions.kt:78)
        at com.intellij.openapi.application.impl.ApplicationImpl.runReadAction(ApplicationImpl.java:917)
        at com.android.tools.idea.model.MergedManifestSupplier.getOrCreateSnapshot(MergedManifestManager.kt:340)
        at com.android.tools.idea.model.MergedManifestSupplier.getOrCreateSnapshotInCallingThread(MergedManifestManager.kt:142)
        at com.android.tools.idea.model.MergedManifestManager$Companion.getFreshSnapshot(MergedManifestManager.kt:332)
        at com.android.tools.idea.model.MergedManifestManager.getFreshSnapshot(MergedManifestManager.kt)
        at com.android.tools.idea.run.activity.DefaultActivityLocator.computeDefaultActivity(DefaultActivityLocator.java:96)

While we still don't know why we're seeing circular dependencies, kunshen@ managed to root cause why this breaks launching the default activity:

  - MergedManifestSnapshotFactory#createMergedManifestSnapshot returns null if it encounters an error computing the merged manifest (in this case, the circular dependency error).
  - When MergedManifestManager receives null from the factory, it creates an "emtpy" MergedManifestSnapshot whose MergedManifestInfo is null.
  - MergedManifestManager#snpashotUpToDate assumes (incorrectly, my bad :c ) that the snapshot's MergedManifestInfo can only be null if the module has been disposed, so it returns false in this case to prevent us from doing more work for an already-disposed module.

These behaviors together mean that when MergedManifestSnapshotFactory#createMergedManifestSnapshot encounters an exception, MergedManifestManager gets stuck in a state where it offers up the "empty" snapshot and never tries to recompute the merged manifest. DefaultActivityLocator relies on the snapshot to get a list of activities to choose from, and so launching the app fails because the empty snapshot doesn't have any activities.

The long-term (3.7) solution will be to use a synchronous index-based API to determine the default activity without needing to compute the entire merged manifest. The best short-term (3.6 Canary 11) solution that I can think of is to

-  Propagate the exceptions in MergedManifestSnapshotFactory#createMergedManifestSnapshot instead of returning null. This means that the future returned by MergedManifestSupplier#get will complete with an exception.
-  Make sure the few consumers we've migrated to the AsyncSupplier-based APIs (DefaultActivityLocator, ManifestEditor) check for exceptions when accessing the result.
-  For legacy callers using the deprecated adapter methods in MergedManifestManager, we'll check for exceptions and return an "empty" snapshot if we encounter one. These callers will continue to receive the same dummy values they did before until the long-term fix lands.

The main advantage to propagating the exceptions is that it gives us a convenient way to bypass the caching scheme so that we don't throw out a stale but complete manifest and replace it with a dummy manifest that gives no information.

Duplicate, which includes video showing the issue:
https://issuetracker.google.com/issues/141757580

Thanks for the video capturing the issue, and for everyone's patience while we've worked to get a solution in place. I've submitted the fixes and they should land in 3.6 Beta 2.

Note that you may still see a few random occurrences of "Default Activity not found" until the subsequent release sometime in the end of October, but after 3.6 Beta 2 the workaround described in #3 should get you out of this scenario in such cases.

Sorry, ignore the attachment :)

@10 I think that on Canary I don't see this issue. Possible?

The last canary doesn't include the fixes mentioned in #10, but there are other mitigating changes in place that try to prevent this scenario as much as possible. Reproducing the problem is fickle and depends on whether there are certain kinds of errors in your manifest files. I think it's very likely that you just happen to not be encountering the issue anymore, even though it's still present.

@12 I see. Thanks.

The workaround in #3 doesn't work for me. The merged manifest view just says "nothing to show".

I think that (rarely) I still see this issue .

I also saw this issue when I opened our project in AS 4.0 alpha3. Project uses AGP 3.5.2

I got this today in 3.6 beta 4.
It was fixed after I did restart and invalidate

For those still experiencing this issue, there is another issue that is still open: https://issuetracker.google.com/issues/143229099

For those of you reporting that this is still an issue, if you haven't already, please include the version of studio you're running and your idea.log (Help > Show Log in Files). Thank you, and sorry for the inconvenience!

My issue still exist with Android Studio 3.6 Beta4 with APG 3.5 beta4

Please find the logs

Please find different logs.
Android Studio 3.6 Beta4 with APG 3.5 beta4

@19 I got a similar issue today, which I'm pretty sure I had before:
It builds fine, about to install and run, but then does nothing...
Note that adb works fine, as it shows logs
See attached files.

Sorry for the delay y'all. I suspect that for most of you the errors you're seeing in 3.6 Beta are due to the same root cause as https://issuetracker.google.com/issues/144939434 . I submitted a fix that should land in 3.6 RC 1, which will hopefully be released sometime next week. 4.0 Canary already includes the fix, so you may wish to upgrade to the early access build in the meantime if this issue is significantly affecting your productivity.

For anyone experiencing issues in 4.0, please attach logs so I can have a closer look.

Okay, after taking a closer look at the timeline, I think the fix to the caching issue described in https://issuetracker.google.com/issues/144939434 and comments #7-8 doesn't cover OP's original issue, which is still present in their logs:

java.lang.IllegalArgumentException: Multiple entries with same key: com.autoscout24.contact.form.ContactFormActivity=com.android.tools.idea.model.ActivityAttributesSnapshot@63ec0b3f and com.autoscout24.contact.form.ContactFormActivity=com.android.tools.idea.model.ActivityAttributesSnapshot@65090061
  ...

Thanks again for your patience while I dive into the root cause.

I've got a different error in my log

2019-12-07 10:47:49,541 [2790979]   WARN - .idea.model.MergedManifestInfo - getMergedManifestSupplier failed Manifest merger failed : Referenced navigation file with navigationXmlId = feature_reward_graph not found

The mentioned navigation graph file does exist but comes from a different module. The setup is like this:

- app AndroidManifest.xml contains <nav-graph android:value="@navigation/notifications_tab" /> declaration
- in navigation/navigation/notifications_tab.xml we've got <include app:graph="@navigation/feature_reward_graph" />
- the included navigation/feature_reward_graph.xml comes from a local library module which the app module depends on

For #25, this is the same issue as b/143828478. I will follow up there as soon as I know more.

#25, can you confirm which version of Studio you're using?

I'm seeing the issue with 4.0.0 Canary 6. Also found this somewhere above in the log, not sure if related:

2019-12-12 22:40:16,381 [  59199]   WARN - d.tools.idea.run.ui.BaseAction - [app-freeletics] Unable to obtain main package from manifest.
com.android.tools.idea.run.ApkProvisionException: [app-freeletics] Unable to obtain main package from manifest.
        at com.android.tools.idea.run.ApkProviderUtil.computePackageName(ApkProviderUtil.java:109)
        at com.android.tools.idea.run.NonGradleApplicationIdProvider.getPackageName(NonGradleApplicationIdProvider.java:35)
        at com.android.tools.idea.run.deployment.DeviceAndSnapshotComboBoxDeployableProvider.getDeployable(DeviceAndSnapshotComboBoxDeployableProvider.java:57)
        at com.android.tools.idea.run.ui.BaseAction.getDisableMessage(BaseAction.java:170)
        at com.android.tools.idea.run.ui.BaseAction.update(BaseAction.java:131)
        at com.android.tools.idea.run.ui.CodeSwapAction.update(CodeSwapAction.java:51)
        at com.intellij.openapi.actionSystem.ex.ActionUtil.performDumbAwareUpdate(ActionUtil.java:176)
        at com.intellij.openapi.actionSystem.impl.ActionUpdater.doUpdate(ActionUpdater.java:379)
        at com.intellij.openapi.actionSystem.impl.ActionUpdater.lambda$null$1(ActionUpdater.java:79)
        at com.intellij.openapi.actionSystem.impl.ActionUpdater.callAction(ActionUpdater.java:107)
        at com.intellij.openapi.actionSystem.impl.ActionUpdater.lambda$new$2(ActionUpdater.java:80)
        at com.intellij.openapi.actionSystem.impl.ActionUpdater.update(ActionUpdater.java:365)
        at com.intellij.openapi.actionSystem.impl.ActionUpdater.expandGroupChild(ActionUpdater.java:232)
        at com.intellij.openapi.actionSystem.impl.ActionUpdater.lambda$doExpandActionGroup$19(ActionUpdater.java:216)
        at com.intellij.util.containers.ContainerUtil.concat(ContainerUtil.java:1641)
        at com.intellij.openapi.actionSystem.impl.ActionUpdater.doExpandActionGroup(ActionUpdater.java:216)
        at com.intellij.openapi.actionSystem.impl.ActionUpdater.expandGroupChild(ActionUpdater.java:259)
        at com.intellij.openapi.actionSystem.impl.ActionUpdater.lambda$doExpandActionGroup$19(ActionUpdater.java:216)
        at com.intellij.util.containers.ContainerUtil.concat(ContainerUtil.java:1641)
        at com.intellij.openapi.actionSystem.impl.ActionUpdater.doExpandActionGroup(ActionUpdater.java:216)
        at com.intellij.openapi.actionSystem.impl.ActionUpdater.expandGroupChild(ActionUpdater.java:259)
        at com.intellij.openapi.actionSystem.impl.ActionUpdater.lambda$doExpandActionGroup$19(ActionUpdater.java:216)
        at com.intellij.util.containers.ContainerUtil.concat(ContainerUtil.java:1641)
        at com.intellij.openapi.actionSystem.impl.ActionUpdater.doExpandActionGroup(ActionUpdater.java:216)
        at com.intellij.openapi.actionSystem.impl.ActionUpdater.expandActionGroup(ActionUpdater.java:140)
        at com.intellij.openapi.actionSystem.impl.ActionUpdater.expandActionGroup(ActionUpdater.java:132)
        at com.intellij.openapi.actionSystem.impl.ActionUpdater.lambda$expandActionGroupWithTimeout$11(ActionUpdater.java:149)
        at com.intellij.openapi.progress.impl.CoreProgressManager.lambda$runProcess$3(CoreProgressManager.java:186)
        at com.intellij.openapi.progress.impl.CoreProgressManager.lambda$runProcess$2(CoreProgressManager.java:170)
        at com.intellij.openapi.progress.impl.CoreProgressManager.registerIndicatorAndRun(CoreProgressManager.java:592)
        at com.intellij.openapi.progress.impl.CoreProgressManager.executeProcessUnderProgress(CoreProgressManager.java:538)
        at com.intellij.openapi.progress.impl.ProgressManagerImpl.executeProcessUnderProgress(ProgressManagerImpl.java:59)
        at com.intellij.openapi.progress.impl.CoreProgressManager.runProcess(CoreProgressManager.java:157)
        at com.intellij.openapi.progress.impl.CoreProgressManager.runProcess(CoreProgressManager.java:186)
        at com.intellij.openapi.progress.util.ProgressIndicatorUtils.withTimeout(ProgressIndicatorUtils.java:258)
        at com.intellij.openapi.actionSystem.impl.ActionUpdater.expandActionGroupWithTimeout(ActionUpdater.java:148)
        at com.intellij.openapi.actionSystem.impl.ActionToolbarImpl.updateActionsImpl(ActionToolbarImpl.java:1089)
        at com.intellij.openapi.actionSystem.impl.ActionToolbarImpl.access$000(ActionToolbarImpl.java:51)
        at com.intellij.openapi.actionSystem.impl.ActionToolbarImpl$1.updateActionsImpl(ActionToolbarImpl.java:164)
        at com.intellij.openapi.actionSystem.impl.ToolbarUpdater$MyUpdateRunnable.run(ToolbarUpdater.java:172)
        at com.intellij.util.ui.UIUtil.invokeLaterIfNeeded(UIUtil.java:2434)
        at com.intellij.ide.IdeEventQueue.ifFocusEventsInTheQueue(IdeEventQueue.java:224)
        at com.intellij.ide.IdeEventQueue.executeWhenAllFocusEventsLeftTheQueue(IdeEventQueue.java:176)
        at com.intellij.openapi.wm.impl.FocusManagerImpl.doWhenFocusSettlesDown(FocusManagerImpl.java:162)
        at com.intellij.openapi.actionSystem.impl.ToolbarUpdater.updateActions(ToolbarUpdater.java:94)
        at com.intellij.openapi.actionSystem.impl.ToolbarUpdater.access$400(ToolbarUpdater.java:26)
        at com.intellij.openapi.actionSystem.impl.ToolbarUpdater$MyTimerListener.run(ToolbarUpdater.java:144)
        at com.intellij.openapi.actionSystem.impl.WeakTimerListener.run(WeakTimerListener.java:35)
        at com.intellij.openapi.actionSystem.impl.ActionManagerImpl$MyTimer.runListenerAction(ActionManagerImpl.java:1545)
        at com.intellij.openapi.actionSystem.impl.ActionManagerImpl$MyTimer.notifyListeners(ActionManagerImpl.java:1534)
        at com.intellij.openapi.actionSystem.impl.ActionManagerImpl$MyTimer.actionPerformed(ActionManagerImpl.java:1518)
        at javax.swing.Timer.fireActionPerformed(Timer.java:313)
        at javax.swing.Timer$DoPostEvent.run(Timer.java:245)
        at java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:311)
        at java.awt.EventQueue.dispatchEventImpl(EventQueue.java:764)
        at java.awt.EventQueue.access$500(EventQueue.java:98)
        at java.awt.EventQueue$3.run(EventQueue.java:715)
        at java.awt.EventQueue$3.run(EventQueue.java:709)
        at java.security.AccessController.doPrivileged(Native Method)
        at java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(ProtectionDomain.java:74)
        at java.awt.EventQueue.dispatchEvent(EventQueue.java:734)
        at com.intellij.ide.IdeEventQueue.defaultDispatchEvent(IdeEventQueue.java:933)
        at com.intellij.ide.IdeEventQueue._dispatchEvent(IdeEventQueue.java:810)
        at com.intellij.ide.IdeEventQueue.lambda$dispatchEvent$8(IdeEventQueue.java:469)
        at com.intellij.openapi.progress.impl.CoreProgressManager.computePrioritized(CoreProgressManager.java:705)
        at com.intellij.ide.IdeEventQueue.dispatchEvent(IdeEventQueue.java:468)
        at java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:205)
        at java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:116)
        at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:105)
        at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:101)
        at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:93)
        at java.awt.EventDispatchThread.run(EventDispatchThread.java:82)

I'm also having the issue in 3.6.0 Beta 5 but there I'm only seeing the stacktrace not the log about the navigation xml file.

Let me know if I can provide more info to you.

Thank you for the information! Let's follow up on https://issuetracker.google.com/issues/143828478, which is reserved exclusively for the manifest / navigation issues.
Indeed, the stack trace you posted also stems from the same issue with manifest merging. If you're re-opening the same project you were using in 4.0 in 3.6 Beta 5, try File > Invalidate Caches / Restart. From what I've seen locally, this should get things working again in 3.6 (please do confirm or deny on the other bug after you've tried it :) ).

From this point forward, I'd like to reserve this bug solely for tracking the original "Multiple entries with same key" issue described in #24. If anyone is seeing the "Default activity not found" issue under different circumstances, please file a separate bug and we will triage appropriately.