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 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.
The error message is "The type 'SBNotificationHub' exists in both 'Microsoft.WindowsAzure.Messaging.iOS, Version=0.0.0.0, Culture=neutral, PublicKeyToken=null' and 'Xamarin.Azure.NotificationHubs.iOS, Version=0.0.0.0, Culture=neutral, PublicKeyToken=null' Sentry.iOS".
The code itself has not been changed; this is a new issue caused by external changes; Wednesday I upgraded both iOS and xCode on the development Mac to the latest versions.
WindowsAzure.Messaging is referenced in the code but 'Xamarin.Azure.NotificationHubs.iOS is not. If I remove the WindowsAsure.Messaging reference to reduce the references, the error changes to "The type or namespace name 'SBNotificationHub' could not be found (are you missing a using directive or an assembly reference?). Why is 'Xamarin.Azure.NotificationHubs.iOS not still referenced?
By removing the reference to Microsoft.WindowsAzure.Messaging.iOS, but retaining the 'using WindowsAzure.Messaging;' I got past the issue.
Is 'SBNotificationHub' now in the Xamarin.Azure.NotificationHubs.iOS but still reference by the above 'using'? Do we program it the same way?
Problem solved using comment above. Question not answered.
Unable to get past the issue:
The name 'SBConnectionString' does not exist in the current context
and / or