I'm trying to implement push notification for an iPhone app using Urbanairship.
So, when I'm using ad hoc build (which is a different cert file), when I go to settings > notification, it is showing up there just fine.
However, with the app version that I put up on iTunes, I don't see my app name when I go to settings > notification. Neither did I get the popup that says, "Hey this app is going to send push notification, allow or disallow".
The only thing I can think off that might cause it is that, while in review, the SSL certificate expired. We have renewed that, but still no luck.
According to this link, How do I renew the SSL certificate for my ios push notification provider?, I don't have to resubmit. Or do I?
Thank you,
Tee
You need to create and issue a Production push cert. Then upload that to urban airship, and switch everything to use that cert for production mode.
Related
I am developing an iOS app which uses Push Notifications. I recently uploaded the first version to the App Store and I have turned on the Push Notifications in the Application Services in the app's App ID in Apple Developer Console. It says "Configurable" now. After that I got an email from Apple with a warning:
Missing Push Notification Entitlement - Your app includes an API for
Apple's Push Notification service, but the aps-environment entitlement
is missing from the app's signature. (...)
Then I found out that in XCode, on the Capabilities tab I need to enable Push Notifications. I did it, then created a new version and uploaded it, then I didn't get such a warning. Looks promising so far.
My problem is that I don't quite know where are the certificates for the APNs. I am using Firebase Cloud Messaging which requires to upload a development and a production certificate.
The internet is full of ways to create these certificates manually. Although Apple says always that XCode can do it automagically, which I'd prefer too. I just don't know where those are and whether created or not yet.
In Apple Developer console, I have two certificates created when I uploaded the first version of the app: a development and a distribution certificate. If I click on the APNs Auth Key, there's nothing displayed (not sure if it's a problem)
What do I need to do to automatically generate (or just find if done already) the certificates by XCode?
Any help is really appreciated.
For Push Service you have to create certificates manually and upload them to Firebase Console.
Ok, so I have an app that is in the app store. In development everything works fine I get all of the notifications that I send. I should mention that we are using Firebase for analyics and push notifications as we have a iOS and Android version of the app. Firebase account has both the correct development and correct production apns cert, the app's capabilities are set correctly to include push notifications and remote notifications in the background.
In the organizer window the entitlement for apns-environement is set to production whenever uploading to the app store or when exporting the app. Whenever the app is first installed and ran the alert to allow push notifications is shown. So my apns certs have to be configured correctly.
I am a working on contract for this company, just started 3 months ago, I would hate for these people to look at me in a bad light but I really don't know where the issue is. I am also using Xcode's automatic code signing option, with the correct provisioning profile and developer account signed in the Xcode on this mac.
Just went through this and I do not know if you solved this,
I turned push off and deleted the certs from apple dev center and created them all over again and this made everything work as it should.
I also had this line of code set to,
FIRInstanceID.instanceID().setAPNSToken(deviceToken as Data, type: FIRInstanceIDAPNSTokenType.sandbox)
I will change it to .prod when I push to the app store.
I've been working on an app for a while that uses push notifications from the chat module of QuickBlox.
I've been testing the push notifications on my iPad and it works fine (Developer Device). I've added both of the certificates to QuickBlox and both are active(Developer & Production).
The production devices are being registered for remote notifications and they are showing that they registered for production push notifications. When I send a message to a developer device it receives the notification and it works fine, however when I send to a production device its not received.
If I try to send a push notification to production users from the admin panel it gets sent, but non receive it. The production users are internal and external testers in TestFlight. I heard the TestFlight testers have to use a production certificate so thats why I'm registering them as so. When I archive the build going to the store I make sure that I do it using the production provisioning profile. I don't know what else to do :O
Thanks in advance
edit: I tried using push notification tester for the certificate and it worked fine. It pushed and the push notification was received to the production device. Still not working on QuickBlox
I tried to remove the certificate and then add it again, but that didn't help. I had to revoke my certificate then create a new one. After I added it, it took a good few hours until the notifications started to work. Must have been an issue with QuickBlox.
I have currently set up Parse Push notifications. I am running a beta with a few of my friends, and it seems that I am the only iPhone is that able to receive push notifications. The badge increments, sound and message, all is there for me.
On the Push tab in Parse the "Pushes Sent" column shows "1" for pushes sent to my iPhone, and "0" for Pushes sent from my iPhone.
We are all using the same build. And all have set notifications on in settings.
Any ideas why this is happening?
First of all, as your app is in Development Mode you should register your friends UDID'S in the Apple Developer Portal Devices Section.
Once you have done that, you should generate a new Development certificate now including your friends devices so they are also signed to receive the same services as you.
Check out one more time the Parse Certificates Tutorial and make sure you are signing your app with the correct certificate and uploading the correct one to Parse Push Settings.
When installing the app please also make sure the certificate is the updated one and you are signing with it.
Hope it Helps.
I'm fairly new and this was the first time i submitted an app.
So i have an app thats already in the app store. I had push notifications set up and it work when i tested it for the ad hoc distribution using the production certificate.
I did another provisioning profile for the app store and submitted it. Strangely after the app got approved some provisioning profiles disappeared . After being in there for awhile they came back but the push notification setting was turned off even the production ssl certificate for push notif was gone.
Now, Push notifications are not working.
Tried generating another ssl cert and the whole keychain exporting stuffs but it still doesnt work.
I don't know if the app, submitted has the profile with the push notification settings on.
Is it possible to add push notifications to that app? If not what is my best solution here?
No if the App submitted has not been signed with a Push Notifications Profile , then you pretty much can't do any thing about it, You may have to resubmit an entire new Version with a different Provisioning Profile with Push Notifications enabled,
Did you check the server you are trying to connect to when you send the push notifications?
Remember that there are more than 1 server :
ssl://gateway.push.apple.com:2195
ssl://gateway.sandbox.push.apple.com:2195
ssl://feedback.push.apple.com:2196
ssl://feedback.sandbox.push.apple.com:2196
It seems that some migration script went wrong on Apple's server. Your best bet would be to contact Apple support and explain your problem to them. May be they can do something for you.
Even after creating a new push notification certificate you would not be able to enable the push notification for the app already present on app store. Since the certificate is regenerated, you would need to update your profiles too and then use them to prepare a new version for app store.
I think the problem was that the devices that i tried had the app built on them from xcode. Because it worked for other devices that i never used xcode with. After removing all the related provision profile from the device itself, located in the settings menu of the phone, reinstall the app from the store then it started to work.