Test Push Notification in Sandbox?

Hey there!
I need some support regarding the testing of Push Notifications in a Developer-Viewer App.
I enabled the push notification in itunes connect and downloaded and coverted all the certificates, but a notification is not showing up.
In itunes connect i registered an in-app-purchase (status: waiting for screenshot): with the name: ClientSubscription. In The Folioproducer I gave the current issue the product id: dev_test.ClientSubscription. In the DPS App Builder I inserted "ClientSubscription" in the Subscription field.
Did I do something wrong? How can I test push-messages on a developer-viewer?
And another Question: Is there a way to test subscriptions in the dev-viewer, too?
Thanks!
florian
P.S. I already found that tutorial, but I am stuck at bullet 6...: http://www.adobe.com/devnet/digitalpublishingsuite/articles/dps-push-notification.html#art iclecontentAdobe_numberedheader_3

Similar Messages

504 error testing Push Notification

When I run the following
"Test-CsMcxPushNotification -AccessEdgeFqdn [EdgeInternalFQDN]"
I get the following error:
Test-CsMcxPushNotification : A 504 (Server time-out) response was received from
the network and the operation failed. See the exception details for more infor
mation.
At line:1 char:27
+ Test-CsMcxPushNotification <<<< -AccessEdgeFqdn elync.middleearth.prv
    + CategoryInfo          : OperationStopped: (:) [Test-CsMcxPushNotificatio
   n], FailureResponseException
    + FullyQualifiedErrorId : WorkflowNotCompleted,Microsoft.Rtc.Management.Sy
   ntheticTransactions.TestMcxPushNotificationCmdlet
Tracing SIP stuff on my Edge server I see this (that coincides):
Trace-Correlation-Id: 2779320912
Instance-Id: 00006455
Direction: incoming;source="external edge";destination="internal edge"
Peer: sipfed.online.lync.com:5061
Message-Type: response
Start-Line: SIP/2.0 504 Server time-out
From: <sip:[email protected]>;epid=071FC4CDE8;tag=d5de7ce9d
To: <sip:[email protected]>;tag=59FEE19DFF45B9B833CFBD36F5844FB6
CSeq: 1 MESSAGE
Call-ID: 55054a3cda594233865f9404fb67c370
Via: SIP/2.0/TLS xx.xx.xx.x:49740;branch=z9hG4bK19F43140.4A6F7CB75D069D34;branched=FALSE;ms-internal-info="aiR0Dj4wu8N2n-MrxwEJfnT_JZa9t_uWycL8Xcpz6MWCO3fG9K-ro3zQAA";received=207.46.5.9;ms-received-port=49740;ms-received-cid=50E0A00
Via: SIP/2.0/TLS xx.xx.xx.xxx:62314;branch=z9hG4bKe4c031fd;ms-received-port=62314;ms-received-cid=18B00
Server: RTC/4.0
Content-Length: 0
Message-Body: –
$$end_record
Any thoughts on why I'm getting this 504 error? Don't have a phone setup yet to test but thought I'd get these tests straightened out first.
thanks
Steve

well, here are the important details from the full SipStack trace not much to go on really. It looks like a good TLS connection is established but then my Edge server never hears back. So, any thoughts are greatly appreciated
Steve
TL_INFO(TF_DIAG) [0]0618.0650::12/19/2011-21:04:50.346.0000005e (SIPStack,SIPAdminLog::TraceDiagRecord:SIPAdminLog.cpp(147))$$begin_record
LogType: DNS
Severity: information
Text: DNS query was successfully resolved
Query: sipfed.online.lync.com
Query-Type: A
Query-Result: 207.46.5.22
Origin: [email protected]
Query-Time: 47
TTL: 300
$$end_record
TL_INFO(TF_DIAG) [0]0618.0650::12/19/2011-21:04:50.444.00000061 (SIPStack,SIPAdminLog::TraceDiagRecord:SIPAdminLog.cpp(147))$$begin_record
LogType: DNS
Severity: information
Text: DNS query against a negative record was successfully resolved
Query: domain.local
Query-Type: SRV
Origin: [email protected]
Query-Time: 94
TTL: 30
$$end
TL_INFO(TF_DIAG) [0]0618.0650::12/19/2011-21:04:50.529.00000065 (SIPStack,SIPAdminLog::TraceDiagRecord:SIPAdminLog.cpp(147))$$begin_record
LogType: DNS
Severity: information
Text: DNS query was successfully resolved
Query: push.lync.com
Query-Type: SRV
Query-Result: sipfed.online.lync.com:5061
Origin: [email protected]
Query-Time: 93
TTL: 300
$$end_record
TL_INFO(TF_CONNECTION) [0]0618.0650::12/19/2011-21:04:50.588.0000006c (SIPStack,SIPAdminLog::TraceConnectionRecord:SIPAdminLog.cpp(164))$$begin_record
LogType: connection
Severity: information
Text: TLS negotiation started
Local-IP: xxx.xxx.28.1:49271
Peer-IP: 207.46.5.22:5061
Peer-FQDN: sipfed.online.lync.com
Connection-ID: 0x11F02
Transport: TLS
$$end_record
TL_INFO(TF_PROTOCOL) [0]0618.0650::12/19/2011-21:04:50.822.00000078 (SIPStack,SIPAdminLog::TraceProtocolRecord:SIPAdminLog.cpp(125))$$begin_record
Trace-Correlation-Id: 129864885
Instance-Id: 000024BE
Direction: outgoing;source="local";destination="external edge"
Peer: sipfed.online.lync.com:5061
Message-Type: request
Start-Line: NEGOTIATE sip:127.0.0.1:5061 SIP/2.0
From: sip:sip.domain.com;tag=53AA4068ECBD5322E4BD76F15422FDE1
To: sip:sipfed.online.lync.com
CSeq: 1 NEGOTIATE
Call-ID: A20CA980901275ED4EE7
Via: SIP/2.0/TLS xxx.xxx.28.1:49271;branch=z9hG4bK0B3F19AC.71A937A4D1326122;branched=FALSE
Max-Forwards: 0
Compression: LZ77-64K
Supported: NewNegotiate,OCSNative,ECC
Server: RTC/4.0
Content-Length: 0
Message-Body: –
$$end_record
TL_INFO(TF_PROTOCOL) [0]0618.0E08::12/19/2011-21:04:50.876.0000007c (SIPStack,SIPAdminLog::TraceProtocolRecord:SIPAdminLog.cpp(125))$$begin_record
Trace-Correlation-Id: 1522472405
Instance-Id: 000024BF
Direction: incoming;source="external edge";destination="internal edge"
Peer: sipfed.online.lync.com:5061
Message-Type: response
Start-Line: SIP/2.0 200 OK
From: sip:sip.domain.com;tag=53AA4068ECBD5322E4BD76F15422FDE1
To: sip:sipfed.online.lync.com;tag=59FEE19DFF45B9B833CFBD36F5844FB6
CSeq: 1 NEGOTIATE
Call-ID: A20CA980901275ED4EE7
Via: SIP/2.0/TLS xxx.xxx.28.1:49271;branch=z9hG4bK0B3F19AC.71A937A4D1326122;branched=FALSE;received=207.46.5.9;ms-received-port=49271;ms-received-cid=CDCF000
Compression: LZ77-64K
Supported: NewNegotiate,OCSNative,ECC
Server: RTC/4.0
Content-Length: 0
Message-Body: –
$$end_record
TL_INFO(TF_CONNECTION) [0]0618.0E08::12/19/2011-21:04:50.876.00000082 (SIPStack,SIPAdminLog::TraceConnectionRecord:SIPAdminLog.cpp(164))$$begin_record
LogType: connection
Severity: information
Text: Connection established
Local-IP: xxx.xxx.28.1:49271
Peer-IP: 207.46.5.22:5061
Peer-FQDN: sipfed.online.lync.com
Peer-Name: sipfed.online.lync.com
Connection-ID: 0x11F02
Transport: M-TLS
$$end_record
TL_INFO(TF_DIAG) [0]0618.0E08::12/19/2011-21:04:50.877.00000089 (SIPStack,SIPAdminLog::TraceDiagRecord:SIPAdminLog.cpp(147))$$begin_record
LogType: diagnostic
Severity: information
Text: The message has a Hosting Service domain
SIP-Start-Line: OPTIONS sip:[email protected] SIP/2.0
SIP-Call-ID: 5ca29c1a88c84cfca6fd0316ed39b8c2
SIP-CSeq: 1 OPTIONS
Peer: sipfed.online.lync.com:5061
Data: domain="push.lync.com"
$$end_record
TL_INFO(TF_DIAG) [0]0618.0E08::12/19/2011-21:04:50.877.0000008b (SIPStack,SIPAdminLog::TraceDiagRecord:SIPAdminLog.cpp(147))$$begin_record
LogType: diagnostic
Severity: information
Text: Routed a request to a Hosting Service federated peer
SIP-Start-Line: OPTIONS sip:[email protected] SIP/2.0
SIP-Call-ID: 5ca29c1a88c84cfca6fd0316ed39b8c2
SIP-CSeq: 1 OPTIONS
Peer: sipfed.online.lync.com:5061
Data: destination="sipfed.online.lync.com"
$$end_record
TL_INFO(TF_PROTOCOL) [0]0618.0E08::12/19/2011-21:04:50.877.0000008d (SIPStack,SIPAdminLog::TraceProtocolRecord:SIPAdminLog.cpp(125))$$begin_record
Trace-Correlation-Id: 3725312887
Instance-Id: 000024BD
Direction: outgoing;source="internal edge";destination="external edge"
Peer: sipfed.online.lync.com:5061
Message-Type: request
Start-Line: OPTIONS sip:[email protected] SIP/2.0
From: <sip:[email protected]>;epid=DF5A96419D;tag=a9cd3a7a1
To: <sip:[email protected]>
CSeq: 1 OPTIONS
Call-ID: 5ca29c1a88c84cfca6fd0316ed39b8c2
Record-Route: <sip:sip.domain.com:5061;transport=tls;epid=DF5A96419D;lr;ms-key-info=AAEAAb4x_MMw6VRGh77MARgJlzjQGKMNpr9JOZp2chRj79PZlYPcyanbg4evMeIGX3zJVqtwUSOvDfOyIeiTPwsLqMy03N31Xtqkto_QP9kWylFMuD5ALlppkclERF3TGzmRcxVR9f75lnZfiz8mw8WuLJGSdzl08HwCR2q_bxWQiwH3w8LGy_LYWck2COKLPL-1yqURh-oAxAzu2EtOUbketZj9CLdR7NvkhGQnmUQDXXOitgyubvEaCx7ylDpe_Lvatt5jNgQlwgd-3yodQLj2KjbwguhhjNkCAmK1EXGweI8BVOGKCLBwVrvRUn-1WFOv79gdJdwJqchNFE0Gmjye8MEqRuWBaxzTQlUFUVwU6mJo3r-KgWhHDNAewBLSz4nGtk-Bd9PnTLkdjI4R1q5XRZOrhKz2pbskw3zaMAtA2TchCCi4QFe3FwpSsHyc1QakjQ2AtQDvrffBSpBkPxqdl7iJ6S2iYbxSoSW98AinW5-RPJQBAPI_0B-kn9I7q815jIacb3SUm6lQ47z2jCuuAGi9U0f4rwAvv5dzp-p47qZc1K1g8NmYhCBUNgPCzOrSJcSVTYA-hZd4CyLoHPmlQrSXSSf4_WmYdq1Y_vr2QnOUS1OE0ZGf9gOA1KutkVo_m1NvJgFA-WjAr8etm4GmyjbNHPdciJWxbcHgxumetO6SmTXjo9Eexh3fvwxF;ms-route-sig=dabFjLEcvse3_IUujeUVfvGK4BW1PdduNoVAJIBqhU3P-Vk5Jo5cppegAA>;tag=53AA4068ECBD5322E4BD76F15422FDE1
Via: SIP/2.0/TLS xxx.xxx.28.1:49271;branch=z9hG4bKA3BF6DE5.68929395D1123122;branched=FALSE;ms-internal-info="ckyE6xefajCWJiMl9wCFIy8vK1FepWApL0P_7wKVtUx36Vk5JoVVxTlAAA"
Max-Forwards: 69
Via: SIP/2.0/TLS 172.16.0.145:55661;branch=z9hG4bK351168b7;ms-received-port=55661;ms-received-cid=11E00
ROUTE: <sip:sipfed.online.lync.com;transport=tls;lr>;ms-edge-route
CONTACT: <sip:Lync.domain.local;ms-fe=Istar.domain.local;transport=Tls>
CONTENT-LENGTH: 0
USER-AGENT: RTCC/4.0.0.0
ms-asserted-verification-level: ms-source-verified-user=verified
Message-Body: –
$$end_record
TL_INFO(TF_PROTOCOL) [0]0618.0650::12/19/2011-21:04:51.064.00000090 (SIPStack,SIPAdminLog::TraceProtocolRecord:SIPAdminLog.cpp(125))$$begin_record
Trace-Correlation-Id: 3098643150
Instance-Id: 000024C0
Direction: incoming;source="external edge";destination="internal edge"
Peer: sipfed.online.lync.com:5061
Message-Type: response
Start-Line: SIP/2.0 504 Server time-out
From: <sip:[email protected]>;epid=DF5A96419D;tag=a9cd3a7a1
To: <sip:[email protected]>;tag=59FEE19DFF45B9B833CFBD36F5844FB6
CSeq: 1 OPTIONS
Call-ID: 5ca29c1a88c84cfca6fd0316ed39b8c2
Via: SIP/2.0/TLS xxx.xxx.28.1:49271;branch=z9hG4bKA3BF6DE5.68929395D1123122;branched=FALSE;ms-internal-info="ckyE6xefajCWJiMl9wCFIy8vK1FepWApL0P_7wKVtUx36Vk5JoVVxTlAAA";received=207.46.5.9;ms-received-port=49271;ms-received-cid=CDCF000
Via: SIP/2.0/TLS 172.16.0.145:55661;branch=z9hG4bK351168b7;ms-received-port=55661;ms-received-cid=11E00
Server: RTC/4.0
Content-Length: 0
Message-Body: –
$$end_record

Push notifications not working with production (apnagent nodes Js)

Hi,
When we tested the push notification in sandbox using apnagent node JS it worked well. But when we switch the sandbox to production it is not working. When we debug the server side we are not getting any errors also in production, but push notifications are delivered to the devices.
First we thought it is a certificate issues and then revoked all the certificates in the portal and created new certificates still no luck.
Can any one tell me why push notifications are not working in production.
Thanks in advance!

You're welcome. The request has been sent in. I first saw your post in the Using Apple Support Communities Forum, now I see it's been moved to the iPod Forum, hopefully it will get moved again.
iIt's been moved.

Universal Apps and Push Notifications (Question on both Store and Phone app)

I have a Universal App and trying to implement notifications. I have an Azure Notification Hub and the code in the app.xaml.cs (shared) file that is creating the channel and binding to my notification hub. This all works great for the Windows Store app.
However, I don't receive any notifications on the Phone app (running in the emulator). I am wondering if this is because the code to create the PushNotificationChannel is only registering once (the Store app) and has the same URI as the phone app. This line
of code is what I am referring to:
var channel = await PushNotificationChannelManager.CreatePushNotificationChannelForApplicationAsync();
Since this is by application, and I am essentially running the same app twice on the same machine, via the phone emulator, is only one URI being generated for this?
Thanks for any assistance.

When you created the push notifications in the Azure, you chose the code fr Windows Store, not Windows Phone. as you mentioned you having a universal apps.
Hint: Did you enabled push notifications for local testing ?
This is the 4 steps to have a successful Push notification integration with your app
Register your app for push notifications
Update the service to send push notifications
Enable push notifications for local testing
Test push notifications in your app
For more info please follow this
link

Push notification feedback problem

Hello everybody. I've installed on my iPhone ad-hoc version, so it means distribution one. I've downloaded apns-shart library and tried to test push notifications on that. I have all necessary certificates. I've succeeded to push notifications using test notification project and with this everything is fine. My problem is: when I've tried to use test feedback project it fetched needed device tokens, but when I've tried to launch it second time, it return 0 bytes. What can I do to fix the problem.

Well if you are a developer then you should know this isn't the forum for development help. They have their own forum. This is for user to user help with just how to use the phone.

Newsstand push notification

How to test push notifications and background downloading for newsstand?
Is there a way to check if the certificates are all right?
What to do if the the notification doesnt work?
Best jan

The answer to this is right here on DPS Devnet http://www.adobe.com/devnet/digitalpublishingsuite/articles/dps-push-notification.html

Are any Houston Chronicle for iPad readers not reliably receiving their daily push notification from the app?

Ever since the update to ios 7, the push notification from the Chronicle has been VERY unreliable. Is anybody else having a similar experience?

Hi,
1. Did you install any protection application on you iphone?
2. Please try to test push notification to see if any error message is received when Lync 2010 is disappeared from notification setting.
Test-CsMcxPushNotification -AccessEdgeFqdn <Access Edge service FQDN>
Regards,
Kent Huang
TechNet Community Support ************************************************************************************************************************
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question.

Push notifications never appear once choosing "Don't Allow" at first run

For applications that use push notifications such as fring or Ping!, when I choose "Don't Allow (push notifications)" at the first run of each application, the options to turn push notifications back on (or off) at Settings > Notifications will never be found there, resulting in not receiving any push forever, even when you change your mind to get push!
Is there any way to correct this? I tried to delete the application and reinstall but still no push is coming. Thank you.

Hi,
1. Did you install any protection application on you iphone?
2. Please try to test push notification to see if any error message is received when Lync 2010 is disappeared from notification setting.
Test-CsMcxPushNotification -AccessEdgeFqdn <Access Edge service FQDN>
Regards,
Kent Huang
TechNet Community Support ************************************************************************************************************************
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question.

Push Notification pushes only doom

I'm trying to get push notification working correctly on my server. I seem to have hit a snag.
Facts:
-DNS for the server is correct (verified with changeip -checkhostname)
-Forward and reverse lookups are correct for server
-Pubsub DNS record is published and correct
-xmpp-server and xmpp-client records are published and tested
-Push Notification is enabled for the iCal server and Mail Server and correctly displays in server admin. I can see the com.apple.notificationuser connecting successfully to xmpp.
-Firewall ports are open and correct
-XMPP has a password in my keychain for the XMPP notification service
-Network capture verifies that when I run the iCal client, it connects to port 5223 of the server. However, at the same time, the server logs this and push fails to work for that client:
Jul 13 21:58:10 internal jabberd/c2s[8883]: [12] [::ffff:<myClientIP>, port=32787] connect
Jul 13 21:58:10 internal jabberd/c2s[8883]: ODKVerifyClientRequestFixed: Unable to authenticate
Jul 13 21:58:10 internal jabberd/c2s[8883]: [12] [::ffff:<myClientIP>, port=32787] disconnect jid=unbound, packets: 0
Note: <myClientIP> was substituted for my IP address of the system that executed the iCal client.
Likewise, Mail server logs a 404 error to XMPP every time I receive an email:
Jul 13 21:57:03 internal push_notify[15477]: error: <iq id='10009' to='[email protected]/push_notify' type='error' from='pubsub.internal.red-abstract.com' xmlns='jabber:client'><error type='cancel' code='404'><item-not-found xmlns='urn:ietf:params:xml:ns:xmpp-stanzas'/></error><pubsub xmlns='http://jabber.org/protocol/pubsub'><publish node='/Public/IMAP/internal.red-abstract.com/portnum/Mailbox/9EE76D0A-E16C-4D92 -B789-360B82C0BB58'><item><plistfrag xmlns='plist-apple'/></item></publish></pubsub></iq>
Clearly, something isn't right here, but I cannot unravel what it is. It seems jabberd/c2s is trying to perform some trick of authentication but it is not succeeding. Server is running 10.6.4.
Has anyone gotten this to work successfully? Verified it with a network capture?
Note that the ODKVerifyClientRequestFixed only logs when an iCal client connects and tries to set up a push session.
BTW, I'm NOT trying to get this to work on iPhones or iPads. I know that does not work. I'm merely trying to get it working with the iCal and Mail clients on the Mac desktops.
Message was edited by: Vermyndax

More interesting data...
If I visit /etc/jabberd/c2s.xml and comment out the line:
<digest-md5>
...for SASL authentication, then when I restart jabber/notification and connect with iCal, I get a different error in system.log, but it's related:
Jul 14 23:27:14 internal jabberd/c2s[90905]: [11] [::ffff:24.96.15.52, port=44572] connect
Jul 14 23:27:14 internal jabberd/c2s[90905]: Password verification failed
Jul 14 23:27:14 internal jabberd/c2s[90905]: [11] [::ffff:24.96.15.52, port=44572] disconnect jid=unbound, packets: 0
I see that even though the notification user opens a session, for some reason the iCal server doesn't get it right. This makes me wonder if the iCal server is trying to bind to the XMPP server with a bad username or password. This log tidbit is prior to the auth error above:
Jul 14 23:27:05 internal jabberd/c2s[90905]: odauth_check_servicemembership: checking user "com.apple.notificationuser" access for service "chat"
Jul 14 23:27:05 internal jabberd/c2s[90905]: odauth_check_servicemembership: mbrcheck_servicemembership returned 0
Jul 14 23:27:05 internal jabberd/c2s[90905]: odauth_check_servicemembership: user "com.apple.notificationuser" is authorized to access service "chat"
Jul 14 23:27:05 internal jabberd/c2s[90905]: [10] SASL authentication succeeded: mechanism=PLAIN; [email protected], TLS negotiated
Jul 14 23:27:05 internal jabberd/c2s[90905]: odauth_check_servicemembership: checking user "com.apple.notificationuser" access for service "chat"
Jul 14 23:27:05 internal jabberd/c2s[90905]: odauth_check_servicemembership: mbrcheck_servicemembership returned 0
Jul 14 23:27:05 internal jabberd/c2s[90905]: odauth_check_servicemembership: user "com.apple.notificationuser" is authorized to access service "chat"
Jul 14 23:27:05 internal jabberd/c2s[90905]: [10] bound: [email protected]/icalserver.20302838dfc b45e5bc5dab8e6e49afb0
Jul 14 23:27:05 internal jabberd/sm[90903]: session started: [email protected]/icalserver.20302838dfc b45e5bc5dab8e6e49afb0
The auth error occurs whenever someone runs an iCal client.

Push Notification questions

Hi,
I have been undergoing some push notification issues and I would like to have some doubts cleared out before taking incisive action;
- it seems that we cant get push notifications for a Newsstand app working on iPad1 with the latest supported iOS for this device installed (5.1.1). Is it an unsupported feature? Because it seems that it works fine on other devices with latest iOS installed;
- Also, some users complain they dont get push notifications delivered. I believe this is an users iPads configuration issue, since I get them working on some devices I checked, but it would be nice to have better arguments for it.
I would like to know if the Notify feature on DPS works only if user had not yet opened the app and received the custom notification for a new issue available for download. If, after checking it and downloading the issue, it wont receive the Notification through DPS and app wont show the bullett counter (or, if newsstand subscriber, the NEW banner wont be displayed on latest cover). Having this feature working on this scenario would help me on testing users notification issues;
- users complain that exclusively iPad mini dont get any notification at all. Their iPad mini rendition is adapted from the normal iPad (1024x768) - due to similarity in screen size and pixel density. I suppose it operates the same as the iPad, but I would like to check it anyway.
Thanks,
Pedro

http://www.adobe.com/devnet/digitalpublishingsuite/articles/dps-push-notification.html
Read :
1. Requirements for push and Newsstand background downloading.
2. How to test push notifications and background downloading

Push Notification Stop Automatically

Hi,
I have implemented push notification on my application, it was working fine on development and production environment. But push notification is stop automatically on my all devices for all runing and published application on both environment development and production.
After discussion with my provider, They ask all port are open for APNs. Also i am sure about firewall on my server. I am able to create all necessary certificates (SSL certificates) and getting device token from APNs sucessfully. My third party api is able to send notification sucessfully but am not able to get notification on device. My application is registered for push notification on my device.
According to following announcement by Apple :- https://developer.apple.com/news/?id=10222014a
But i am not able to test push notification immediately the development environment.
Please suggest us.

please contact Nimbuzz on this matter, as they are the developer of the application.

When sandbox is testing, the push notification is done.

Hi
How should I do so that the push notification is not done though am transmitted the push notification when contents are opened to the public when the sandbox is tested to add contents with InAppPuachase of iOS?
Please teach when there is understanding.
My best regards.

Pages that use "mixed content" (some parts of the page use HTTP and some use HTTPS) are not secure from tampering, so they will not show the site identity button. To fix this, make sure the external resources you are embedding are available over HTTPS, and that you are using HTTPS to embed them.
For example, for iframe widgets like the Facebook "Like" buttons, make sure that that your iframe uses src="https://..."
See also the discussion here: http://stackoverflow.com/questions/3587021/facebook-like-button-breaks-https-ssl

App testing phase: Push notifications are not getting delivered to certain devices (iphone 4S/ios7.0.4 and ios7.0.3 - Push never worked for these two devices for this app). Received OK responses from Apple PUSH services, but notifications not delivered

We are testing an app at work and Push notifications are not getting delivered to certain devices (iphone 4S/ios7.0.4 and ios7.0.3 - Push never worked for these two devices for this app). Received OK responses from Apple PUSH services, but notifications not delivered to these tow devices.
PUSH notification were delivered to some of the other iOS devices: (iPhone5 / iOS 6.1.4 and iPhone5 / iOS 7.0.3)

Sounds like you have a battry issue but don't want to believe it.
If a car was running fine on one tank of gas, then you filled it up with another tank of gas and it began to run funny, one might suspect that tank of gas. But let's just say coincidence blew a valve-- would you think the new tank of gas was the culprit?
BUT WAIT!! It just might have been! The gas could have been of higher octane and put more more strain on the valves; you know, like going from 87 octane (OS6) to 93 octane (OS7) and showing you the engine was on the edge of compromise.
Sometimes you have to go with common sense. If everything else is ruled out, it must be the battery. And if it runs fine one moment in OS6 but immediately ***** in OS7, I'd believe my battery was suspect-- though comfy-- in OS6 but the OS7 showed its true power.
Moreover, if you had the answer-- or didn't want to believe someone's more competent advice-- why did you even call? You've already shown that you don't know much when you asked if you could go backwards after setting up the new OS as a new phone.
Additonally, if you're such the know-it-all, but yourself the $29 battery and put it in yourself. It's a piece of cake.
<Edited By Host>

App does not send push notification when app gone live but was working fine when tested locally?

Please help us to get this solved. We tested the webserice URL which works okay. Port 2195 is also open. APN certificate is also not expired. What could be the problem that app when tested before live was sending push notification and when it is live, it has stopped!?

This would seem to be a question better posted in the App Developers forum.

Push Notifications to APNS Fail 50% of the Time

Sending a notification to an iOS device fails half the time with this error:
The Push Notification System returned an Internal Server Error
Here is my setup:
Free Trial version of Azure
Sandbox certificates uploaded to a Mobile Service/Notification Hub
App developed with PhoneGap and built using Adobe's PhoneGap Build service
Using the com.microsoft.azure-mobile-services Cordova plugin
I am able to use either the DEBUG page on the Azure site, Visual Studio 2013 (Server Explorer -> Azure), or the ServiceBusExplorer open source program to send test JSON messages to Apple. It works, half the time, and the other half of the time I
receive the error above.
Steps to reproduce:
Open Visual Studio --> Server Explorer --> Azure. It points to my trial account.
Context-click on my Notification Hub a pick "Diagnose"
Under Device Registrations, I delete any registrations I've previously accumulated. There are now no device registrations.
Delete and re-install the test app on the iPhone (iOS 8)
Launch the test app. A new registration appears in the notification hub. The type is "Native." (I've also had problems with "Template.")
Go to the Test Send tab; Recipient: Broadcast; Message Type: Apple (Default)
I am using the default, sample notification (but I get similar outcomes with other JSON messages):
{"aps":{"alert":"Notification Hub test notification"}}
Hit "Send"; It fails. Under "Message Result:," for my single registration I have this error message: "The Push Notification System returned an Internal Server Error"
Wait 90 seconds, hit Send again. The notification works, it appears on the phone, the message result is "The Notification was successfully sent to the Push Notification System"
Wait another 90 seconds, hit Send again. The notification fails
with the same Internal Server Error that it did the first time.
Wait another 90 seconds, hit Send again. It works perfectly just like it did on the second attempt.
Overall it is working about half the time. In the example above, it worked every-other time, but this is not always the case--it can succeed multiple times in a row or fail multiple times in a row. I'm not changing the JSON at all between
the above test messages. Even if I vary the JSON, I get the same outcome. I get similar outcomes regardless of whether I do the testing through Visual Studio (above), the Azure portal (the DEBUG tab), or through the ServiceBusExplorer program.
What is causing this? How do I troubleshoot this?

Hi David,
I don't have an answer for you, but I wanted to chime in because I am having problems as well. I get the same "The Push Notification System returned an Internal Server Error" message trying to send a test push via either the Debug tab in the manage.windowsazure.com
console or in Visual Studio.
I have been focused on troubleshooting this problem since yesterday (Saturday February 21) but I believe it has been happening quite a bit longer.
At one point I was able to get some notifications through after clearing all the registrations, but now it is failing again. I have had the same certificate since last April (2014) and it has worked fine, so I know the certificate setup is good.
More data points:
using the SimplePush PHP script from
raywenderlich.com with the same certificate, the notifications go through immediately.
Normally we send notifications from our Mobile Service using the Javascript backend, and it gets a "success" response from the Notification Hub even when it fails, e.g.
{"isSuccessful":true,"statusCode":201,"body":"","headers":{"transfer-encoding":"chunked","content-type":"application/xml; charset=utf-8","server":"Microsoft-HTTPAPI/2.0","date":"Sun,
22 Feb 2015 05:05:20 GMT"}}
We have another notification hub with our production certificate, and it seems to be working better.

Test Push Notification in Sandbox?

Similar Messages

Maybe you are looking for