Is there any way to push notifications to a windows store app that isn't deployed on the store ? My application is an enterprise one, deployed by side loading.
Thank you,
Mathieu.
This post about deploying Enterprise Apps is mentioning the following about push notifications without deploying the app to the Windows Store:
http://msdn.microsoft.com/en-us/library/windows/apps/jj657971.aspx
Note In order to use some features, such as Windows Push Notification Services (WNS), you’ll need to use a Windows Store developer account to reserve a name for your app and then associate your package with the the package identity (package name and publisher name) assigned to your app by the Windows Store. You will need to sign the app with a certificate that matches the publisher name assigned by the Windows Store and which is trusted on your PCs. While app names are released after one year if the app is not published in the Windows Store, the app’s package identity will remain associated with your app, and you can continue to use these features in your app even if you never publish it in the Store.
Related
I currently have two applications: A and B. In both there is a common functionality, a message box. When a message is sent to your mailbox, you receive a notification. If the message is sent from application A, it is sent a notification to application A of the destination. Otherwise, it is sent to application B.
The question is: it's better to have a firebase project for each of the applications or there is some way to have both applications in the same project and know which application each user has installed to send the corresponding notification.
All apps in a Firebase project share all resources of that project. So they all share the same Firebase Authentication users, the same (Firestore or Realtime) Databases, and the same Cloud Messaging keys and audiences.
Firebase projects are meant to host a single logical application. If you have an administrative app and an end-user app, a free and a premium version, and then have iOS, Android, and Web versions of all, you have up to 12 variants of the app inside a project, but they're really all just part of the same application.
There are also limits as to how many apps you can add to a Firebase project. The exact limits have varied a bit over time, but if you have more than 30 apps in a project Firebase may prevent you from adding more.
So: if you app A and B are variants of the same application, it's totally fine (and probably a good idea) to add them to the same project. If you have another use-case, keep the guidance above in mind.
I have 2 Firebase projects, one for development and one for production.
If I send a message to a topic in one environment, will it send notifications to devices registered to both projects?
e.g. I have one device with the production app installed and subscribed to the topic broadcast, I also have another device with the development app install and subscribed to the topic broadcast.
If I then send a message to the topic broadcast using the development Firebase project notification composer, will only the device with the development app installed receive it?
It can be due to the reason that you have registered app in both project with same application id.
Try adding suffix in build.gradle file to the development version like .dev
And register the app in the firebase development project with this id i.e. your_app_id.dev
The app id will now help firebase identify you dev and production app
I have developed an application using android studio. It is already published in the google play store.
This application uses the Firebase FCM service for push notifications.
During the development stage, this worked perfectly. But since the publication in the play store, the SendMessageNotification function is not executed in the firebase backend (Firebase functions).
I have entered the api key in the console, as shown:
.
However, the service continues without running.
Have I skipped a step?
Have you gone through the firebase launch checklist?
Specifically, have you remembered to add the production certificate for your app as well as the development certificate? From the above page "Add a release SHA1 fingerprint for Android apps in the Firebase console (for OAuth client IDs)."
I don't know if this affects client messaging or not.
I have a Push-Notification service set up that I had to migrate (because IBM is closing the old service).
I used the original app and just opened a new Push-Service.
Now, when I try to test the installation with the REST-API online, it tells me that the app secret isn't valid.
Do I have to open a new app as well? (besides, I can't find the app-secret in the new interface)
What happens to the old mobile apps. Does the service run side by side for a while?
The app-secret value for the new push service is the VCAP credential, not an overall application secret like it was with the old services. The new services are more decoupled and thus only push requires the secret value at this time (added to prevent malicious usage of the REST API) and it is located in a different spot than in the old services.
Here are the steps to grab the app secret from your new push service instance (taken from: https://console.ng.bluemix.net/docs/services/mobilepush/t_restapi.html). Note where it says to click Show Credentials this is in reference to the new push service instance tile on your application dashboard's Connections tab.
With that said I highly recommend migrating completely from your app using the old services (Push, Mobile Data, Mobile Application Security) to a new app using nothing but the new services (Push Notifications, Cloudant NoSQLDB, Mobile Client Access). The services are not intended to work together cross-generation, and should be taken wholesale.
I have developed an app for an open source home security solution (ZoneMinder). The app I developed is called zmNinja (open source again) - and it works rather well. I am now implementing a mechanism to push notifications (motion detection alarms) to people who will use the app.
After going through the APNS and GCM documents, it looks like the "server" which sends the push to devices must integrate with SSL certificates and API keys generated from Apple and/or iOS. And this, specifically for apple requires a developer account.
Therein lies the predicament. Users of 'zoneminder' install their own servers. There is no central server. I've developed a event server that works with 'zoneminder' on web sockets that can be installed along with zoneminder and it sends notification when there are new alarms. This works very well on Android because Android allows the web socket to be open in background but iOS kills it (I can't treat the socket as VoIP/Location/content-news as its none of the above). Hence I am thinking of how to support APNS in the server. In other words, even if I can't do GCM for Android, there is still a way to receive alarms. No such joy for iOS users.
The problem is that like I described above, I won't be hosting the server. The users of the app will own their own server.
Given this, is there any way to support push notifications in IOS without requiring everyone who has their own servers to have apple developer accounts? I assume I can't give my certificates to them either as that would compromise my account.
Thanks