Is it possible to get Apple push notification service to work on both development and distribution builds?
I want to debug my app while it's installed on other devices with the distribution provisioning profile.
Yes, you can create push certificates for both the distribution and development (sandbox) push environment. And an individual app installed on a device will choose which push environment to work with based on the <aps-environment> entitlement in the provisioning profile (which will determine if it is assigned a production or development device token when registering to APNS).
That said, I strongly recommend that you don't use the same server and DB for storing production and development device tokens. Development tokens are valid only in development push environment. If you try to send notifications to development tokens while using the production push certificate and connecting to production APNS server, you'll get an error (invalid token) and the connection will be closed, which may interrupt the sending of notifications to production tokens too.
If you have a development server, your development build should send the device token to that server, and only the development server should connect to the APNS sandbox environment.
Related
We are evaluating mesibo for InApp messaging within our SaaS application. We would need OnPrem setup to comply to Data compliance requirements.
One clarity we would need on this regard is, when we switch from Cloud to Onprem setup still client side code continues to use https://mesibo.com url. In this case we believe all the traffic gets routed to our OnPrem server via Mesibo server.
Please confirm if this understanding is right? If so would there be any data residing on Mesibo server? This clarity is required for us to respond to our customers.
Thanks
No, once you enable On-premise, your client directly connects to your on-premise server. You can verify it using netstat utility. mesibo cloud will have no access to your data.
Refer to the following to learn more https://mesibo.com/documentation/faq/on-premise/#do-i-need-to-change-or-recompile-my-apps-to-run-with-mesibo-on-premise
Mesibo APIs support both cloud and on-premise. By default, it connects
to the cloud. However, if the app is configured to be on-premise, the
mesibo cloud will refuse to serve and will ask the client to connect
to an on-premise server, and will disconnect. Then onward, the client
will directly connect to the on-premise server and then all the
messages and calls will route to your mesibo on-premise server.
I have made an angular application that will run in a secured network. This application also shows push notifications upon some operations. But the problem is that this application is showing push notifications when run outside the secured environment and not in the secured environment.
By secured network / environment I mean, there will be checks on the eligible links that a user can open on the secured network. So, I have a doubt that the service, which could be a HTTP link or some other protocol, that is responsible for getting the push notification to the machine and browser from web push servers need to be whitelisted by the administrator. And I don't know what are those links and ports and they are not mentioned anywhere (as per my knowledge). I need those links and ports for chrome, firefox and edge web push service which could improve this situation.
Thanks for any help in advance.
I have a web application that uses websockets to receive real time updates. Since I don't use the websocket connection for anything else, and scaling websocket servers is a pain, I'm considering moving the messaging part to Firebase Cloud Messaging.
It seems a pretty straight forward port for my web app.
However, the web app comes with a companion desktop app that some customers use, that is written in QT+Python. Is there any way to receive the FCM messages in a different client than the official SDKs?
We have developed a mobile app using Meteor+Ionic2. We use our internal NodeJS server which is not in internet zone. We got the app deployed to our enterprise app store which enables AirWatch VPN tunneling to get the access to server in intranet zone.
Everything works great when tested with iOS device level using "F5 Access" VPN when deployed using Xcode or enterprise app store with NO VPN tunneling . But when download the app from our enterprise app store which does per-app VPN using AirWatch VPN Tunneling, iOS app gets stuck at the splash screen. It is not seems to call any client side or server side code of Meteor+Ionic2.
When redeploying it using development distribution, It seems to be stays at about:blank and not going to localhost and getting "Failed to load resource" error in about:blank.
The same AirWatch VPN Tunneling works great in Android. This issue seems to be happening only in iOS. I checked device level logs and also AirWatch VPN tunnel logs which donesn't report any errors.
I'm not sure whether Meteor+Ionic2 supports AirWatch VPN Tunneling for iOS as none of framework codes get called. Is there anyway to debug the enterprise distributed app? Is VPN-Tunneling not supported in iOS app development using Meteor?
Thanks,
Annadurai.
The root cause of the issue seems to be AirWatch config which causes the localhost to be appended with domain name like localhost.mycompany.com. As AirWatch couldn't fix this issue, we dropped plan of using AirWatch VPN tunneling.
We are running MobileFirst Platform Foundation 7.0 and are using both iOS Push as well as Android Push messages. We have an issue with talking to GCM after a server restart.
MFP is installed on a WebSphere AppServer Network Deployment version 8.5.5 environment. This server is running behind a corporate firewall.
We set the environment entries to specify the proxy-server MFP should use to talk to GCM; as documented here: https://www-304.ibm.com/support/knowledgecenter/SSHS8R_7.0.0/com.ibm.worklight.deploy.doc/admin/t_using_JNDI_lookup_to_override_WL_properties.html
After a full restart of WAS, meaning a stop of the App Servers, the Node Agents and the Deployment Manager and a subsequent start in opposite order - GCM push works fine.
However, if we restart just the App Server MFP is running on, the following errors appear in the server log:
[10/28/15 11:04:17:022 CET] 00000123 JavaScriptInt I com.worklight.integration.js.JavaScriptIntegrationLibraryImplementation info Wed Oct 28 2015 11:04:17 GMT+0100 (CET): Send MyIT Broadcast message for IT Failure with title 'Test Push Message 3' [project babel]
[10/28/15 11:04:17:061 CET] 00000156 GCMMediator E com.ibm.pushworks.server.notification.gcm.GCMMediator sendOrWait FPWSE1051E: Notification through Google Cloud Messaging (GCM) was not sent to application 'MyITHelpdeskApp-android-0.1.2' because connectivity details to GCM are not set.
And push message sent to Android devices fail to be delivered. It seems environment entries for web modules are not loaded correctly upon AppServer restart, or MFP does not pick-up namespace entries correctly when reloaded.
Is there any setting we missed? Or is there a way to force the update of the namespace with the corresponding GCM Proxy settings?
It turned out that the answer in this case was that the .wlapp deployed to the server was an old version, without an appropriate GCM connection key (in other words, it was a development issue, not an infrastructural one). On fixing this, GCM starting working.