Bug 30025 - Comparing two numbers of type Decimal gives wrong results on Lollipop
Summary: Comparing two numbers of type Decimal gives wrong results on Lollipop
Status: RESOLVED DUPLICATE of bug 29570
Alias: None
Product: Android
Classification: Xamarin
Component: General ()
Version: 5.1
Hardware: Macintosh Mac OS
: --- normal
Target Milestone: ---
Assignee: Jonathan Pryor
URL:
Depends on:
Blocks:
 
Reported: 2015-05-13 07:22 UTC by Juro
Modified: 2015-05-13 10:59 UTC (History)
1 user (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 DUPLICATE of bug 29570

Description Juro 2015-05-13 07:22:41 UTC
After upgrading Xamarin.Android to 5.1, we started to experience the wrong results when comparing the negative decimal values. It seems that it ignores the negative sign.
E.g. (decimal)0 < (decimal)-1 is true or (decimal)-2 > (decimal)1 is true

It only happens on Lollipop devices (Nexus 7 with Android 5.1 and LG G3 with Android 5.0). It works well on KitKat.

Our build has armeabi, armeabi-v7a and x86 (it has no 64bit support). The Target API level is 21 (Android 5.0). Minimum API level is 10 (Android 2.3.3).

It happens with both Mac and Windows version of the Xamarin tools.

My config is:
Xamarin Studio
Version 5.9.1 (build 3)
Installation UUID: ae320932-d643-493d-bc90-afeb5e20e5c9
Runtime:
	Mono 4.0.0 ((detached/d136b79)
	GTK+ 2.24.23 (Raleigh theme)

	Package version: 400000143

Apple Developer Tools
Xcode 6.3.1 (7703)
Build 6D1002

Xamarin.iOS
Version: 8.10.0.267 (Business Edition)
Hash: 6481535
Branch: master
Build date: 2015-04-27 04:38:13-0400

Xamarin.Android
Version: 5.1.0.115 (Business Edition)
Android SDK: /Users/juro/Library/Developer/Xamarin/android-sdk-macosx
	Supported Android versions:
		2.3   (API level 10)
		4.0.3 (API level 15)
		4.4   (API level 19)
		5.0   (API level 21)
Java SDK: /usr
java version "1.7.0_76"
Java(TM) SE Runtime Environment (build 1.7.0_76-b13)
Java HotSpot(TM) 64-Bit Server VM (build 24.76-b04, mixed mode)

Xamarin Android Player
Version: Unknown version
Location: /Applications/Xamarin Android Player.app

Xamarin.Mac
Not Installed

Build Information
Release ID: 509010003
Git revision: aad75a6e7e48f18120ce41f47d0ff2c6216f49c3
Build date: 2015-05-08 12:46:18-04
Xamarin addins: 1246b3044cbb7f56a217334f8fc5489ef8eefe3f

Operating System
Mac OS X 10.10.3
Darwin 14.3.0 Darwin Kernel Version 14.3.0
    Mon Mar 23 11:59:05 PDT 2015
    root:xnu-2782.20.48~5/RELEASE_X86_64 x86_64
Comment 1 Jonathan Pryor 2015-05-13 10:59:23 UTC

*** This bug has been marked as a duplicate of bug 29570 ***