Bug 19762 - Should check that Activities/etc. only contain ASCII, and error if they don't.
Summary: Should check that Activities/etc. only contain ASCII, and error if they don't.
Alias: None
Product: Android
Classification: Xamarin
Component: MSBuild ()
Version: 4.12.4
Hardware: PC Mac OS
: Normal enhancement
Target Milestone: ---
Assignee: Jonathan Pryor
Depends on:
Reported: 2014-05-14 08:49 UTC by narayanp
Modified: 2015-04-13 15:57 UTC (History)
3 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 for Bug 19762 on Developer Community or GitHub if you have new information to add and do not yet see a matching new report.

If the latest results still closely match this report, you can use the original description:

  • Export the original title and description: Developer Community HTML or GitHub Markdown
  • Copy the title and description into the new report. Adjust them to be up-to-date if needed.
  • Add your new information.

In special cases on GitHub you might also want the comments: GitHub Markdown with public comments

Related Links:

Description narayanp 2014-05-14 08:49:16 UTC
Steps to reproduce:
1.Create Android template with Cyrillic character like 'Ӛ' or 'ӛ'
2. Run the application.

Actual Result: It builds successfully but deployment failed internal error. 

Expected Result: Application should deployed and launched successfully with Cyrillic character.

Supplement info:
Deploy to device output: https://gist.github.com/saurabh360/d9140763814e1694c32f
adb logcat: https://gist.github.com/saurabh360/29424f82133a0f58363a

Environment details:
X.S 5.0(Build 869)
Git revision: 2c44a2f074583892493ac44676d8a1ba05aae12d
X.Android 4.12.4-10

Regression status: 
NOT A REGRESSION: Same behavior happening with stable X.S 4.2.5(Build 0) and X.Android 4.12.3-3
Comment 1 Akhilesh kumar 2014-10-30 11:05:56 UTC
I have try to reproduce this issue with latest Stable builds but I am getting a new issue Bug 24162.

So as of now I am leaving this issue as NEW.
Comment 2 Akhilesh kumar 2014-10-30 11:27:58 UTC
An other update regarding this issue. We are able to reproduce this issue with application having whole solution name(like "ӚӚӚӚӚӚ") of Cyrillic characters.

Application output: 

Detecting installed packages
Waiting for packaging to complete
Installing application on device
Deployment failed because of an internal error: Unexpected install output: 	pkg: /data/local/tmp/x______.x______-Signed.apk
Deployment failed. Internal error.

Screencast: http://screencast.com/t/ERXOhveM2rqJ
Build output: https://gist.github.com/saurabh360/5c38b900451fa83d5701
IDE log: https://gist.github.com/saurabh360/3c1b4cb44273c16e74f1

Environment info:
=== Xamarin Studio ===

Version 5.5.3 (build 6)
Installation UUID: ff0c16c6-3c75-46d8-ac56-56c3b56e2c76
	Mono 3.10.0 ((detached/e204655)
	GTK+ 2.24.23 (Raleigh theme)

	Package version: 310000023

=== Apple Developer Tools ===

Xcode 6.0.1 (6528)
Build 6A317

=== Xamarin.Android ===

Version: 4.18.0 (Indie Edition)
Android SDK: /Users/360_macmini/Desktop/android-sdk-macosx
	Supported Android versions:
		2.1    (API level 7)
		2.2    (API level 8)
		2.3    (API level 10)
		3.1    (API level 12)
		3.2    (API level 13)
		4.0    (API level 14)
		4.0.3  (API level 15)
		4.1    (API level 16)
		4.2    (API level 17)
		4.3    (API level 18)
		4.4    (API level 19)
		4.4.87 (API level 20)
		4.5    (API level 21)
Java SDK: /usr
java version "1.7.0_65"
Java(TM) SE Runtime Environment (build 1.7.0_65-b17)
Java HotSpot(TM) 64-Bit Server VM (build 24.65-b04, mixed mode)

=== Xamarin.iOS ===

Version: (Trial Edition)
Hash: 08968c4
Build date: 2014-10-20 21:48:06-0400

=== Xamarin.Mac ===

Version: (Indie Edition)

=== Build Information ===

Release ID: 505030006
Git revision: fbe3e9453daf6a3bb9a9709ed22bec35f7c9056b
Build date: 2014-10-23 13:08:38-04
Xamarin addins: e44add2b39de4dd57c0742bb2e620dfad84c64c6

=== Operating System ===

Mac OS X 10.10.0
Darwin Apples-iMac.local 14.0.0 Darwin Kernel Version 14.0.0
    Fri Sep 19 00:26:44 PDT 2014
    root:xnu-2782.1.97~2/RELEASE_X86_64 x86_64
Comment 3 Jonathan Pryor 2015-04-13 15:57:55 UTC
This is actually a Android-ism: Android requires that all classes specified within AndroidManifest.xml -- <activity/>s, <service/>s, etc. -- must ONLY contain ASCII characters. Ditto the package name.

Failure to do so results in an Android package installation error:

> W/PackageParser(  281): /data/app/vmdl-715088571.tmp (at Binary XML file line #5): <activity> does not have valid android:name

Our AndroidManifest.xml generator should check the generated type names to double check that the resulting names only contain ASCII characters, and "do something" if they don't (replace them? error?).