Not an expert, but this doesn't make a whole lot of sense to me - Unless the browsers on these devices are quite different (try Chrome on IOS, maybe?) cross-frame blocking is cross-frame blocking. It should happen everywhere.
You might need to play with the X-Frame-Options setting of Tableau's web server (httpd.conf) to enable it to allow this behavior. This is bad for two reasons:
- Less secure
- Modifying httpd.conf on your own puts you outside of support.
You might want to try Tableau Support on this one.
Yes, I will try support. I am just a little bit confused as to why it fails on Android but works elsewhere.
Additional information: we are using trusted authentication. So I am wondering if the whole thing is not a bug with Android + trusted authentication in an embeded frame.
Some workbooks do load correctly, others don't. I will follow up with support, but for the community's sake, I will come back here and let know what the issue is in case someone else encounters it.
Ok, I would just like to know.
Can anyone who does viz embeding (without Tableau Public) try on an Android device?
One thing which is REALLY weird is that for some workbooks, it works, and for others, it does not.
Well, I feel like I'm talking to myself here -
I enabled CORS on the Tableau Server, but that did not solve the issue. So I decided to try some other browsers "just in case".
Firefox on Android was giving a different error, something about "Access Denied to set property: Orientation".
UC Browser: this one works!
Chrome: Fails (CORS)
Browser: Fails (CORS)
So it seems the problem might be a bug on Android...