Bug 40480 - FSharp syntax error: The type 'IJavaPeerable' is required here and is unavailable
Summary: FSharp syntax error: The type 'IJavaPeerable' is required here and is unavail...
Status: RESOLVED NOT_REPRODUCIBLE
Alias: None
Product: Android
Classification: Xamarin
Component: General ()
Version: unspecified
Hardware: Macintosh Mac OS
: --- normal
Target Milestone: ---
Assignee: Jonathan Pryor
URL:
Depends on:
Blocks:
 
Reported: 2016-04-18 11:03 UTC by Mitchell
Modified: 2017-06-28 11:02 UTC (History)
2 users (show)

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


Attachments
Screen Shot of the IJavaPeerable syntax error (87.37 KB, image/png)
2016-04-18 11:03 UTC, Mitchell
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 NOT_REPRODUCIBLE

Description Mitchell 2016-04-18 11:03:46 UTC
Created attachment 15750 [details]
Screen Shot of the IJavaPeerable syntax error

Xamarin syntax highlighting shows the error "Error: the type 'IJavaPeerable' is required here and is unavailable. You must add a reference to the assembly 'Java.Interop, Version=0.1.0.0, Culture=neutral,PublicKeyToken=84e04ff9cfb79065'.'

The 'IJavaPeerable' error appears on any F# class type that inherits a Java base class. But, it only appears in the syntax highlighting. The code will compile and run. I've yet to see any issues arise from this error at runtime, or compile time.


Environment

FSharp Path
/Library/Frameworks/Mono.framework/Versions/4.4.0/bin/fsharpi

Xamarin Studio Indie
Version 6.0 (build 4968)
Installation UUID: 42957e0c-6659-4ed3-9226-d287adc6c370
Runtime:
	Mono 4.4.0 (mono-4.4.0-branch/a3fabf1) (64-bit)
	GTK+ 2.24.23 (Raleigh theme)

	Package version: 404000122

Xamarin.Profiler
Not Installed

Xamarin.Android
Version: 6.1.0.37 (Xamarin Indie)
Android SDK: /Users/hynkle/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)
		6.0   (API level 23)

SDK Tools Version: 24.4.1
SDK Platform Tools Version: 23.1
SDK Build Tools Version: 23.0.1

Java SDK: /usr
java version "1.8.0_77"
Java(TM) SE Runtime Environment (build 1.8.0_77-b03)
Java HotSpot(TM) 64-Bit Server VM (build 25.77-b03, mixed mode)

Android Designer EPL code available here:
https://github.com/xamarin/AndroidDesigner.EPL

Xamarin Android Player
Version: 0.6.5
Location: /Applications/Xamarin Android Player.app

Apple Developer Tools
Xcode 7.3 (10183.3)
Build 7D175

Xamarin.iOS
Version: 9.8.0.244 (Xamarin Indie)
Hash: 977921b
Branch: cycle7
Build date: 2016-04-07 14:20:17-0400

Xamarin.Mac
Version: 2.8.0.244 (Xamarin Indie)

Build Information
Release ID: 600004968
Git revision: ab7092ce63351276394f283e4f9c8646baf51fce
Build date: 2016-04-08 09:30:34-04
Xamarin addins: be0a0aef6ec8b075b4ba4690bd147d1e33c2abd7
Build lane: monodevelop-lion-cycle7

Operating System
Mac OS X 10.11.4
Darwin Mitchells-MacBook-Pro.local 15.4.0 Darwin Kernel Version 15.4.0
    Fri Feb 26 22:08:05 PST 2016
    root:xnu-3248.40.184~3/RELEASE_X86_64 x86_64
Comment 1 Prashant [MSFT] 2017-06-28 11:02:40 UTC
Unfortunately, we’re unable to reproduce this report. If this issue is still occurring for you, please reopen this issue and attach a reproduction to the bug by starting with a clean Xamarin.Android project adding just the code necessary to demonstrate the issue.