google-chrome-app

I'm testing scenario where I call a hangouts web page in separate window but application doesn't have access to microphone and camera - buttons are red and message says that "Hangouts can't use the selected microphone/camera". I have included in permissions "audioCapture" and "videoCapture" . What has to be done to make it work? Edit: After allowing media app has access to camera and microphone - I can see that in settings of hangouts but picture and voice are not transmitted over the hangouts to other participants. Is there something I have to set for streaming media? I already have this

I am constantly getting this error when uploading my app: An error occurred: Failed to process your item. This item is not an app, please remove app section from manifest. This is the manifest file for my Chrome app (based on the Getting started - Hello World tutorial): { "name":"App name", "description":"app description", "version":"1.0.4", "manifest_version":2, "app":{ "background":{ "scripts":["background.js"] } }, "icons":{ "16":"icon_16.png", "18":"icon_128.png" } } I tried to install my application locally through the Chrome extensions section and it works just fine. I can see it

I am looking to integerate IAP ( https://developer.chrome.com/webstore/payments-iap ) in to my extenstion but I can't seem to find a way to test payments. If I switch the env to sandbox I get and error of type "ENV_NOT_SUPPORTED_ERROR" Quoting the docs you link: Testing purchases Prior to publishing your app to the world, you can test the In-App Payment experience by publishing it only to trusted testers. When your app is published to trusted testers, the purchase flow will proceed normally, except they will not be charged. 来源： https://stackoverflow.com/questions/28311236/testing-chrome-in-app

I'm using the HTML5 FileSystem API in a Chrome Packaged App to write to a log file. I want the user to be able to download this file, so I tried something along the lines of: fs.root.getFile('log.txt', {create: false}, function(fileEntry) { var url = fileEntry.toURL(); // do something with the file url }); This doesn't help though, because the URL is something like filesystem:chrome-extension://eekedjcagggbfigdmifkmhkjbhiklnpj/temporary/log.txt and it's not possible to open it somewhere. What technique would you recommend to make a FileSystem API file in a Packaged App downloadable? Edit:

To put it bluntly, do Mobile Chrome Apps have anything to do with chrome at all? After all, it seems reasonable to expect that as it has Chrome in the name. This question stems from the fact that as I was porting my 'chrome based mobile app' (which does not run in the 'Browser'), I got a huge string of weird errors and for the first couple of hours I had no idea what was happening. NOTE: This question is out of date , Mobile Chrome apps now works differently as outlined in the edit section of the main answer: By default, Chrome Apps for Mobile leverage an embeddable Chromium WebView provided

I'm using the dev-channel v23 of Chrome and I'm working with the new Chrome Packaged Apps platfrom. One purpose of the new platform is to take packaged apps "out of the browser" and give the packaged app top-level window status. I have a lot of things working, but the window that Chrome opens for me has no title bar, or minimize, maximize buttons. It does have the chrome's custom close button (like the one on internal windows like settings dialogs). You can hide the close button, and provide custom min/max/close functionality in html/js but it breaks the UX in functionality and appearance. If

I'm writing a packaged app for Chrome that has a webview tag where I load my website. Is it possible for the website JavaScript code to detect that it was loaded in a webview? The navigator.userAgent property has no clues. Other approaches in addition to the one mentioned by Jivings: Load a slightly different URL in the webview, e.g., http://example.com?in_webview=1 , and reflect that in the JavaScript served by the site. Same idea but use a #fragment. I don't know for sure whether a #fragment will work correctly, but it if does, it's nice because the server won't get confused by a strange

I'm trying to authorize with chrome.identity.getAuthToken() to get token for Picasa web service. I couldn't find Picasa API in Google Developer Console and set its scope to " https://picasaweb.google.com/data/ " oauth2 part of manifest.json. Picasa docs say that I can skip this step. chrome.identity.getAuthToken({ interactive: true }, function (token) { if (chrome.runtime.lastError) { console.error(chrome.runtime.lastError); } else { console.log(token); } }); getAuthToken() always ends with an error "OAuth2 request failed: Service responded with error: 'bad client id: {0}'". If no scopes are

today when testing android apps with the arc runtime, which for some reason updated without me noticing. and all I get is that it immediately crashes. I have tried repacking using the arc welder which is somehow also updated with no results. UPDATE: since i did not see any progress on the stable channel i tried this on canary channel to see what might be causing the crash and found the errors "plugin not ready" and "plugin crashed: captured minidump" is there a way to solve these errors? 来源： https://stackoverflow.com/questions/32408792/arc-apps-crash-with-google-chrome-45