Hi,
Working on an audio provider app and wanted to add a menu for the ConfigureSyncView. This includes a button "Sync", which would call Media.startSync(); in order to finish the ConfigureSync and start the SyncDelegate.
Now, by all looks starting the sync through that button works correctly, however, all requests for HTTP_RESPONSE_CONTENT_TYPE_AUDIO seem to be skipped. When the button does a WatchUi.popView(SLIDE_IMMEDIATE); the sync also starts and everything looks the same, but now the HTTP_RESPONSE_CONTENT_TYPE_AUDIO requests are performed correctly and thus the sync is actually completed properly. (this is on a physical watch device. The simulator actually syncs well in both cases)
I noticed also that these HTTP_RESPONSE_CONTENT_TYPE_AUDIO requests cannot be made from anywhere but the SyncDelegate (very weird, since this is not documented anywhere). I simply get a UNSUPPORTED_CONTENT_TYPE_IN_RESPONSE = -1002 response code (from the simulator).
So the questions I have are:
1. Is there a difference between Media.startSync() or Communications.startSync()?
2. Why did the sync not work when started through Media.startSync() ? And why does the exact same code actually properly sync in the simulator?
3. Why can requests for audio content not be made outside SyncDelegate? (and more importantly: Why is there no documentation of this?)
Thanks in advance!
Best regards,
