My company do integration of our product with Jawbone API.
I'm looking for the way to get date&time when user uploaded data to Jawbone UP server last time. I mean time when users sync it's data from wearable device&smartphone to Jawbone Server.
Can't find something like that in API Spec. The only Idea I have is to use Pub Sub notification date & time as indicator that user recently uploaded data to server. However I'm not sure that Pub Sub notifications being sent only in case of data upload. Please let me know if you have an ideas.
PubSub is the best way. You can use the type field in the notification to determine what kind of data was just synced.
There is a list of all the possible Notification Types under All notification events on the Pub Sub documentation.
Related
In a few weeks, I'd like to track subscription status etc. for my app.
I know about the server notifications that you can set up on App Store Connect - however, I haven't found a way to request a data set for all transactions that would have fired server notifications if they were already set up at a time.
Does Apple expect you to set up the receiving end for these notifications in advance, even if you don't need the data right now, or is there a way to request the past few years worth of notifications (or transaction information or whatever you want to call it) that you have "missed"?
We want to generate Uber Eats reports for multiple customers. Since everything is running on one system, the webhook notification for report generation will all arrive on the same local API.
Now wondering if there is a relation between the webhook notification and the original report request?
The reason is that we would like to check the signature of the notification and for this we need the appropriate client secret. Also we want to mark the original report request as completed.
So we need to be able to associate the notification to the right client or at least to the report request.
Is it possible that the workflow id we receive with the report request is included in the notification?
Or is the job_id what I'm looking for? In the notification example this is not so clear to me.
Do you have other ideas here?
I want to save data on device itself that would be persistent even after deleting the app and installing it again (data can even be one int/date).
According to my knowledge it is impossible because each app can store data only on it's sandbox (I know I can use iCloud etc. but I don't want any services user can not have or give the app specific permissions).
As to my understanding the only option to do that is to store it on my server.
But, Apple doesn't allow to send UDID or any other specific device ID and I can't get the iTunes ID. I know I can use any other ID like Facebook ID but the app doesn't have it and that would make a really bad user experience.
I've download apps that does just that successfully (saving data specifically to my device that been recovered even after deletion and without the need to enter any ID or login process). How do they do it? Do they send UDID to some server and apple miss that or there is a way to save data outside the app sandbox?
Well there is the KeyChain, which can store data the would kept even if you delete the app.
We do that too in our app:
Basiclly we create an UDID of our own and store that on the device (in the keychain).
Combined with user id that gives us all we need on the server side to identify the user and his device. We don't store any other app data on the device, all is server managed.
You could pack your data up, store it in the documents folder for your app, and back up your device to the cloud or iTunes. you can then do a restore to get it back. You just can't do anything on your phone between the backup and the restore. Just saying.
Does Parse have a limit on the number of channels I can have? I am trying to send a push notification to individual users and the only way I can figure out how to do that is to set up a channel for each user. Other question: Is there a better way to do this?
I emailed Parse and this was the response I got:
Nope, there's no limit on channels. We'll be providing a better way to push to a specific user pretty soon. I'll put you down to get notified when it's ready.
EDIT:
A recent email from Parse about the 'better way':
I wanted to let you know that you can now push directly to a user on iOS, provided you are sending notifications via the REST API. This blog post has more information: http://blog.parse.com/2012/07/06/pushing-to-queries-in-ios/ . You can also target push notifications by device token, geographical region, or according to any other data that you store on a per-device basis.
I'd like to develop a tracking system using an API of course (like the famous Orange API).
the idea is simple:
I send a SMS (from my Web interface) to the person i want to track
The person's mobile terminal (GPS like this) send me back automatically
the coordinates by SMS.
The sent information are displayed on the user's web interface.
The questions are simple:
How the terminal can send automatically the response?
How to indicate in the message that the information is for "user4655"?
How to make connection between the information and the database?
Thanks,
Regards.
* How the terminal can send automatically the response?
Ans: You set the gateway and the time intervals you want the device to send the sms to on the device itself.
* How to indicate in the message that the information is for "user4655"?
Ans: The gateway you use will have the API to determine that the number it is sent from. The device will use a registered phone number from either a sim or enabled by one of those cell providers.
* How to make connection between the information and the database?
Ans: I dont understand this. But I'm guessing you will have a database to keep track of the user data. You'll just probably need another table that is a child of the user, which has a list of the data and the time they came in.