Hi, We are a group of PhD student working on developing a health related app using SensorKit and AppleHealth Kit. We submited our research propsal on Feb 16 and have not heard back from apple support. We wonder that how long would be the processing time? Thanks,

Hi, My middle schooler is working on a project for National Science Fair competition to estimate blood pressure from ppg signals. While he is using external database to develop his algorithm, it would be very useful to test it with real time data. I have a Series 6 watch and wondering how I can access my ppg sensor raw data.

Hi, I am trying to find out the GPS/Location update rate that the iPhone14 can accomplish. Most GPS update rates are 1hz (1 location update per second). I am hoping that the newest iPhones can provide a faster update rate. Also I would like to know the accuracy of the GPS. It is 100meter, 50meter, 10meter, 3meter? Where could I find this information? Thanks, Adam

Hello, I'm having a problem on my watchOS app where even though I have instantiated a WKExtendedRuntimeSession the app stops logging IMU data a few seconds after the watch has gone to sleep. This happens on my Apple Watch Series 6, but does not happen on the latest Apple Watch Series 8. CPU usage in both cases does not exceed 70%, so I doubt my app is exceeding the limits thus cancelling the WKExtendedRuntimeSession. To back that up, I am not getting the WKExtendedRuntimeSessionInvalidationReason trigger I was suggested to put in place form the documentation. I have tested a couple of different sample rates, this does not seem to happen with a sample rate as low as 1, but does happen already with a sample rate of 30. Could it be a watch limitation, or am I forgetting something? P.S. I have also set the background mode to physical therapy and ticket the workout processing box.

There is a description on this document https://developer.apple.com/documentation/sensorkit/srfetchrequest ”SensorKit places a 24-hour holding period on newly recorded data before an app can access it. This gives the user an opportunity to delete any data they don’t want to share with the app. A fetch request doesn’t return any results if its time range overlaps this holding period. “ Does that mean I can't get real-time data from the sensors

As we're starting to analyze data for the SRDeviceUsageReport we've found a small number of duplicates. Out extraction strategy for SensorKit in general is to keep the date of the last sample retrieved and start the next SRFetchRequest at essentially 1 millisecond after that time so we don't get the same sample again and conceivably don't miss anything in between. On 3 participants looking at iPhone data, with about 5000 samples reviewed, we found about 1 % of samples were seen more than once - spanning an extraction cycle. More troublesome we found about 0.5% were ALMOST equivalent, but overlapping. So since these reports come in 15-minute segments, one might be 2022-05-12 12:00:00 - 12:15:00, but the next one might come in at 2022-05-12 11:59:00 - 12:14:00. And sometimes they have totally different data! Curious if anyone else has experienced this or has any advice on how to avoid/make sense of the data in that situation.