Hello,
I've been developing an Apple Watch app targeting watchOS 3.2 and have been testing it in the simulator. The app works fine in the simulator, but I'm having trouble getting it to install on the physical watch device. My phone and watch have been updated to the latest version (iOS 10.3.1, watchOS 3.2) and I am able to deploy the iOS app to the phone. When I go to the Watch app and try to install my app to the watch, I get the icon on the watch with the install progress indicator, but it always seems to time out and get stuck on the screen showing something like 80%.
I read through Testing on Watch Devices to see what I could find. I believe that my certificates and provisioning are correct (I think it probably wouldn't even attempt to install if they were incorrect). The closest sounding portion is Watch App fails to start while debugging on device, but I have this issue whether debugging or compiling for release mode and the description basically has no solution... I've tried cutting down my app size by removing all 3rd party libraries other than Xamarin.WatchOS and .NET frameworks, but to no avail. I've also tried looking at the device logs, but couldn't find anything that looked right.
I'm open to any suggestions or guidance on what to look for in the device logs (should I be looking at the phone log or watch logs?)... I haven't yet seen the SPErrorGizmoInstallNeverFinishedErrorMessage
error in the logs either...
My setup:
Visual Studio 2017 Professional
MacBook Pro w/ Xcode 8.3
Posts
Apparently, it was my entitlements... Finally found it in the logs after looking in Console on macOS. I had two entitlements added to both the WatchKit extension and app:
I removed both as I don't need the app group. After that, the app installs but is unable to get any data because the iPhone app crashes... On to the next issue
Hi There,
I tried removing entitlement.plist from Watch extensions but still not able to install application into smart watch..
Any suggestion is really appreciated ..
Thanks
Shafi
@Shafi @brader did you guys fix the the issue?