Thanks, @jantzen. We took a look at our code and found that @Horia's
answer did indeed point us in the right direction. One of our MVPDs was
configured for SSO on the backend when in fact they did not have it.
Appreciate the help!
(bump)Anybody at Adobe care to chime in on this? Knowing whether we
should be designing for a unified SDK moving forward or some kind of
dynamic build-time solution would go a long way in helping us plan our
Hi Gurus,We have a framework which has traditionally used Adobe Pass for
an AVOD solution. Of course since Apple released SSO we've had a number
of our brands begin participating in that program. We've been quite
successful using the Adobe Pass beta to get those clients' apps in the
store. The problem is maintaining our product for clients who aren't
interested in participating in SSO. It doesn't seem there is a good way
to disable the SSO functionality. I realize the SSO support is not part
One of our larger clients is having issues getting data in the Omniture
Dashboard whenever we update their Adobe Video Heartbeat SDK beyond
version 1.37 (on Android only). The client would like to be on the
latest 1.5x version. I’m a little fuzzy on the plugin mentioned in the
release notes, and whether it is or isn’t required. Any insight you or
your team could provide as to what might cause the Heartbeats data not
to arrive in the the client console would be greatly appreciated. I
clearly see ...