apple-push-notifications

问题 I'm trying to set up push notifications through Amazon SNS in Unity. I have the Android side of things working perfectly but we're having issues with iOS. I am able to get the device to register to a Apple Production SNS application and subscribe to a topic but as soon as I attempt to send a notification the endpoints "Enabled" status becomes "False". I read that this could be due to the certificate being set as Production although we followed the instructions on creating a Development

问题 I'm trying to set up push notifications through Amazon SNS in Unity. I have the Android side of things working perfectly but we're having issues with iOS. I am able to get the device to register to a Apple Production SNS application and subscribe to a topic but as soon as I attempt to send a notification the endpoints "Enabled" status becomes "False". I read that this could be due to the certificate being set as Production although we followed the instructions on creating a Development

问题 // Register for notifications [[UIApplication sharedApplication] registerForRemoteNotificationTypes:( UIRemoteNotificationTypeAlert | UIRemoteNotificationTypeBadge | UIRemoteNotificationTypeSound | UIRemoteNotificationTypeNewsstandContentAvailability)]; This is the code I use for registering for registering for push notifications. The app registers for Alert, Badges, Sound. But the app did not register for the newsstand push notifications. Checked it in

问题 I am new to the APNS certificate thing. My question is a old developer lost our Private Key which we used for several in-house (ad-hoc) applications, and an application we use to push out applications and policies to users. I know that the only way to get the private key is to revoke the certificate and then generate a new one and re-sign all the internal applications and re-deploy with the new cert. My only concern is what happens to the application that uses APNS, does this still use the

问题 Does anyone know where the vulnerabilities are in Apple's APN push notification services? We can ensure that our notifications are sent securely to Apple, so we just need to know whether they can be intercepted from that point? Motivation: We have built an iOS messaging app that we are making as a 100% secure solution, with some features that have never been exploited before in security. 回答1: Apple released the UNNotificationServiceExtension last year, allowing developers to send fully

问题 I am currently facing a problem with push notifications in iOS. My app receives silent push notifications containing an identifier. This identifier is then used to fetch data from a remote server from which a local notification is created. As far as I'm aware, if the user has force-quit an app (i.e. by double tapping the home button and swipe closing the app) then the silent push notification does not get passed onto the didReceiveRemoteNotification method in the AppDelegate class [1] [2],

问题 I've developed an iOS app, that receives Push Notifications. I'm sending them from a .NET environment using PushSharp. Everything went beautifully while developing, and the Pushs were successfully sent: var push = new PushBroker(); var appleCert = File.ReadAllBytes(@"Utils\Cert.Development.p12"); push.RegisterAppleService(new ApplePushChannelSettings(false, appleCert, "*******")); push.QueueNotification(new AppleNotification() .ForDeviceToken(token) .WithContentAvailable(1) ); push

问题 I am listneing to actions pressed for my local notifications, but is there a way to determine when the user dismisses a notification? Here is how I'm listening to my actions in my AppDelegate, but the dismiss doesn't fire this: func application(application: UIApplication, handleActionWithIdentifier identifier: String?, forLocalNotification notification: UILocalNotification, completionHandler: () -> Void) { var actionName: String? = nil if let identifier = identifier { switch identifier { case

问题 I'm sending my push notifications with an APNs Auth Key ("never expires") which worked well until suddenly I get 403 Forbidden: {"reason":"InvalidProviderToken"} as a response when sending push notifications. What could be the reason for this when it worked once and suddenly it doesn't without having an expiration date? In the meantime it worked again for some pushes, but now I get the error again... Did anyone else experience this? EDIT Not sure but it seems as if this only happens on the

问题 I am researching server side development of Apple Push Notifications in Java. I am using the enhanced format, in order to detect failed messages and resend messages that follow bad messages. I know that Apple to not guarantee the delivery of Push Notifications, but I wish to be able to know whether Apple received my messages and whether the contained any errors. I noticed that when I try to send an invalid message (invalid device token, too large payload, etc...) to Apple, I can send several