Standard Disclaimer: This is a non-Microsoft website. The page appears to be providing accurate, safe information. Watch out for ads on the site that may advertise products frequently classified as a PUP (Potentially Unwanted Products).
- The Microsoft Band is not intended to be a do-everything smartwatch, and this device doesn't feel positioned to compete with the Apple Watch or even Android Wear hardware.
- So, if you have an Apple Watch, or have preordered and are eagerly waiting for it to arrive, let us guide you on exactly how to use the your new friend and what it can do for you.
After you've followed the deployment stepsto create App IDs and App Groups (if required), use the instructionson this page to:
- Set-up your Devices in the Apple Dev Center, and
- Create Development Provisioning Profiles, then
- Deploy and test on an Apple Watch.
Devices
Testing iOS apps on a real iPhone or iPad has always requiredthe device to be registered on the Dev Center. The device listlooks like this (click the plus sign + to add a new device):
Watches are no different - you now need to add your Apple Watchdevice before deploying apps to it. Find the watch's UDID usingXcode (Windows > Devices list). When the paired phoneis connected the watch's information will also be displayed:
When you know the Watch's UDID, add it to the device listin the Dev Center:
Once the Watch device has been added, ensure it is selectedin any new or existing development or ad-hoc provisioningprofiles you create:
Don't forget if you edit an existing provisioning profileto download and re-install it!
Development Provisioning Profiles
To build for testing on your device you need tocreate a Development Provisioning Profile foreach App ID in your solution.
If you have a wildcard App ID, only one Provisioning Profilewill be required; but if you have a separate App ID for eachproject then you'll need a provisioning profile for eachApp ID:
Once you've created all three profiles, they'll appearin the list. Remember to download and install each one:
You can verify the provisioning profile in the Project Optionsby selecting the Build > iOS Bundle Signing screenand selecting the Release or Debug iPhone configuration.
Microsoft To Do Apple Watch 3
The Provisioning Profile list will show all matchingprofiles - you should see the matching profiles thatyou've created in this drop-down list:
Testing on a Watch device
Once you have configured your Device, App IDs, and ProvisioningProfiles, you are ready to test.
Make sure your iPhone is plugged in, and the Watch is alreadypaired with the iPhone.
Ensure the configuration is set to Release or Debug.
Ensure the connected iPhone device is selected in the target list.
Right-click on the iOS App project (not the watch or extension)and choose Set As Startup Project.
Click the Run button (or choose a Start option from the Run menu).
The solution will build and the iOS app will be deployed to the iPhone.If the iOS app or watch extension provisioning is not set correctly thendeployment to the iPhone will fail.
If deployment completes successfully, the iPhone will automatically attempt tosend the watch app to the paired Watch. Your app icon will appearon the watch screen with a circular installing progress indicator.
If the watch app is successfully installed, the icon will remain on the watchscreen - touch it to start testing your app!
Microsoft To Do Apple Watch 3
Troubleshooting
Microsoft To Do Apple Watch 5
If an error occurs during deployment use the View > Pads > Device Log tosee more information about the error. Some errors and their causesare listed below:
Error MT3001: Could not AOT the assembly
This may occur when building in DEBUG mode to deploy to an Apple Watch device.
To temporarily work around this issue, disable Incremental Builds in the Watch ExtensionProject Options > Build > watchOS Build window:
This will be fixed in a future release, after which incremental builds can bere-enabled to take advantage of faster build times.
Watch App fails to start while debugging on device
When attempting to debug a watch app on a physical device, only the icon & loadingspinner appear (and eventually time-out). This will be addressed in a future release;a workaround is to run a RELEASE build (which will not allow debugging).
Invalid Application Executable or Application Verification Failed
If these messages appear on the watch screen after theapp has attempted to install, there could be a couple ofissues:
The Watch device itself has not been added as a deviceon the Apple Dev Center. Follow the instructionsto configure devices correctly.
The development provisioning profiles being used for testingdid not have the Watch device included; or after the Watch wasadded to the provisioning profiles they weren't re-downloadedand re-installed. Follow the instructions to configure the provisioning profiles correctly.
If the iOS Device Log contains
The system version is lower than the minimum OS version specified for bundle...Have 8.2; need 8.3then the Watch App's Info.plist has the wrong MinimumOSVersion value.This should be 8.2 - if you have installed Xcode 6.3 youmight need to manually edit the source to insert set it to 8.2.The Watch App's Entitlements.plist incorrectly hasan entitlement enabled (such as App Groups) that it shouldn't have.
The Watch App's App ID incorrectly has an entitlementenabled (such as App Groups) in the Dev Center that it shouldn't have.
Install Never Finished
This error could indicate unnecessary (and invalid) keysin the Watch App's Info.plist file. You should notinclude keys meant for the iOS app or watch extensionin the Watch App.
'waiting for debugger to connect'
If the Application Output window gets stuck showing
check if any of the NuGets that have been included in yourproject have a dependency on Microsoft.Bcl.Build. Thisis automatically added with some Microsoft-published librariesincluding the popular Microsoft Http Client Libraries.
The Microsoft.Bcl.Build.targets file that is added to the.csproj can interfere with the packaging of iOSextensions during deployment. You can track the bug.A possible workaround is to edit the .csproj file and manuallymove the Microsoft.Bcl.Build.targets to be the last element.