Wrong Activity is use for launch when there is an alias [162259273]

Fixed

Bug

Status Update

No update yet.

Description

[Deleted User]

created issue #1

Jul 29, 2020 03:00PM

Build: AI-201.8538.31.41.6692364, 202007191539,

AI-201.8538.31.41.6692364, JRE 1.8.0_242-release-1644-b01x64 JetBrains s.r.o, OS Windows 10(amd64) v10.0 , screens 2560x1440

AS: 4.1 Beta 5; Kotlin plugin: 1.3.72-release-Studio4.1-5; Android Gradle Plugin: 4.1.0-beta04; Gradle: 6.5; NDK: from local.properties: (not specified), latest from SDK: (not found); LLDB: pinned revision 3.1 not found, latest from SDK: (package not found); CMake: from local.properties: (not specified), latest from SDK: (not found), from PATH: (not found)

EXPECTED: When running application from IDE, it should launch that application after successful build and install. ACTUAL: When run app button is clicked, application is successfully built and installed on the device but is not launched automatically and has to be started manually.

Run window output:

07/29 16:37:47: Launching 'app' on Pixel 3a API 29.
Timed out waiting for process (com.avast.android.vpn) to appear on Pixel_3a_API_29 [emulator-5554].
Install successfully finished in 16 m 40 s 193 ms.

Build window output:

BUILD SUCCESSFUL in 2m 36s
42 actionable tasks: 28 executed, 11 from cache, 3 up-to-date

Comments

uc...@google.com <uc...@google.com> #2Jul 29, 2020 04:22PM

Thanks for the feedback. To help us troubleshoot this issue further, we will need more information. Please share detailed reproduction steps and as much as possible of the following information when it applies if you haven’t already:

1. Android Studio version and OS type and version
2. Screenshots or videos of the issue
3. idea.log file (select Help > Show Log in Finder / Explorer)
4. Thread dumps if the issue is a freezing or non-responding UI.

For more information on what’s needed and how to obtain this information please read the guide at

https://developer.android.com/studio/report-bugs#studio-bugs

[Deleted User] <[Deleted User]> #3Jul 30, 2020 06:53AM

It is already in original comment
I would rather not, since I would have to redact quite a lot. But pls let me know if steps to reproduce are not clear enough.
Added as attachment
Not eligible

idea.log

954 KB

View

Download

uc...@google.com <uc...@google.com> Jul 30, 2020 05:11PM

Assigned to an...@google.com.

ac...@google.com <ac...@google.com> #4Jul 30, 2020 05:19PM

Reassigned to Deleted User.

I suspect this is a dup of

bug 160269604

.

Are you able to attach the logcat to this bug?

If not, can you look into the logcat to see if you have the same issue as the aforementioned bug?

In particular, look for something like "I/ActivityManager: Force stopping <package-name> appid=10080 user=0: pkg removed" after Studio relaunched the application?

[Deleted User] <[Deleted User]> #5Jul 31, 2020 07:34AM

It does look similar but in my case force stop happens before app is started.

2020-07-31 09:24:31.063 2043-3227/? I/ActivityManager: Force stopping com.avast.android.vpn appid=10329 user=0: from pid 30222
2020-07-31 09:24:31.071 2304-2304/? D/CarrierSvcBindHelper: No carrier app for: 0
2020-07-31 09:24:31.106 2043-5127/? I/ActivityTaskManager: START u0 {act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] flg=0x10000000 cmp=com.avast.android.vpn/.activity.OnboardingActivity} from uid 2000
2020-07-31 09:24:31.106 2043-5127/? W/ActivityTaskManager: Permission Denial: starting Intent { act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] flg=0x10000000 cmp=com.avast.android.vpn/.activity.OnboardingActivity } from null (pid=30231, uid=2000) not exported from uid 10329

But I see now that it failed because of Permission Denial and found this Stackoverflow issue that helped me: https://stackoverflow.com/a/22929102/862024

To give some context, this is our AndroidManifest definition of Launcher activity:

        <!-- This activity alias is needed for proper migration from ASL 1.0 Where activity of this name is the launcher activity,
        therefore we need this for preserving launcher icon. -->
        <activity-alias
            android:name=".app.wizard.WizardActivity"
            android:label="@string/main_title"
            android:launchMode="singleTop"
            android:targetActivity=".activity.OnboardingActivity">
            <intent-filter>
                <action android:name="android.intent.action.MAIN" />

                <category android:name="android.intent.category.LAUNCHER" />
                <category android:name="android.intent.category.LEANBACK_LAUNCHER" />
                <category android:name="android.intent.category.DEFAULT" />
            </intent-filter>
        </activity-alias>

        <activity
            android:name=".activity.OnboardingActivity"
            android:label="@string/main_title"
            android:launchMode="singleTop"
            android:theme="@style/Theme.Vpn.SplashScreen" />

For some reason AS chose OnboardingActivity as a default activity instead of WizardActivity. If I change run configuration to launch WizardActivity instead, it works as expected and run also launches application automatically.

ac...@google.com <ac...@google.com> #6Jul 31, 2020 05:04PM

Reassigned to sa...@google.com.

Thanks for for looking into this for us.

There are some recently restructure on how Studio picks out Activity to launch. May be it is not dealing with alias well?

sa...@google.com <sa...@google.com> #7Aug 3, 2020 11:36PM

I am able to reproduce the issue on my end. The problem is that our apk based AndroidManifest.xml parser is resolving activity-alias (.app.wizard.WizardActivity -> .activity.OnboardingActivity) when building the list of candidate activities.

These should **not** be resolved but returned as declared. e.g: In #5 example, the list to be returned should not be only #1:.activity.OnboardingActivity

but

#1:.activity.OnboardingActivity
#2:.app.wizard.WizardActivity

A CL is on the way to address this issue.

sa...@google.com <sa...@google.com> #8Aug 10, 2020 05:23PM

Marked as fixed.

Fixed in Android Studio 4.1 RC 1

ha...@gmail.com <ha...@gmail.com> #9Aug 12, 2020 10:15AM

This is still an issue in 4.1 RC1. If launcher activity is an activity-alias it won't start the app on run.

jo...@google.com <jo...@google.com> Aug 12, 2020 02:33PM

Status: Assigned (reopened)

sa...@google.com <sa...@google.com> #10Aug 12, 2020 05:16PM

I am unable to reproduce this issue on my side.

#9 Can you share the AndroidManifest.xml or a MWE so I can see what is wrong? idea.log would also help.

Message last modified on Aug 12, 2020 05:17PM

sa...@google.com <sa...@google.com> #11Aug 12, 2020 10:28PM