Notice (2018-05-24): bugzilla.xamarin.com is now in
Please join us on
Visual Studio Developer Community and in the
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
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 54230 on
GitHub or Developer Community 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
In special cases on GitHub you might also want the comments:
GitHub Markdown with public comments
Start an android xamarin project on an android simulator on Wîndows, set a breakpoint anywhere and write in the immediate window:
Result is 132 instead of 131
Do the same with a windows test project.
Result is 131
This also happen when the calculation is put directly in Android code, thus is not a problem with the debugger.
Non-engineering team preliminary quick review
(See https://developer.xamarin.com/guides/cross-platform/troubleshooting/questions/howto-file-bug/ for general reference.)
## Suspected to be a regression or a problem with a new feature?
Uncertain. The issue is reported for the first time
## Specific to one particular project, development computer, or target mobile device?
I am able to reproduce this issue on Mono on Mac, and with Android project on Windows.
Note that this is affected only in `Immediate` Windows, the values correct when running within the app
## Includes clear steps to reproduce the problem?
## Considers the relevant log files for the part(s) of the process where something goes wrong (IDE editing, MSBuild building, deploying, launching, attaching the debugger, an in-app error, or something else), and has them attached?
No, but bug description is good enough to reproduce the issue
## Already took up time for many users?
Unclear. This is the only report I have seen for this issue and no other users are on the cc list for this bug report.
## Makes development (a) difficult, impossible, or potentially hazardous, (b) moderately inconvenient, or (c) mildly inconvenient for users?
I would say (c) based on the description
## Version Information
=== Xamarin Studio Enterprise ===
Version 6.2.1 (build 3)
Installation UUID: 31e31e77-8008-415b-a88b-44a133744a1b
Mono 4.8.0 (mono-4.8.0-branch/8f6d0f6) (64-bit)
GTK+ 2.24.23 (Raleigh theme)
Package version: 408000520
=== NuGet ===
=== Xamarin.Profiler ===
Location: /Applications/Xamarin Profiler.app/Contents/MacOS/Xamarin Profiler
=== Xamarin Inspector ===
Build date: Mon, 20 Mar 2017 02:36:23 GMT
=== Apple Developer Tools ===
Xcode 8.3 (12169)
=== Xamarin.Mac ===
Version: 18.104.22.1688 (Visual Studio Enterprise)
=== Xamarin.Android ===
Version: 22.214.171.124 (Visual Studio Enterprise)
Android SDK: /Users/prashantvc/Library/Developer/Xamarin/android-sdk-macosx
Supported Android versions:
6.0 (API level 23)
7.0 (API level 24)
SDK Tools Version: 25.2.5
SDK Platform Tools Version: 25.0.3
SDK Build Tools Version: 25.0.2
Java SDK: /usr
java version "1.8.0_101"
Java(TM) SE Runtime Environment (build 1.8.0_101-b13)
Java HotSpot(TM) 64-Bit Server VM (build 25.101-b13, mixed mode)
Android Designer EPL code available here:
=== Xamarin Android Player ===
=== Xamarin.iOS ===
Version: 10.6.0.10 (Visual Studio Enterprise)
Build date: 2017-03-28 00:48:33-0400
=== Build Information ===
Release ID: 602010003
Git revision: 5217903c99e9d9c5d3caa2498fd66d607debac29
Build date: 2017-03-23 12:36:46-04
Xamarin addins: 2c96d252b353fce2e8b8fd20884eee70c16c7f32
Build lane: monodevelop-lion-cycle9
=== Operating System ===
Mac OS X 10.12.4
Darwin Prashant-MBP.local 16.5.0 Darwin Kernel Version 16.5.0
Fri Mar 3 16:52:33 PST 2017
I also haven incorrect values in both the running app
And the debugger.
Using Math.Floor works as expected.
Tested on android simulator 5.1 (x86) and an android device
(32 bit Samsung s3 on android 7.1.1).
(In reply to softlion from comment #2)
> Tested on android simulator 5.1 (x86) and an android device
> (32 bit Samsung s3 on android 7.1.1).
Could you share the version information from Xamarin/Visual Studio? It will help us to debug this issue. You can find instructions here https://developer.xamarin.com/guides/cross-platform/troubleshooting/questions/version-logs/#Version_information
Ok happens only in the debugger.
Well no it happens in both debugger and app.
Xamarin Android 126.96.36.199