How can I test google chromecast states with appium Ios java - json

I'm running automation tests on an app that has casting button from chromecast , is there anyway to access the chromecast states in order to validate information about it, if so, is there any possibility to do that with Ios-appium or maybe just in a java code? Thanks,

Related

Trusted web activity - Digital assets link validation for intranet/private web app seem to be failing

I've followed this doc to
Create a wrapper Android app based on this sample project for my UI application which runs in non-public domain in our corporate servers.
Add assetlinks.json in my Angular 6 PWA application, with SHA256 fingerprints of my release key.
Deployed the signed apk to a Android 4.4.3 device running Chrome Dev 69 and Google play services - 12.8.74.
When I run the application, everything works fine except hiding the address bar, which makes it as a regular custom tab and not the "Trusted web" content.
I don't see any error in the log and not sure how to debug this scenario. Any help on this is appreciated.
Got confirmation from Chrome team that they are using TWA assets link validation in server side using an API call and so this solution wont work for Private web apps. Said that, they are also considering to move that logic to browser to support this use case. Will update here when I have any update on this.
Update: As of Chrome Version 72, TWA(Trusted web activity) if available in Chrome stable version and the web asset validation(to make sure the web page is yours/same as the app its loaded to) happens in browser. So this solution can be implemented for private web apps for hosting inside enterprise environment.
Also, now PWAs can be packed as regular app using TWA solution and uploaded to Play store as an apk file. Documentation on this is still being updated as per one of Chrome developer. But the solution as such is ready for use.

Citrix Receiver Kiosk App "Unsupported chrome app origin detected"

I searched all over and couldn't find my specific issue here so please excuse me if my search-fu has failed me.
My issue:
I am currently trying to create a kiosk app for my company's chromeboxes. I have the application packaged and published privately on the chrome web store. I get the app to load but once I launch the kiosk app and enter in my company's url I am presented with, "Unsupported Chrome App Origin Detected". The only thing I can find so far about this is to run the flag --disable-web-security. I can only find examples for Windows/Mac/Linux plus that isn't secure. Am I missing something in my Default.cr or manifest.json files? Is this even possible? This is on a vanilla chromebox that isn't part of a Google Apps domain. Do I need to have it added to a Google Apps for Work domain to get this to work? Any help would be appreciated.
Please add your generated chrome extension app id to storefront web.config file. Please have a look at http://docs.citrix.com/en-us/receiver/chrome/1-7/receiver-chrome-deploy.html point 8 at the end on how to do it.
Also please use 1.7 as it supports better Kiosk mode integration.

How to obtain Android Device key in AIR with Action Script 3?

I am trying to make a push notification in my game using GCM through AWS.
I have bought this ANE: http://myappsnippet.com/gcm/comment-page-2/
But I cannot get the token in my device.
Can somebody help?
Adobe AIR does not have a built-in function to get any device id, because of various platforms. You should use some kind of extension, like Distriqt's Application ANE.

Chrome Packaged App Access Chrome APIs

I'm interested in writing a Packaged App that can access data about chrome, namely the chrome.windows.onCreated and chrome.windows.onRemoved events. If I try to add a listener to either of these, I get an error in the console:
Uncaught TypeError: Cannot read property 'onRemoved' of undefined
Is there any way around this?
The other answers are correct that this isn't directly possible from a packaged app, but there is a solution that meets your needs: You can write an extension as well as a packaged app and have them communicate with chrome.runtime.sendMessage.
The user will have to install both app and extension, but you can make this easy by directing them to the chrome web store from within your application. You can read about this here: Communicating between a Chrome packaged app and a Chrome extension?
Edit: and as pointed out in a comment on that thread, there is a Chrome App Sample that helps demonstrate this in action: https://github.com/GoogleChrome/chrome-app-samples/tree/master/messaging
The chrome.windows API is a Chrome extension API, not a packaged apps API. It is used by extensions to interact with browser windows.
If you can write your application as an extension, it will be able to use that API. Packaged apps, however, don't have the ability to manipulate other windows besides their own.
One simple typo here: It is chrome.windows.onRemoved not chrome.windows.OnRemoved ;)
Note the lowercase o.

Does the BlackBerry Playbook Simulator support geolocation inside WebWorks application?

I am testing HTML5 geolocation code inside a WebWorks application for BlackBerry Playbook, using the 0.9.4 Simulator in VMWare Player. Here's the code:
navigator.geolocation.getCurrentPosition(geolocationSuccess, geolocationError, options);
Launching the application gives a popup saying:
Geolocation Request
local:// wants to access your location.
When I click "OK" this always results in a callback to the error handler function geolocationError, never the success handler.
The webpage works fine in Firefox 3.6.15 on Win 7.
Is there any way to test a successful geolocation request inside a WebWorks application in the Playbook simulator?
Updates:
Geolocation works in the Playbook web Browser, so you can test your application as a web page in the Browser.
I asked about this issue at a BlackBerry Developer Day and they confirmed this restriction. I asked them to publish a list of known limitations, they said they would look into it.
The simulator as of 0.9.4 still has no support for geolocation, according to the AIR SDK Release Notes. It's likely the same limitations apply in this case.