I have modified the app. It will now present an opening view and then an error view if there are no subscriptions available. This is in order to assist with the App Review. I don't think the change will affect the UX in the long run. Hopefully that will allow the team to get through their process successfully. Thanks for your response.

Want to clarify that I know how to compare two dates. This is about having a previously purchased product to test against.

DONE: FB14321983 Thanks

Hey - Quinn straightened me out on the "but why?" part. Thanks again.

Thanks again Kevin. I made this work for me with a bit of retooling the app in question. Thanks for spending your valuable time helping me out.

Hey Quinn, And now I know! :-) I'm going to accept Kevin's answer since .taskIsWaitingForConnectivity provided a solution that is acceptable (albeit with much more code). I hope that Apple reviews this informational only API and releases the chains for truly independent watchOS apps. I appreciate you spending your valuable time to respond. Respectfully Randy

Hey Kevin, thanks again. Marginal success, but doesn't come close to the usecase I've provided. Appreciate your help and feedback.

Still thinking...and now feel a bit put off by your comment. "it isn't the silver bullet..." - but why? I've proven otherwise with about 15 lines of code. Please tell me why it doesn't work after I've proven to myself that it does exactly what my use case requires.. If the issue is battery life with polling involved, you've just shifted the polling requirement to us. I doubt we can be nearly as efficient as the framework. Sorry to be harsh, I appreciate your time and feedback.

You know, thinking about your "magic bullet" statement... Isn't my use case the same use case that API is used to accomplish on every other platform in the ecosystem?

'...talking about other ways to make it clear to users of your app what's happening and why would be the reason to come and chat with the engineering team. " Yes, that is quite reasonable. I think Kevin just made your point for you. Thanks for your feedback.

Thanks Kevin. You've clarified the workflow for me. I had looked at, but not admittedly tried that approach. I'll give a try.

@Frameworks Engineer Thanks for the comment. I do not agree with your premise "it's impossible to interpret the response". I submitted a WatchOS autonomous app - it is clear they are unable to install that app on an iPhone. Second, Apple provides absolutely no resource that answers the question: "What UIRequiredDeviceCapabilities are required/available for WatchOS?" Here is the key question: "What do I need to register as UIReqiuredDeviceCapabilities specifically for an autonomous WatchOS app?"