For the purposes of ADBTuner, there seems to be some overall confusion on this.
It is very rare that you would need to identify a specific activity (the part after the /) with an app that supports deep links. Triggering a specific activity to get the app to open usually doesn't move the needle in making the app work with ADBTuner. The package name (ex. com.sling) and a valid deep link URL is all that should be needed.
The situation is different if you are looking to open the app as part of a sequence of automated commands with hdmi-for-channels or ah4c.
com.tennischannel.tceverywhere.amazon is the package name.
Unfortunately this app does not officially have deep link support. There are no activities that trigger android.intent.action.VIEW" and there are no resolvers that accept data (eg. URLs).
$ adb shell dumpsys package com.tennischannel.tceverywhere.amazon
Activity Resolver Table:
Non-Data Actions:
android.intent.action.MAIN:
e58baac com.tennischannel.tceverywhere.amazon/com.firetv.web.MainActivity filter 29c68da
Action: "android.intent.action.MAIN"
Category: "android.intent.category.LEANBACK_LAUNCHER"
Category: "android.intent.category.LAUNCHER"
AutoVerify=false
Receiver Resolver Table:
Non-Data Actions:
com.amazon.inapp.purchasing.NOTIFY:
1b01375 com.tennischannel.tceverywhere.amazon/com.amazon.device.iap.ResponseReceiver filter 9f72285
Action: "com.amazon.inapp.purchasing.NOTIFY"
AutoVerify=false
If you want to open the app you can specify com.firetv.web.MainActivity as the activity, but this most likely won't help with ADBTuner.
What happens if you just use com.xfinity.cloudtvr.tenfoot (just the package name, without specifying an activity)?
I don't have an Xfinity account so all I get is a login screen, but it did open the app as expected based on the activity resolvers reported by the app (see screenshot I posted the other day). I know you have a working solution, I'm still just curious why it's working that way.