I am trying to receive MMS through my client's messaging app that's in development. One major issue that I am facing is that I am unable to test in India as service providers here are using legacy system of sending MMS. What I mean is while using default messaging app, when I send MMS from one phone to another, I don't receive the message itself, instead I get the link to portal of my service provider, where I have to login with my username and password to see the attachment as well as the text message. Therefore, I am unable to test MMS receiving and the parsing of received binary data on my phone. So, I have to ask if anyone else who has worked on a messaging app before, could provide some guidance on the topic.
Related
My client is complaining that he is not receiving text notifications to his phone. I sent him some tests and he says he hasn't received any. He also confirmed that his phone carrier is open to all numbers. Am I able to verify the connection works properly on my end? Thank you.
I'm attempting to connect to Office 365's Exchange Web Services, but it keeps coming up with a 404 error. I'm pretty sure the issue is with the credentials, but I seem to lack the knowledge to resolve it.
I performed a test via testconnectivity.microsoft.com (Service Account Access test under the Office 365 tab) and it is also getting a 404 error. I know from searching online that the format of the credentials is a common problem, however it is in the 'user#company.com' format.
I think the problem may have something to do with the domain or that the authentication goes through my company's server. For example, if I log into outlook.office365.com with the 'user#company.com' format, it forwards me to my company's log on portal (I believe this is a typical setup). In order to log in, I first have to change the user name from the 'user#company.com' format to 'user#domain' or 'domain\user' (the domain is different from the company name).
My question is, since the authentication goes through my company's server, do I need to authenticate to Exchange Web Services in a different manner? (Currently I'm using a WebCredential)
Alternatively, if my company's portal were to accept user#company.com as a valid user name, would that allow me to connect to EWS using a WebCredential?
This is the code I'm using for the connection, however I don't think it is the problem given that Microsoft's test site was also getting a 404 error.
service = new ExchangeService();
service.Credentials = new WebCredentials("user#company.com", "password");
service.Url = "https://outlook.office365.com/ews/exchange.asmx";
I am implementing Web Push Notification in an application and I have successfully registered the client app with GCM. I have the subscription object that contains the endpoint that looks like this.
"https://android.googleapis.com/gcm/send/dV4lSfI5J6Q:APA91bEU28F9YG5qNr3xSjvYlH2Mh1GPgiqMaRcjandHbpfqnVyAeZxqoE31OXYq4yzW2_vrkn74YHdgsITZP_6SELO8-xHf1hylquJefJdY85-Xx9AWTAPP9H6kfq7CKp23dsoQHbH
I read and found out that we need to use a third party library like web-push to send push using this endpoint to the clients because the payload needs to be encrypted according to spec. My objective is to send notifications to all my users, web + mobile, at once, using Firebase Console's Notification feature.
Is there a way to send push to web clients using Firebase console or to convert the GCM endpoint to an FCM token?
Update: If I try to use Firebase console to send push the token generated above, I get the following error.
As per testing this out, for some reason, registration tokens for Web are not working or allowed in the Firebase Console. Only tokens for Android and iOS do:
The request could still proceed where the console would show that it is sent/complete, but there wouldn't be any messages received.
I need advice after looking a lot about receive push/toast notifications regardless of the status of the application (closed or open).
The application communicates with a NodeJS API.
The idea is that a user logs in once to the application and then can receive notifications (depending on his account): i the user restarts his system for example, at startup he receives notifications without having to open the application (like the Mail application for example).
Most tutorials on MSDN use Azure and I don' use this. I would like to know if you have tips or links (tutorials, ...) for doing this in an UWP (or WinRT) application.
Thanks in advance for your help.
Regards
You can send push notifications from your NodeJS api via Windows Notification Service. This service has nothing to do with azure but when using Azure Notifications Hub it will be easier to get it implemented, but again this is not required;
In essence:
- register your app in dev center
- obtain a client id and client secret to use WNS in the dev center
- When your app launch it obtains a push notification channel uri and sends this to your backend. Your backend need to save all the URI's for the different devices
- When you have a notification select the uri's of the devices you want to send the push notification to
- post a xml message (based on what you want to update, tile, toast, badge or raw) to the URI's. To be able to post you need to authenticatie with the client id and client secret
more detailed read: https://msdn.microsoft.com/en-us/windows/uwp/controls-and-patterns/tiles-and-notifications-windows-push-notification-services--wns--overview#
I'm developing a website and mobile application that communicate with each other.
It's very basic at the moment: the app makes a get request to a URL and the server returns JSON data.
I want to secure this and make sure no-one can send a get request to the URL and get this data (only the website and the app). Is it ok to make a 60+ character password that the app can send with the request that the server accepts before data is sent, or is this breakable?
I dont want to use OAuth because it's overkill as only the app and the site are going to communicate. Please provide me with a few solutions, thanks!
You can use HTTPS to transmit data.But you will need an SSL cerificate for this.