I always used Parse for my applications and I cannot seem to find a service anywhere that allows for multiple apps to utilize one backend (multiple .p12s uploaded to utilize push app to app). Does Firebase, Kinvey, or any service not allow this yet?
push notification certificate create by Bundle ID,the bundle ID is unique about the app.so the push notification certificate can't allow multiple certificates.
Related
I want to add push notification to my app with Firebase Cloud Messaging but I don't know the right way to set this up.
My App Logic is: I have multiple customers (companies) who host their own server's own database and their own users. Some of the employees of the different customers will download the app to receive push notifications from their company's server which implements the firebase admin SDK to send push notifications.
How is it possible to handle all customers from one FCB or is it even possible?
So the customer can just enter the created „server key/topic or project id / UUID“ to his server configuration and can receive the push notification.
They should also not be allowed to see any data from other customers or send messages to them.
At the end of the day, I need to handle all customer
Using the Admin SDK allows one to send messages, it does not allow you to receive messages. So from that perspective it sounds like the approach suits your needs.
The customers using the Admin SDK will also get full administrative access to your entire Firebase project though. So if you use any other Firebase products aside from Cloud Messaging, that would be a security risk.
I have an OpenEdge database, I have created a REST Service and am able to CRUD to it from the outside World.
I have created a Nativescript app that can pull data from the REST service etc, but now i want Push notifications.
I know about the Progress Kinvey backend, and Firebase backend with their push notification features but i don't want to use them.
is there a way to create my own Push notifications on my REST server etc?
So first I would like you to understand how Push Notification works just to make sure we are on same page,
Once your app is installed, you can query for a unique token and save it in your backend for future use. Whenever you want to send a push notification, you have communicate with APNs (Apple Push Notification Server) / FCM (Firebase Cloud Messaging) in order to send a push notification to your iOS / Android device using the unique token you acquired earlier.
So now you must use Firebase as that is the only way you can communicate with Android, yet you may choose to communicate with APNs yourself. But in my opinion, it will be a overhead for you as both have their own protocols, you will have to distinguish your tokens between iOS & Android, use appropriate protocols etc.,
I would suggest you to go with just Firebase plugin (until you are super familiar with APNs already), so you don't have to worry which platform the token belongs to, update / revoke invalid tokens over time etc., FCM has pretty decent APIs & Documentation that can make your life easy here.
i strongly recommend you to see my answer here answer here.
from it:
when you want to pull anything from place_1(e.g. api) to place_2(e.g. browser_client) you most have an identifier of the
place_1_resource (which commonly is the uniform-resource-locator of
api)
when you want to push anything from place_1(e.g. notification_central_server) to place_2(cellphone_client) you most
have an identifier of the place_2_resource
if you don't have any identifier for a cellphone which you want to
send it a notification, your server dont know where to send that
notification so we need a resource_identifier_like for cellphones
which is actually a device_token_like and you have just one approach
to get this device_token_like and that is the FCM/APNS
I want to install same push notification certificate in multiple servers. I wonder Is there any limitation for provider(server) count with same certificate?
For example, We have 10 clients who bought our web application server. The server has function that works as push notification provider for iphone users. There is iphone application on App Store that works client of web application. All servers uses same iphone application and same push notification certificate.
You can install the certificate on multiple servers, there's no limitation as far as I know. The only recommendation is that you keep the connection with the Apple server open for as long as possible, and that you refrain to send notifications to devices where your application has been uninstalled. For this, you have to query Apple's feedback service.
I hired an objective-c programmer to develop my iphone app, he wrote the code, and now I want to test the push notification service, but he wouldn't send me the p12 file, he said he cant send me the p12 key, because it contains his private key.
1) So can I create the p12 file myself, if so how can I do this? doesn't it need to be attached to the app? I need the app's id?
2) Can I just add him as a developer under my apple' developer account so he can set up everything?
The key used with APNS does not need to be the same key used for signing apps. It should not be the key used for signing apps, since it will end up installed on a virtual server on third-party hardware in a fourth-party data center. You might even want to use different development and production keys, if more people will have access to the development server (e.g. developers might run it on their own computers as necessary for debugging).
You can create the keypair, send him the CSR, get him to create the cert and send that to you, and use the cert on your server.
You'll need to set the app up under your own account at some point anyway (assuming you're not going to pay him to support it indefinitely) so you might as well do it now. Depending on how much you trust him, you can add him as a developer or just do it all yourself.
I'm pretty sure you can also give accounts restricted permissions - just enough to upload a CSR, create an "iPhone Development" cert, and download provisioning profiles. You can do the rest (add UDIDs, set up app IDs, and configure provisioning profiles), right?
You can create your own .p12 file and your app is not dependent on push notification certificate.
.P12 is used to authenticate and communicate between correct device and APNS server.
Check this tutorial
Once done you can test using by your own server if you have access or use the below tool to test
Pushtry.com
Hey,
Is it possible to add push notification functionality to an already existing app?
Will it be possible if I have to change the appID?
I am asking this because I am about ready to submit my app, and currently don't require push notifications. In the provisioning portal I have already created default appID, with a wildcard Bundle Identifier.
I will however need the push notification service in the future - And for that I will need to use a non-wildcard Bundle Identifier. Will it be possible to easily change in the future? I prefer not to go through the push notification service certification right now.
You can not change the bundle id of your app (inside the info.plist and iTunesConnect). So choose your bundle id now currectly for later usage.
You can sign you app with other certificates (without wildcard) on an update.