Bug 12923 - Android SDK throws errors with accent
Summary: Android SDK throws errors with accent
Status: RESOLVED NORESPONSE
Alias: None
Product: Android
Classification: Xamarin
Component: Tools and Addins ()
Version: 4.6.x
Hardware: PC Windows
: --- normal
Target Milestone: ---
Assignee: Jonathan Pryor
URL:
Depends on:
Blocks:
 
Reported: 2013-06-27 15:38 UTC by Allie Miller
Modified: 2013-12-05 18:36 UTC (History)
2 users (show)

Tags:
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:
Status:
RESOLVED NORESPONSE

Description Allie Miller 2013-06-27 15:38:50 UTC
I try to install and use Xamarin.Android. But the Android SDK cannot be set because my computer's name has an accent in it.  It says the path is not correct. After trying to move it to a location without the accented character, the issue remains. I do not have the option to choose the location to install.
Comment 2 Mikayla Hutchinson [MSFT] 2013-07-02 18:18:11 UTC
This appears to apply to the installer and androidtools, not just to XS.
Comment 3 Marek Habersack 2013-07-03 03:42:44 UTC
Allie, is it Windows or OSX? Can you provide a stack trace of the error, or a screenshot?
Comment 4 Mikayla Hutchinson [MSFT] 2013-07-09 19:49:38 UTC
We need the exact error messages.
Comment 5 PJ 2013-11-19 17:05:36 UTC
This bug has been in the NEEDINFO state with no changes for the last 90 days. Can we put this back into the NEW or CONFIRMED state, or are we still awaiting response?

If there is no change in the status of this bug over the next two weeks, this bug will be marked as NORESPONSE.
Comment 6 PJ 2013-12-05 18:36:03 UTC
This bug has not been changed from the NEEDINFO state since my previous comment, marking as RESOLVED NORESPONSE.

Please feel free to REOPEN this bug at any time if you are still experiencing the issue. Please add the requested information and set the bug back to the NEW (or CONFIRMED) state.