How to authorize for CMSensorRecorder

I am having the same experience. Accelerometer is available for recording but it is not authorized.

Interestingly enough, Apple removed all the documentation related to CMSensorRecorder: https://developer.apple.com/library/prerelease/watchos/documentation/Miscellaneous/Reference/CMSensorRecorder_class/index.html#//apple_ref/occ/cl/CMSensorRecorder now returns "Page not found"...

I am wondering if this has anything to do with the Motion & Fitness privacy settings. My app is not listed there and I could not find any way to

request "Motion & Fitness" permssions.

Strange :-/ Accelerometer is working fine woe me but only when watch display and all is active. My app is in the privacy security settings listed on the iPhone because I'm using workout to track heart rate - but also workout is not working correct for me. App stays not in foreground therefore heart rate is only able to measure when display is active. Tried to query on the iPhone for the data from the HealthKit but it is only available when workout finished and not Immediately

This link is working for me but still CMSensorRecorder not 😐:

https://developer.apple.com/library/prerelease/watchos/documentation/CoreMotion/Reference/CMSensorRecorder_class/

now CMSensorRecorder without any code changes - strange :-/

But just some seconds of data is to much payload to transfer with sendMessage method

I found that the CMSensorRecorder.isAuthorizedForRecording() returns true only after your app is authorized in Privacy/Motion & Fitness (on the iPhone). Then to make the app authorized for Motion & Fitenss I had to access one of the core motion function (like startActivityUpdatesToQueue or even recordAccelerometerForDuration). After that you just need to confirm on the iPhone and from now on CMSensorRecorder.isAuthorizedForRecording() returns true.

Still, I can't get any data from the CMSensorRecroding. In my case the accelerometerDataFromDate function does not return any data - the returned value is always nil. Because it is said elsewhere that it can take up to 3mins for the data to become available, I am doing the following scenario:

1. I am starting the recoding session with recordAccelerometerForDuration(30). Here I record the current date: recordingStartDate = NSDate().

2. I wait more than 3min30s (keeping the app on the watch active) and after this time I call:

accelerometerDataFromDate(NSDate(timeInterval: 10, sinceDate: recordingStartDate), toDate: NSDate(timeInterval: 20, sinceDate: recordingStartDate)

As you can see, I making a 10s window within the requested 30s recording frame.

3. I get "nil".

I also tried shorter timeouts, accessing the data immediately, and even activating the accelerometer before calling ecordAccelerometerForDuration. Nothing helps, I still get nil back from accelerometerDataFromDate.

I really wonder how you guys are able to get any readings back from the sensor recorder...

Maybe things will get better after September 9.

Just to share.

I am getting it working from time to time. It apparently does not like the charger to be plugged in on the watch when starting recroding. It also does not seem to respect the time boundaries for reading out the recorded data. Seems to be pretty random, and it is not rare to get more than 2000 samples for an interval of 1.0 second and many samples are just plain junk from some date far in the past - the valid samples are indeed having timestamps indicating 50Hz sampling rate though. Also the overall success seems to depend on the requested recording interval and then even the position of the data-read window matters (if it is on the worng postion I do not get any data). It also looks like that one cannot start reading before recording finished completely.

From my experience it is so unpredictable that it seems to be useless for any practical use.

I am seeing alot of that too, the timestamps seem horribly random? Can anyone from Apple comment on what is going on there? I understand they are intervals from the boot time, however nothing seems to match up....

Yes, I've seen very similar results. The sensor working when on the charger is also seen (I have a bug with Apple on this one but they haven't replied yet).

You might check the 'sensor' public project I have over at https://github.com/gcmcnutt/Sensor-- this shows my evolution of trying to get sensor recorded data out through the phone and out to AWS. It works fairly well now at least in diagnostic mode. But the data gaps and data dropouts are chronic. I'm guessing this will be fixed with the official release.

I really want to figure out how to get the watch app to be a background process. Right now the recorder dequeuer is in a foreground process, which really limits the throughput.

Just checked with the GM release. No improvement observed. It is still very random.

Thank you guys for responding. At least I know I am not alone with this 🙂.

Have the same problem now again "not authorized"

It's working now when I requested once the permission for fitness access int the iOS app and then toggle the switch off and on in the settings under privacy and fitness for the app.

But that cannot be the normal way it should work. 😕

Any ideas?