Bug 37527 - BI1029 Internal error CoreIsProtocolizedEventBacked unable to find property
Summary: BI1029 Internal error CoreIsProtocolizedEventBacked unable to find property
Status: VERIFIED FIXED
Alias: None
Product: iOS
Classification: Xamarin
Component: General ()
Version: XI 9.4 (iOS 9.2)
Hardware: PC Mac OS
: Normal normal
Target Milestone: (C7)
Assignee: Manuel de la Peña [MSFT]
URL:
Depends on:
Blocks:
 
Reported: 2016-01-08 17:18 UTC by John Miller [MSFT]
Modified: 2016-05-17 15:18 UTC (History)
5 users (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:
VERIFIED FIXED

Description John Miller [MSFT] 2016-01-08 17:18:22 UTC
**Overview:**

   The attached binding project has a build error when trying to compile. 

**Steps to Reproduce:**

   1. Build the attached project. 

**Actual Results:**

   > warning BI1029: btouch: Internal error: CoreIsProtocolizedEventBacked unable to find property: Delegate on ExactTarget.ETPushSdk.ETBulkUpdateShim

**Expected Results:**

   No build errors. 

**Build Date & Platform:**

   XI 9.4
Comment 2 Saurabh 2016-01-12 08:46:08 UTC
I have checked this issue by building the attachment project mentioned in the comment 1 and observed that I am able to reproduce this issue.


Build output: https://gist.github.com/saurabh360/1e3a773ea0e952483928

IDE Log: https://gist.github.com/saurabh360/6c7b3e256f3df20ed051

Environment info 

=== Xamarin Studio ===

Version 5.10.2 (build 49)
Installation UUID: 91997f85-0008-4b4c-9f53-c7f991fcdae3
Runtime:
	Mono 4.3.2 (master/58d269c)
	GTK+ 2.24.23 (Raleigh theme)

	Package version: 403020270

=== Xamarin.Profiler ===

Version: 0.24.354.0
Location: /Applications/Xamarin Profiler.app/Contents/MacOS/Xamarin Profiler

=== Xamarin.Android ===

Version: 6.0.1.5 (Trial Edition)
Android SDK: /Users/360_macmini/Desktop/AndroidSDK
	Supported Android versions:
		2.3    (API level 10)
		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)
		5.0    (API level 21)
		5.1    (API level 22)
		6.0    (API level 23)

SDK Tools Version: 24.4
SDK Platform Tools Version: 23.0.1
SDK Build Tools Version: 23.0.1

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)

=== Xamarin Android Player ===

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

=== Apple Developer Tools ===

Xcode 7.2 (9548)
Build 7C68

=== Xamarin.iOS ===

Version: 9.4.1.20 (Trial Edition)
Hash: 122b860
Branch: master
Build date: 2016-01-05 20:20:30-0500

=== Xamarin.Mac ===

Version: 2.4.1.5 (Starter Edition)

=== Build Information ===

Release ID: 510020049
Git revision: deed4cd240ff3611c8742bbc62296e207f46173d
Build date: 2015-12-17 11:13:36-05
Xamarin addins: 8bd975e7b465f6fe812b64d736f3b7e8c1a79a3e
Build lane: monodevelop-lion-cycle6-c6sr1

=== Operating System ===

Mac OS X 10.10.5
Darwin Apple-iMac.local 14.5.0 Darwin Kernel Version 14.5.0
    Tue Sep  1 21:23:09 PDT 2015
    root:xnu-2782.50.1~1/RELEASE_X86_64 x86_64
Comment 3 Sebastien Pouliot 2016-01-13 20:26:26 UTC
> warning BI1029: btouch: Internal error: CoreIsProtocolizedEventBacked unable to find property: Delegate on ExactTarget.ETPushSdk.ETBulkUpdateShim

It looks like a binding error (in user code) but we should not be reporting this as a warning that refers to an internal error.
Comment 4 Sebastien Pouliot 2016-02-05 19:24:57 UTC
To clarify: there are errors in the binding project.

The bug is how we're reporting the first one. It's confusing because:

* we say it's a warning, but we throw an error;
* the message include types from the generator (it's not meant for the user);
* the additional data is not very help (for the customer);


To solve this we need to:

1. Figure out the mistake. In this case the ETBulkUpdateShim binding is missing 

		[Wrap ("WeakDelegate")]
		ETGenericUpdateObjectProtocol Delegate { get; set; }

so the `Delegates = new[] { "WeakDelegate" }` and `Events =...` has meaning.


2. Express this properly in the error message

3. Change this from a warning (bool parameter)

4. Add a unit test for the generator, see maccore/tests/generator
Comment 5 Manuel de la Peña [MSFT] 2016-03-01 09:34:02 UTC
Fix in master/8e30027bf2fb1a62b0cb5e78f48335e97cb8b535 and cycle7/0aabe37f4387b52dc3bf19f80e1daa4c372073a7
Comment 6 Sunil Kumar 2016-05-17 14:29:22 UTC
Hi,

I have checked this issue with latest C7 XamarinStudio-6.0.0.5156_6bb41168165682b4ed22a94364bf0cf24e6b1d5c and xamarin.ios-9.8.0.318_efefc1edafbccb25395796b2a4f594c420f37bb3 and observed that now it is showing new warning as below

> warning BI1113: btouch: BaseType.Delegates were set but no properties could be found. Do ensure that the WrapAttribute is used on the right properties.

Is it expected behaviour? please confirm

Previously it was showing warning as mentioned in comment 3.

Build output: https://gist.github.com/sunil360/ea0e33fcb15527a9dea5b9cd74adacee

Environment info: 
https://gist.github.com/sunil360/febc2a2560ad1888d6850ee4a50bee39
Comment 7 Manuel de la Peña [MSFT] 2016-05-17 14:38:25 UTC
Yes, that is the expected behaviour, the compilation error has to happen with the error string:

warning BI1113: btouch: BaseType.Delegates were set but no properties could be found. Do ensure that the WrapAttribute is used on the right properties.

The bug was that the error was misleading.
Comment 8 Sunil Kumar 2016-05-17 15:18:52 UTC
As per comment 7, It is the expected behaviour. Hence I am closing this issue marking it as VERIFIED.