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.
Created attachment 11281 [details]
Email details of code and alernative bits tried.
This same code works still in the 32bit version. We've branched and updated to Unified.
Now when we call RegisterNativeAsync, the device token is passed, but the callback is never made. And in the Azure portal, the device token is missing, which means push notifications sent are not received.
We have also tried to non-async method.
Attached is a PDF with details and images of code snippets etc. from Ben Bishop who is lead dev on this.
It turns out based on Ben's analysis that RegisterNativeAsync needs to be called on the UI Thread. This solves the issue of the non-async method never issuing a callback.
Unfortunately since this is a Microsoft maintained component, we can't do much about the binding to this, but we can update our documentation to specify this.
To make matters more complicated, Microsoft now has a version 2.x of their mobile services which appears to merge messaging into the main component itself.
More analysis is needed on the best route forward, but for now the work around is to call the method on the UI Thread.
This is an issue with a microsoft component and the design of the API that they expose.
An new version of this components is available