we have developed an application that use push notifications by following the very good guide created by David Mytton.
The push service worked great on the development profile. But now that it is finished we have changed to the customers distribution profile. The application is an in-house application using an Enterprise account.
We have changed the certificate on the server and we have changed to the production url as specified in the tutorial. We have also replaced the profile used when building the application and installed it to the tester iPhone. Everything seems to work on the server, and no error messages is returned but the push is never recieved on the iPhone. We are pretty clueless right now and don't know where to start debugging on this. We have checked that the tokenId is updated after replacing the profile.
Has anyone any experience in this and might know what's wrong or where to start debugging? Thanks!
I have no idea what was wrong here but i finally got it to work..
After hours of debugging without results i threw in the towel and created a new developer certificate, app id, push sertificate and distribution profile. I cleaned the project added the new profile and replaced all files on server.
And it worked! No problems at all... Sometimes i hate being an iPhone/Apple developer :\
A few things that you could try:
Make sure your phone is plugged in to a power source (sometimes not having this causes delayed notifications).
Use the following PHP library:
http://code.google.com/p/php-apns/
This allows you to debug the communication with the server and see where the error occurs. Specifically it allows you to debug if your token id is incorrect.
You could try using an incorrect token id on the server and see the behavior. Compare this with using the correct token id.
Any in-house distribution profile gives out a same tokenID, how ever
this tokenID varies across different devices.
Other only issue could be only with the ProductionURL.
I have also notices that the push notification reception is delayed sometimes, mostly when used with production URL.
Hope this helps.
Related
Hello to all
I am new in Amazon Alexa, I have a work to Alexa Skill account linking using PHP with oauth 2.0.
I have successfully configured all and also get code for Auth Code Grant but when I run my code in Chrome Browser it is generating Account linking Failed issue but when I run same URL in Firefox it generates Amazon linking failed with ERROR=missing-state.
Please help me to resolve my issue, any help would be highly appreciated.
Implementing Account Linking is tricky at times. The thing is at some point what happens between Alexa and the OAuth2 server is transparent for the Skill (Lambda), for example the process of refreshing a token among others, that is why I suggest you take a look at the references cited below.
Also because of the error shown, it seems that the parameter code is missing in one of the URLs exchanged back and forth between either the Alexa web console or Alexa mobile app and the OAuth2 server. Please verify it is always the same and is always present in the URLs. Implementing a proxy for sure will help on debugging this issue.
I would suggest you take a look at these great sources:
Debugging Account Linking
Using API Gateway to Debug Account Linking issues
I hope this helps somehow.
Cheers
I have recently joined a startup who has been using an offshore team up until now. Our app in built in Obj-C with a PHP backend, both of which I am fairly new to (I come from a JS background). I have been wanting to make some alterations to the current in-app notifications (banners), but have been unable to figure out how to test them. I am aware that testing notifications on the simulator is not possible, and have installed the developer build to my device. However, I am still not receiving any notifications when I would normally receive them in the production build, such as when a friend posts a message. If anyone has any experience with this I would love to hear it. I am currently developing in Xcode 8.2.1
This might get closed as too broad a question, but for what it's worth here are some checkpoints:
The app is enabled for notifications in iPhone Settings
The app is requesting a push token from APNS
(registerForRemoteNotificationTypes)
It receives a valid token from APNS and
passes it to your PHP server (didRegisterForRemoteNotificationsWithDeviceToken)
Your server is storing the token correctly
Your server is triggering a push notification correctly
Your development certificate is correct
(read this post iPhone APNS Device Tokens in sandbox vs. production)
If you want to test push without the server in the loop, checkout PushMeBaby (there are several on GitHub).
try it:
if app is already launched in App Store: they enabled the production certificated ... and u r running the application through Xcode ,u will not get the notifications in ur device... for that u need to create IPA file for ur project and run through iTunes...
Ok, so I have setup a Docusign Connect to a 3rd party application (Infusionsoft) and have it working great.
They don't natively work together, so I created a php script that reads the tabs in the docusign envelope, and passes it to Infusionsoft, along with a copy of the completed envelope itself.
Now I would like to pass payment info through this as well, as one of the document templates I have in Docusign is a billing agreement. I have done a test run of this with dummy info and I am able to do this well, BUT, I now have to be concerned with PCI compliance on this, right?
I have a dedicated server with a domain that has an SSL certificate which is hosting the php script, which does not store any information. It just passes the docusign info (gathered by using the docusign connect) and then formats it so it can be accepted by Infusionsoft.
I am a novice programmer, and pretty ignorant regarding knowledge behind encrypting data or securing a connection. The fact that Docusign passes the info through an XML file seems to be not ideal for handling sensitive data (at least I would imagine), and that is something that is out of my control.
So what I am asking is would it be possible to securely transmit payment info (credit card or bank account) through a Docusign connect connection in the type of setup I have? If so, how would I approach it? I am open to hiring a programmer if needed or getting a different server setup if it was necessary.
I can do this without adding the payment info to the template, and just adding it afterwards directly into Infusionsoft to limit my liability, but it would be so much easier if I could do it directly through Docusign Connect as it would automate the entire sign up process.
Well Comodo's test turned up a bunch of holes and warnings, with a detailed report of what to fix. I took that in turn to Hostgator support, who went ahead and made the appropriate changes to fix the holes. The also reported that their were a bunch of false positives with supporting documentation.
So I have to do another test to verify that everything was closed up and report the false positives. But other than that it seems like it should all be cleared up.
I also spoke with Docusign Support over the phone about this, and they confirmed other companies are doing what I am doing as well, which was reassuring.
So in short, use Comodos online scan tool to see what holes you have. Then contact your hosting company to fix the holes. Not a great answer, but I suppose better than nothing.
I have developed a simple app for iPad which has push notifications in it as a feature.
I created its app id and enabled the push notifications and downloaded the certificates for development as well as distribution.
I created .pem files for both as well.
While using development profile, everything worked fine and push notifications were working perfect.
But when I started checking it with distribution profile push notifications didn't come.
I also got the php file changed and removed sandbox from it. I checked everything but I cannot seem to find what is missing.
Do we need to do anything exclusive for Enterprise apps for enabling push notifications in them?
Thanks in advance.
Best regards
I built a project last year that had some basic facebook features, such as fetching a user's name, email, and importing his friends. That project is still working, however the client contacted me to tell me that Facebook's API has changed and I need to update the code before the legacy support goes away.
I can't find any mention of such changes, can someone point me to see what has changed and how I can update the code?
You may follow next topics to get informed about API and functionality changes:
Change Log
Developer Roadmap
Completed Changes