We build an iOS app using Apple Push Notification feature. We integrated everything the Apple docs told including provisioning profiles etc... A test in development mode worked fine with Apple tools. Same should be in near future with Google, but I´m talking here just about iOS implementation...
Our backend on Azure collects the registration ids from all iOS apps proper. I mean: We are storing the token retrieved from registration directly at Apple services.
Now we want to use Azure to send Push Notifications to all our apps. But I´m confused from reading the Microsoft documentation:
Must my mobile apps register to Apple or to Microsoft with corresponding SDK?
We don't use the MS SDK on app side. We just register at Apple. Can we send Push Notifications to our iOS apps (just simple broadcast to all registered apps) with Azure?
Our backend on Azure collects the registration ids from all iOS apps proper. I mean: We are storing the token retrieved from registration directly at Apple services.
Where are you storing them? You have to store/register the device tokens at your Azure Notification Hub.
Must my mobile apps register to Apple or to Microsoft with corresponding SDK?
Your app has to get a device token from APNS and then register this token at your Azure Notification Hub, so basically you have to do both.
Have a look at the documentation here. On a high level the whole process looks like this:
We don't use the MS SDK on app side.
You don't have to use the SDK, you can use the REST API.
Related
I am using MDM to configure Email accounts on the devices using
Mail/Exchange ActiveSync payload.
I was wondering if there is a way where I can also configure OneDrive and DropBox accounts using MDM or Apple Configurator.
I know we can install the Apps but is there a way where I can add a specific account too?
Each application has different capabilities for being provisioned as it's being sent down to the device, therefore, there's no easy answer to this
However, firstly, I'd start with https://appconfig.org which is an initiative to getting developers to use the same format for Managed App Config. This also allows MDM vendors to "read" the Managed app config capabilities of an app, saving you the hassle of having to look this information up on the web
You'll struggle with Microsoft apps beyond VERY basic capabilities. However, for DropBox, there's some information here: Dropbox EMM support
I have an ASP.NET MVC5 Application which I have moved from Microsoft Azure to AWS i.e. Redeployed from Microsoft to AWS. Can moving servers from Azure to AWS affect Firebase service in any way? My push notifications have stopped for my iOS client. Do I need to do something at Apple's end i.e. APNS etc.?
Found the Answer:
I was building a developer App with the developer Profile.
Needed to create an APNS certificate for developer builds.
Needed to upload the APNS to the firebase console.
We want to integrate Stripe Connect with iOS application to transfer amount from one person to person.
Let's say, I want to transfer $100 to my sister's account using Stripe Connect Standalone/Managed Account. And we also want to take business commission from sender which includes stripe commission also.
We have gone through Sharing Customers also but won't be able to find any solution for Stripe Connect with iOS SDK.
We have also checked iOS SDK.
Can anyone please guide us how to integrate Stripe Connect with iOS mobile app in above scenario?
How can we transfer payment to end customer?
Do we need to integrate through iOS SDK or web page?
Stripe's iOS and Android SDKs serve the same purpose in a mobile application as Checkout or Stripe.js do in a web application: they take payment information and produce a token in return.
Once the token has been created, it must then be sent to a backend server where it can be used in API requests sent with the secret key. You can't create charges or transfers directly from your mobile app -- that must be handled by an external server.
(Also, please note that there might be compliance issues with what you're trying to do. I recommend you reach out to Stripe's support to explain your usecase and make sure it's something that Stripe can support.)
You can easily integrate Stripe Connect with your iOS app check the following link
https://github.com/gurunglaxman0/StripeConnect-iOS
Once you connect your stripe user id with server you can create charges and application fee using Stripe Api's from backend
We are using IBM Push-Notification service and Mobile-App-Security on our Bluemix app (serving iOS clients).
In order to send a push notification, our server sends a POST request to: https://mobile.ng.bluemix.net/push/v1/apps/{application-id}/messages
with the application secret in the Ibm-Application-Secret header (following the instructions here).
To initialize Mobile-App-Security SDK inside our app you need both the application-id and the application-secret - this means that the app itself must contain these values (as constant parameters or download it from a server). If a malicious user fetches these values using simple reverse-engineering, he would be able to send the same POST requests, i.e. send push notifications to other clients, right?
Shouldn't there be two application-secrets? One secret for the app (making it hard to fake registrations - i.e. require reverse-engineering) and one for the server (which allows to send notifications and should never be stored on client-side).
Is it possible to initialize the Mobile-App-Security iOS SDK without an application secret?
I understand your concern. To address all your questions:
-You must have the app secret on the Client side in order to authenticate with MAS and use the Push service (Push relies on MAS auth)
-We recommend implementing your own form of security to prevent a malicious user from easily obtaining the App Secret. For example, encrypting the file that stores the app secret, or just the app secret itself.
If you are looking for a more robust built-in level of security, I would recommend using the newer MobileFirst Services Starter, with support for Push and the Advanced Mobile Access service (AMA), which is currently only available for iOS 8.
A mobile device registers with its unique device id at the server running on Bluemix. If you don't trust a device, you could send a push notification with a key to this device and request it back. If you get this key back, the device has also registered at Google or Apple successfully.
I am using Amazon SNS Service for an iOS application that needs push notifications.
I have figured most of the things, except for the part where I have to register my device tokens.
This is where Amazon talks about it. It can be done manually or with the help of createPlatformEndpoint API which they obviously recommend for bulk uploads. My question is how we can directly register tokens from devices that will install the app later on. The documentation talks about a proxy server which I would want to avoid as of now. Isn't there a direct way of doing this, like where I can directly call a method and push the device token received in the application to my SNS Platform?
This, is a possible duplicate except that it is in reference to Android.
The AWS Mobile SDKs support accessing SNS directly from the mobile device. If you're interested in seeing code demonstrating this on iOS, we included some as a sample we prepared for re:Invent 2013 called Mobile Photo Share.
The important thing to note when accessing SNS directly from the mobile device is that you'll want to restrict the credentials delivered to the device to only those services and resources you'll need to access. You can accomplish this via web identity federation or a token vending machine with appropriately restricted policy.
If you want to learn more about the Mobile Photo Share app, we had two talks at re:Invent about the app and its architecture. The video and slides for those talks are available here:
Building Cloud-Backed Mobile Apps
Integrating Social Login Into Mobile Apps