Watch complication available to add in Watch app on phone

I'm not sure what you have working and what you don't have working. The app should run from Xcode on the simulator or a real device. The app should show up on the Apple Watch. (There are many many reasons why that might not be working.) Then when you force touch the watch to change the watch face and select a complication on the watch face your app's name (i.e. the bundle display name in the info.plist of the Watch Kit Extension) should show up as an option - provided you added the correctly sized complication image to your Assets.xcassets under your WatchKit Extension (not a different xcassets). One issue I had is that the watch caches the images and refereshes that cache only when the watch, and perhaps also the iPhone, is shut off and turned back on. I went through a delete - turn off - turn on - reinstall - turn off - turn on cycle to be sure changes in the complication images were transfered to the watch. Many of those steps may have been over kill but some were necessary because of the cache.

Sorry, the app is showing up properly on the watch, and the complication is available to add to the watch face when force touching and customizing the watch face on the watch itself. The issue is in the "Watch" app on the phone. When attempting to configure a watch face in the Watch iPhone app, my complication does not show up in the list of complications to add to a watch face. So everything is working correctly on the physical watch itself. I just must be missing something in the complication code that triggers the complication to show up in the Watch app on the phone. I actually noticed that the Starbucks complication has the same issue. It is available to add to a watch face on the watch iself, but not availabe in the picker list of complications when trying to customize a watch face in the phone app. Hope that makes sense.

Did you closely follow https://developer.apple.com/library/content/releasenotes/WatchKit/AddingComplications/?

I somehow missed this, and going through it I also found that I had failed to provide a text provider for one of the templates, which was causing the complication to crash. Thank you!