Bug 46968 - Notification Service Extension is not being triggered
Summary: Notification Service Extension is not being triggered
Status: RESOLVED DUPLICATE of bug 43985
Alias: None
Product: iOS
Classification: Xamarin
Component: General ()
Version: XI 10.4 (C9)
Hardware: Macintosh Mac OS
: --- normal
Target Milestone: (C10)
Assignee: Bugzilla
URL:
Depends on:
Blocks:
 
Reported: 2016-11-14 23:28 UTC by Artur Malendowicz
Modified: 2016-11-15 06:38 UTC (History)
2 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:
RESOLVED DUPLICATE of bug 43985

Description Artur Malendowicz 2016-11-14 23:28:54 UTC
Since yesterday I am struggling with implementing service extension to notifications. After following tutorials I am unable to trigger did receive on service. Push contains mutable-content : 1, has no content available and is set to display alert which it does but without changing body which had to be done in service. Both projects are developer mode with separate provisioning profiles. Regards.
Comment 1 Alex Soto [MSFT] 2016-11-15 06:38:45 UTC
This is currently being investigated by our team

*** This bug has been marked as a duplicate of bug 43985 ***