Bug 4892 - Getting Error when binding the Google Analytics jar file with Mono for Android 4.1.1
Summary: Getting Error when binding the Google Analytics jar file with Mono for Androi...
Alias: None
Product: Android
Classification: Xamarin
Component: General ()
Version: 4.1.x
Hardware: Macintosh Mac OS
: --- normal
Target Milestone: ---
Assignee: Bugzilla
Depends on:
Reported: 2012-05-04 16:56 UTC by Chris Hardy [MSFT]
Modified: 2012-05-11 08:16 UTC (History)
3 users (show)

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:

Description Chris Hardy [MSFT] 2012-05-04 16:56:50 UTC
I get the following error when binding the Android Google Analytics JAR file:

/Users/chrisntr/Projects/GoogleAnalytics/GoogleAnalytics/obj/Debug/generated/src/Com.Google.Android.Apps.Analytics.GoogleAnalyticsTracker.cs(135,135): Error CS0234: The type or namespace name `IDispatcherCallbacks' does not exist in the namespace `Com.Google.Android.Apps.Analytics'. Are you missing an assembly reference? (CS0234) (GoogleAnalytics)

Example binding project here: http://dl.dropbox.com/u/90453/GABinding.zip
Comment 1 Jonathan Pryor 2012-05-04 20:25:54 UTC
Fixed in ebb76970.
Comment 2 Atsushi Eno 2012-05-07 05:03:22 UTC
It is reopened for... some reason?
Comment 3 Jonathan Pryor 2012-05-07 13:12:14 UTC
It's reopened because the fix wasn't a fix. :-)
Comment 4 Atsushi Eno 2012-05-08 03:41:55 UTC
FYI this kind of issue could be workarounded by adding <remove-node /> metadata.
Comment 5 Atsushi Eno 2012-05-11 08:16:50 UTC
Fixed in master (post-4.2).