Bug 24482 - SecureTextEntry is viral to surrounding text fields
Summary: SecureTextEntry is viral to surrounding text fields
Status: RESOLVED UPSTREAM
Alias: None
Product: iOS
Classification: Xamarin
Component: General ()
Version: XI 8.4.0
Hardware: PC Mac OS
: Normal normal
Target Milestone: Untriaged
Assignee: Paola Villarreal
URL:
Depends on:
Blocks:
 
Reported: 2014-11-13 00:38 UTC by Cody Beyer (MSFT)
Modified: 2014-11-23 22:46 UTC (History)
3 users (show)

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


Attachments
TestCase2 (225.67 KB, application/zip)
2014-11-13 00:38 UTC, Cody Beyer (MSFT)
Details
Objective-c test case. Proofs that the problem is iOS' instead of Xamarin.iOS' (79.16 KB, application/zip)
2014-11-23 22:45 UTC, Paola Villarreal
Details


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 UPSTREAM

Description Cody Beyer (MSFT) 2014-11-13 00:38:11 UTC
Created attachment 8713 [details]
TestCase2

### Description

When having two fields, one for username and one for password, where the later is set to SecureTextEntry = true, if the same values are entered in both fields, and then focus is switched between them, the non secure field gets replaced with secure characters. 

### Video

https://www.dropbox.com/s/czzhkrvqhnstnph/PasswordFields.mov?dl=0

### TestCase

Attached

### Steps to Reproduce

1. Open attached test case
2. Run in Simulator
3. Enter same value in both fields
4. Switch focus between fields
5. Notice the username field eventually becomes blocked out with secure placeholders

### Version

=== Xamarin Studio ===

Version 5.5.4 (build 13)
Installation UUID: 3e4348fa-e0b3-46a4-8426-58f27e19159e
Runtime:
	Mono 3.10.0 ((detached/771f43f)
	GTK+ 2.24.23 (Raleigh theme)

	Package version: 310000030

=== Apple Developer Tools ===

Xcode 6.1 (6604)
Build 6A1052d

=== Xamarin.iOS ===

Version: 8.4.0.38 (Business Edition)
Hash: 9e57461
Branch: 
Build date: 2014-11-10 21:18:38-0500

=== Xamarin.Android ===

Version: 4.20.0.24 (Business Edition)
Android SDK: /Users/codybeyer/Library/Developer/Xamarin/android-sdk-macosx
	Supported Android versions:
		4.0.3  (API level 15)
		4.4.87 (API level 20)
Java SDK: /usr
java version "1.8.0_25"
Java(TM) SE Runtime Environment (build 1.8.0_25-b17)
Java HotSpot(TM) 64-Bit Server VM (build 25.25-b02, mixed mode)

=== Xamarin.Mac ===

Version: 1.10.0.18 (Business Edition)

=== Build Information ===

Release ID: 505040013
Git revision: e3f694bbe83524db6d7e8cae11bff54773daf8ab
Build date: 2014-11-10 04:11:00-05
Xamarin addins: f7574394ab210968f35256aa4ff98f7bf4ed7fa9

=== Operating System ===

Mac OS X 10.10.0
Darwin Codys-MacBook-Pro.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 1 Rajneesh Kumar 2014-11-13 02:04:02 UTC
I have checked this issue and able to reproduce. To reproduce this issue I have followed the steps mentioned in bug description.
I observed that when I enter same values in both fields and then switch focus between both fields notice the username field eventually becomes blocked out with secure placeholders.

Note: In the attached test case there are two solution and I am able to reproduce this issue on both.

Screencast(TestPasswordProblem): http://www.screencast.com/t/51iLBqqh

Screencast(TestPasswordProblem2): http://www.screencast.com/t/Ypdfqx5gr

Additional Information: I observed that if I enter the different values in both fields, and then focus is switched between them, the non secure field does't gets replaced with secure characters. 
Screencast: http://www.screencast.com/t/83msGuicAJ

Ide log: https://gist.github.com/Rajneesh360Logica/da25cfb31d80fe8c57c5

Environment Info:

=== Xamarin Studio ===

Version 5.5.3 (build 6)
Installation UUID: 011d70a5-dede-428b-ab04-ef451c2e539d
Runtime:
	Mono 3.10.0 ((detached/e204655)
	GTK+ 2.24.23 (Raleigh theme)

	Package version: 310000023

=== Xamarin.Android ===

Version: 4.18.1 (Business Edition)
Android SDK: /Users/MM/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)

=== Apple Developer Tools ===

Xcode 6.1 (6604)
Build 6A1052d

=== Xamarin.iOS ===

Version: 8.4.0.16 (Business Edition)
Hash: 80e9ff7
Branch: 
Build date: 2014-10-22 15:09:12-0400

=== Xamarin.Mac ===

Version: 1.10.0.18 (Business 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.9.5
Darwin MacMini.local 13.4.0 Darwin Kernel Version 13.4.0
    Sun Aug 17 19:50:11 PDT 2014
    root:xnu-2422.115.4~1/RELEASE_X86_64 x86_64
Comment 2 Paola Villarreal 2014-11-23 22:45:45 UTC
Created attachment 8845 [details]
Objective-c test case. Proofs that the problem is iOS' instead of Xamarin.iOS'
Comment 3 Paola Villarreal 2014-11-23 22:46:45 UTC
Upstreaming this bug as it is an iOS problem, not Xamarin.iOS (I attached an xcode project that proofs this :)