I have a Google Drive app, which is registered as my default opener on Google Drive. This works perfectly fine when opening files using drive.google.com - When I open a file with my App, the app gets given permission to open the file and I can see that in the drive.google.com web interface.
However I recently tested this on a chromebook, and when I open a file using the Files app, I get sent to my app, however it gets a 'File Not Found' error. When I check the permissions for that file, my app hasn't been given access to it.
If I open the file using drive.google.com and then try opening using the files app again, it works since my app has been given access to the file when I opened it using drive.google.com
Seems there is a bug in the Files app on Chrome OS here, where it doesn't set the permissions to give the app opening the file permissions to access it, whereas the web interface does that correctly. Has anyone else run into this and/or should I report this as a bug to Google?
Using ChromeOS 5116.115.4 + Chrome 33.0.1750.152
This was indeed a bug, and it's fixed in the upcoming chrome 34: https://code.google.com/p/chromium/issues/detail?id=332332
Related
I use Google Chrome Dev (109.0.5410.0) on Windows 10.
After recent update I noticed that I am unable to open any .html file from my local disc. Let me describe the scenario.
For example:
In my desktop there is a file as C:\Users\soumyadipd\Desktop\test.html
Now if I drag-and-drop the file to chrome then it opens using the URL file:///C:/Users/soumyadipd/Desktop/test.html in address bar.
But if I double click the file to open then the file failed to open because the URL is http://%22c/Users/soumyadipd/Desktop/test.html%22"
Anyone faced this problem ? Or is it a Chrome bug? Or any other solution is there?
I just upgraded to Google Chrome v73.0.3683.103 and I am now unable to view FTP sites in Chrome. Instead of Chrome loading the FTP directory listing in the browser, it downloads a file named download which contains a directory listing.
How do I get the ability to view the FTP directories directly in Chrome back?
I have tried going into Internet Options > Advanced and clicking on the "Enable FTP folder view (outside of Internet Explorer)" but, that didn't seem to do the trick.
In-browser FTP was deprecated back in v72. I hadn't updated Chrome in a few releases. I have rolled back to v71 until I find a better workflow substitute
DETAILS: https://developers.google.com/web/updates/2018/12/chrome-72-deps-rems
I am trying to install App using App Manager in Firefox OS device. But my problem is I am unable to push any of the apps which are published on MarketPlace. It show that
The webapp manifest isn't a valid JSON file: SyntaxError: JSON.parse:
unexpected character at line 1 column 1 of the JSON data at:
https://marketplace.firefox.com/app/pacman-canvas can't be opened
So can anyone suggest some way to push the app to my device using App Manager only?
It's pretty easy. On the Marketplace page (in Firefox desktop) open the marketplace page for the app. Then open Devtools and select the Debugger. In the debugger, break in file iframe-installer.html, on this line:
installPackage(e);
Now click the 'Free' button, the debugger will break on this line. In the console you now type:
e.data.data.product.manifest_url
This will give you a URL. If the URL is located at someone else's webserver (like Pacman), e.g. http://pacman.platzh1rsch.ch/pacman-canvas.webapp, you can (in the App Manager) click 'Add hosted app' and paste the URL. However you will need internet on the phone the first time you use the app (because its hosted app).
If the URL is a Mozilla URL (https://marketplace.firefox.com/app/etc.), you can open the link in your browser. Open the file. You now have a JSON file in which you need to look for the package_path key. F.e. for Recorder it's
"package_path": "https://marketplace.firefox.com/downloads/file/258677/recorder-1.1.zip"
You can now download this ZIP file, unzip it in a folder, and add the folder as a Packaged app.
For apps in the marketplace, you best solution for getting them on the phone is to just use the marketplace app. That said if you own the app in the marketplace you should be able to look at the manifest url of the app using the edit listing marketplace button. If this is a hosted app you can you use this manifest url in the add hosted app entry box within the app manager to add it and then push it to phone. On another note you can debug the system apps by using the procedure described here:
https://developer.mozilla.org/en-US/Firefox_OS/Using_the_App_Manager#Debugging_Certified_Apps
We have an app that integrates with google drive SDK, and open/new URLs are configured in the API console, working well on the desktop. The "Mobile Browser Support" checkbox is ticked. Still, when I open the Google Drive web page from a mobile browser (Ipad), clicking on a file link downloads the file instead of opening our application in the browser. Any idea if this is a config problem or a bug in the mobile Drive UI?
From what I've tried, on the mobile Google Drive website, a file is opened with your application instead of being downloaded only if the file has the mime-type of your application. This mime type looks like the following:
application/vnd.google-apps.drive-sdk.nnnnnnnnnn
You can find it by requesting information about your app using the API [1].
[1] https://developers.google.com/drive/v2/reference/apps/list
I've made a few chrome apps and published them to the chrome store and when I install them then appear in my chrome://chrome/extensions/ page. When I package an app into a crx file and install in manually, my app works fine and shows up on the new tab page but not the chrome://chrome/extensions/ page. Am I missing something in my manifest file or will only store apps show up on the extensions page?
The correct way to have apps which are under development show up in the extensions page is to load them as an "load uppacked extension" from the extensions page. You just point it to the parent directory of your app, then as you make changes, you just save and refresh your app. When you are ready to publish, just zip it up and upload it to the store.
There's no need to manual package your app unless you are distributing the app outside the chrome web store.