I have a receiver page which receives an url an it is used in an iframe.
I want from my android app have controls to make scrolling on that iframe, is it posible?
I am able to send messages from my android app to the receiver page without problem, but can't make scrolling.
I received the message,
"Blocked a frame with origin "receiver url" from accessing a frame with origin "iframe url". Protocols, domains, and ports must match."
I know this is related with same origin policy, but how chromecast extension for chrome works? because I see it works well there.
The Chromecast extension generates a video stream of the content in the Chrome tab. The scrolling is happening in the sender not the receiver.
Also, doing scrolling on the receiver would likely be a bad user experience for the Chromecast device. That kind of interaction is best suited for the sender device. The ChromeCast UI is best suited for fullscreen experiences that don't require scrolling.
Related
I have the MS team's custom tab application for the team's. It is an angular application, it has some internal navigations like navigating from one view to another. When I am sending a notification using the sendActivityNotification API call, it reaches to the mobile app. With the click of the notification, the application loads and it works fine.
But after navigation, if I tap on the back button of the device or (<-) button from the MS team's app header then it behaves like loading the history instead of navigating back to the activity(Feed).
Thanks,
Pratap
I'm developing a PWA that exchanges public keys between friends using SMS.
The process begins with one person clicking a link to a partially populated
SMS url and opening a window - the portion of the url which is populated is
the body, which points to a dynamic url generated by the app.
For example:
"sms://&body=http%3a%2f%2facme.com%2findex.php?id=128409234823432"
What remains is the selecting of a contact from your phone book to send the link to.
The problem I am facing is the browser loses focus to the SMS app and there is no
way to programmatically bring the browser back to the foreground if the SMS is sent
or even canceled - This causes confusion for non-tech users as they think
the app has been closed.
Is there a way to return to the browser after the user sends the SMS?
I am unable to cast with my styled receiver from chrome browser.
I have an unpublished styled receiver chromecast app. The "preview" button works fine. My testing device is registered with status "ready for testing". The send serial number checkbox is checked from my android app (OS X app never finds chromecast, so I cannot verify with another app).
Setting the app ID to be my application ID (which seems to be an 8 digit number in the SDK developer console) throws a session error when I try to connect. Changing this back to the default app ID has success. I registered a second identical application and tried with that ID as well.
What could have gone wrong? I am unable to connect to the debugging console, but I read on SO that you need a custom receiver (not styled receiver) to connect.
I am able to connect to the custom receiver as defined in this sample receiver as well.
Is there no testing for styled receivers?
Note that there is one oddity about my setup, and that is that the chromecast is connecting to a wifi network that has been shared by my macbook, not a normal router.
You don't need a custom receiver to be able to debug, using your own Styled receiver is adequate (you basically need to have your own App Id). I would suggest you double check your serial number; take a photo and enlarge that to make sure it was read correctly.
Solution was use a router instead of sharing internet access via Wi-Fi from my macbook. Re-checked the send serial number box, restarted device and everything worked.
I have a weird situation, My app was working fine and I was able to select my chromecast device and see my receiver application without problem, so my chromecast is whitelisted.
Now my app doesn't work, the chromecast icon is disabled and I can't select my device.
Basically this line was working fine
mMediaRouteSelector = MediaRouteHelper.buildMediaRouteSelector(MediaRouteHelper.CATEGORY_CAST, getResources().getString(R.string.app_name), null);
but now it doesn't. Why? any ideas?
But this line works fine:
MediaRouteHelper.buildMediaRouteSelector( MediaRouteHelper.CATEGORY_CAST)
Of course I can't see the receiver app (html).
I am thinking maybe my chromecast is not whitelisted, just like the beginning when I started with the development.
Any ideas?
Is there a way to check if my chromecast is whitelisted or not?
Thanks in advanced.
Can you access your Chromecast device through your Chrome browser via:
http://[IP address of your Chromecast device]:9222?
If yes, then the device has been successfully whitelisted.
Make sure the "Send this Chromecast's serial number when checking for updates" option is checked in the Chromecast setup. This option gets cleared if you do a factory data reset.
I'm using the code from this article, with phonegap app.
http://blogs.msdn.com/b/glengordon/archive/2011/12/02/phonegap-on-wp7-tip-3-sending-sms-and-intro-to-plugins.aspx
The plugin works all fine, but when the SMS is sent, I want to return to my app automatically. Is this possible? If its possible to send an SMS without go to the default integrated sender, it could be even better.
I'm a newbie to C# and windows phone apps - please help me ;)
there is no way to avoid the integrated SMS sender due to security reasons. User will return to your app after hitting the Back button on the SMS conversation page (that is esured automatically because of the stack-controlled nature of paging in WP7, but will not return after hitting the home button (again, this behavior cannot be prevented in any way) and your app will be suspended (possible to return to it by holding the back button and choosing it).