Bug 34893 - ReceivedRemoteNotification not firing when app is in background until user taps notification
Summary: ReceivedRemoteNotification not firing when app is in background until user ta...
Status: RESOLVED DUPLICATE of bug 34896
Alias: None
Product: iOS
Classification: Xamarin
Component: Xamarin.iOS.dll ()
Version: XI 9.4 (iOS 9.2)
Hardware: Macintosh Mac OS
: --- normal
Target Milestone: Untriaged
Assignee: Bugzilla
Depends on:
Reported: 2015-10-15 04:35 UTC by torch
Modified: 2016-12-22 09:08 UTC (History)
2 users (show)

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:

Description torch 2015-10-15 04:35:33 UTC
1) Notification arrives.
2) Notification alert/sound/badge works correctly and the notification is displayed to the user.
3) iOS's ReceivedRemoteNotification does not fire until the user taps the notification. When the notification is tapped, it fires which correctly initiates the sync.

But when I get back to the backgrounded app (or open a closed app) ReceivedRemoteNotification not firing.

ps. my app has the "Remote notifications" background mode enabled in the plist
Comment 1 Prashant [MSFT] 2016-12-22 09:08:51 UTC

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