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.
For example, INActivateCarSignalIntentHandling_Extensions.ConfirmActivateCarSignal actually checks whether the signals can be activated, and not whether they have been activated.
I believe this is true across the namespace, but it may be necessary to go case by case.
On further review, this may not be the case at all. INPayBillIntentHandling_Extensions.ConfirmPayBill confirms details with the user, which leads me to believe that, in general, it is not a capability that is being confirmed, but permission and/or details.
Well I have the simple solution to this:
_Which turns out to also be the name of the Swift version._
Let's review them all, `ConfirmPayBill` in Swift is also `Confirm`.
Some of those are not new API in xcode9 (e.g. `ConfirmPayBill`) and cannot be changed without breaking API.
@Alex please double check the new API to see if Vincent's suggestion can be applied. Thanks!
In Progress -> https://github.com/xamarin/xamarin-macios/pull/2591
Fixed in xamarin-macios/xcode9 @ 17a7b1c386572788dba119bc18414f2c31afad62