I've been developing an app with push notifications powered through UrbanAirship and its been working great for development. The problem is when I create an Ad Hoc build. The push notifications seem to stop working. I'm not sure where the breakdown occurs, but it just doesn't seem to be working.
I have already setup my app ID for both "development" and "production" push notifications and I've added the certificates before building and releasing. I am sure that I am using the proper app ID for my distribution mobile provision as well.
I don't know what could be going wrong. Has anyone else experienced this?
Related
I know I have done this successfully in the past.
I have an app with different dev streams. The app is currently in the App Store, and I am trying to track down an issue related to PUSH notifications that seems to be plaguing that version only. So, I am trying to debug Production/Release PUSH notifications. I know I have done this in the past, but it has been a while, and I have forgotten the exact set of settings that allowed this to work.
App setup is as follows:
App is tied in to Azure Notification Hub.
Notification Hub has a Production APNS certificate.
Currently, PUSH notifications succeed when the app is deployed to a device either by:
Downloading from the App Store, or
Building in Release mode with a Distribution Provisioning Profile
The problem is with a particular KIND of PUSH notification, and specifically how the app responds to it (so, it's not the PUSH notification that is the problem, but I need to be able to debug incoming PUSH notifications).
I think I remember the following to enable debugging Distribution PUSH notifications:
You have to build in Release mode.
You have to build with a Development Provisioning Profile.
But something is going wrong. No matter what combination of settings I choose, I am either unable to debug my app (and then the PUSH notifications works), or I am able to debug my app (and then the PUSH notifications fail). Has something changed in Xcode, or am I making some other mistake? Like I said before, I am positive that I have been able to get this working in the past. How can I get it working now?
I am trying to make my application work with a push notification service in a test flight mode ( essentially in a downloadable form, which is already in the app store ) but has worked in vain.
My IOS application was built with react native framework(0.39v). The application worked fine in the debug/release mode, being able to receive FCM sent from the API server or messages from Firebase console. Thinking it is ok to put the app on the appstore shelf, I uploaded the application and downloaded to my mobile. It worked expected except receiving Push Notification. It turns out that a testflight mode also shows malfunctioning of a push notification service. I am not sure why.
What would be the typical approach to deal with this issue? I reapplied the provisioning profile to the app but ended up failing. What would you recommend me to do? Might have this issue been triggered because of APNs certificate or Push Notification certificate?
If you have had similar issues, please them share with me!
I've never made an app with push notifications before until now. Currently Im doing some testing with internal users on iTunesConnect and the push notifications are coming in fine.
Because of I’ve never done this before, I wanted to ask if this means my push notifications will still work when I actually release to the store? If not, could someone explain the difference between testflight and appstore builds are?
Thanks
Yes the push notification will work on AppStore too, as there are two types of push notification certificates:
Development (Used for testing development builds)
Production (Used for production builds such as Adhoc and AppStore)
So if the push is working fine in TestFlight it will defiantly work on AppStore builds.
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'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.