How to reset `WCSession.remainingComplicationUserInfoTransfers` during watchOS complication development or testing?

Is there a way to reset the complication communication threshold WCSession.remainingComplicationUserInfoTransfers during development or testing?

I tried deleting the app and reinstalling and this threshold does not appear to reset.

During development we get only 50 tries per day? After that pack up and go home?

Yes. Go into the iPhone's Settings app, and scroll down to "Developer". In that screen, scroll about 75% of the way down and you'll see WIDGET TESTING and a switch to turn on Widget Developer Mode. That should ignore the constraints.

It would be awesome if it did. This is as close to an answer as I've found, so thanks for that.

However, when I log remainingComplicationUserInfoTransfers I still get 0 after using up the allotment earlier today.

Is there another step I need to follow?

I uninstalled and reinstalled the app from Xcode after toggling this setting.

I also power cycled both iPhone and watch, with no luck.

Hmmm. That should've worked. Maybe you need to delete the app from the Watch and reinstall it? Xcode has many weird undocumented quirks, sadly.

I also tried re-installing on the watch, still no luck.

What is the expected result?

A) remainingComplicationUserInfoTransfers will always be set to a positive number

OR

B) Even if remainingComplicationUserInfoTransfers is 0, transferCurrentComplicationUserInfo(_:) will still function instead of falling back to transferUserInfo(_:)

How to reset `WCSession.remainingComplicationUserInfoTransfers` during watchOS complication development or testing?
 
 
Q