Bug 11608 - <activity-alias> should be moved after its android:targetActivity
Summary: <activity-alias> should be moved after its android:targetActivity
Alias: None
Product: Android
Classification: Xamarin
Component: MSBuild ()
Version: 4.7.x
Hardware: PC Windows
: Normal normal
Target Milestone: ---
Assignee: Radek Doulik
Depends on:
Reported: 2013-04-05 07:30 UTC by softlion
Modified: 2017-09-01 07:09 UTC (History)
6 users (show)

Is this bug a regression?: ---
Last known good build:

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and Mono organizations on GitHub to continue tracking issues. Bugzilla will remain available for reference in read-only mode. We will continue to work on open Bugzilla bugs, copy them to the new locations as needed for follow-up, and add the new items under Related Links.

Our sincere thanks to everyone who has contributed on this bug tracker over the years. Thanks also for your understanding as we make these adjustments and improvements for the future.

Please create a new report on Developer Community or GitHub with your current version information, steps to reproduce, and relevant error messages or log files if you are hitting an issue that looks similar to this resolved bug and you do not yet see a matching new report.

Related Links:

Description softlion 2013-04-05 07:30:37 UTC
When an <activity-alias> is manually added in AndroidManifest.xml, 
the project compiles and links, but when deploying on a device it fails:

Deployment failed because of an internal error:

Comment 1 Radek Doulik 2013-05-03 09:14:19 UTC
I have fixed it in master branch.

commit 2e7fcccc9b7ce069ad4852c546fcb3cfd58370a9
Comment 2 softlion 2013-05-10 10:53:43 UTC
Could you fix it in alpha and beta chanches ?

Thank you ...
Comment 3 softlion 2013-05-10 10:55:50 UTC
I need it in alpha channel in fact ...
Comment 4 Radek Doulik 2013-05-10 15:50:20 UTC
Yes, it will be included in the next version 4.7.5, which will be available through the alpha channel.
Comment 5 narayanp 2013-05-23 07:42:47 UTC
Today we have checked this issue with following builds:

X.S 4.0.7
Mono 3.0.11
Xamarin.Android 4.6.7-4

And we have followed some steps:

1. Create Android application.
2. Added AndroidManifest.xml file.
3. Added following code in this file:
<activity-alias android:label="HelloAndroid" android:icon="@drawable/icon">
4. Debug/Run the application.

We are getting Deployment failed internal error "Failure [INSTALL_PARSE_FAILED_MANIFEST_MALFORMED]"

Hence reopening this issue.
Comment 6 Radek Doulik 2013-05-23 11:20:32 UTC
Hopefully there will be Xamarin.Android 4.7.5 in the alpha channel today, which has the fix.
Comment 7 Atin 2013-08-02 09:20:06 UTC
Today we have checked this issue with following builds:

X.S 4.0.11(build 6)
Mono 3.2.1 ((no/f3f789e)
Xamarin.Android 4.8.1-13

This issue still exists, We are getting Deployment failed internal error "Failure

Hence reopening this issue.
Comment 8 Francesco Pretelli 2015-01-06 23:35:35 UTC
I'm experiencing the same issue, is this bug still open?
Comment 9 softlion 2017-09-01 07:09:38 UTC
Seems finally fixed ...