I have a google drive app. It is setup to be a drive app and the open url is given in the app details.
Everything works well, but for some reason when the user installs the app it is not displayed in the "Open with" list of apps.
the app is setup to use google documents and docx (this is given in the default mime types).
I also had pdf in the mime types and it was working for them I switched it off and it was correctly turned off.
Any idea why an app might not be showing up in the "open with" menu by default?
Please get back to me as this is having a huge impact we are getting a lot of questions from users that are not being able to find the app..we have over 1000 installations already.
The app also has a launch icon setup on the manifest file. I don't supposed this affects it's behaviour on drive?
"launch": {
"web_url": "http://mail.google.com/mail/"
}
Best regards,
Joao Garin
Have you enabled both the Drive API and the Drive SDK in the Google Developer Console?
See the details on enable the drive platform and make sure you have everything configured properly.
Related
this is question related to google apps script and Google Drive.
Is there any way to construct a URL for a file that causes opening that file in desktop application?
I'm basically asking whether it is possible to access "Open With" application list programmatically and pick up one from listed applications.
Now, when I get the URL, it causes opening another screen where I need to pickup an application and only then it starts opening. I would like to skip that step and open the file directly in a given desktop application.
Thank you!
Petr
"Open Width" requires having Google Drive for Desktop installed, having installed a Chrome extension and using Chrome.
Considering the above, since Google Apps Script server side code hasn't access to user environment it's not possible to
"Open With" application list programmatically and pick up one from listed applications.
I am working on a requirement where we need to support the docs in offline mode, I am planning to integrate the Google Drive iOS SDK and I would like to know weather its possible to get Offline access of google drive using the SDK approach
Google Drive "offline" is available only for files Every file you edited or created while offline will sync back with the online version of Drive when the network connection is reestablished (click on Switch to Docs online or load an entirely new Google Drive page with a refresh).
Steps to make a file offline:
Go to your drive and select a file in a folder/individual file.
Click on "i" (information) which is next to edit, navigates to Details.
You will see an option "Keep me on device". Turn it on.
This file becomes offline available.
Check this link for more information.
I have created a realtime document on Google Drive. When I attempt to share this file with someone who doesn't have my app installed, the file shares successfully, but when they click the file it says "Sorry, no preview is available".
This realtime document is a shortcut file. How do I get it to prompt the person to authorize my app?
I'm using the Realtime Playground as my example as I'm not sure of the specifics of your application.
App authorisation
When you created your application you visited the Google API Console and created a project with Drive API enabled. At some point you copied "Client ID" from the Google API Console into you application ID code.
In the realtime-playground case APP_ID is set in the javascript file rtpg.js (you might not be using JavaScript but there will be an equivalent step for other languages).
rtpg.APP_ID = '840867953062';
File creation
I believe that any drive realtime document/shortcut you created with your application will contain a reference to the creating application (mostly likely in the form of the client/application ID you obtained above).
File sharing
Once you can see your newly created Google Drive Realtime document/shortcut you can share this with somebody else using the normal Google Drive sharing methods. At this point they can see it but cannot do anything apparently useful with it. This is where I believe your application may differ from the realtime-playground example.
Integration with Chrome Web Store
On the GitHub repository for realtime-playground you'll notice a cws (Chrome Web Store) directory containing the stuff necessary to deploy the realtime-playground as Google Drive application in the Chrome Store including screenshots to be used. If you look at the manifest.json file you will see another reference to the client id:
"api_console_project_id" : "840867953062"
So if I share a realtime-playground file with somebody who doesn't have it installed, then clicking on the file in Google Drive will result in a "Connect app" popup which will try to locate the corresponding Chrome Web Store Drive app (using the common id as the key) and this will show something similar to what you might see if you found this application directly in the Chrome Web Store.
The manifest.json also contains:
"app" : { "launch" : {
"web_url" : "https://realtimeplayground.appspot.com/" } }
which tells Google Drive what to do when the installed app is called.
So my guess is that your application doesn't work like this as you don't yet have public visibility of your app in the Chrome Web Store.
See also: Create a Chrome Web Store Listing
I hope this helps.
That is fine. If you open your eyes, you will notice that Playground demo does not provide any preview either
Yet, you see, the associated app is available. You can click it and open-with works normally. Your app-created files operate similarly. They are associated with your app by default. You can open them by open with rather than by preview. Can you? No, you cannot. But that is another question.
Otherwise, I see no cleverness in associating your file with chrome extension rather than with your app.
How do I get it to prompt the person to authorize my app?
I recently had a similar question. Instead of linking your files with extension in chrome, pass the direct link, like http://your-app#fileId=..., as playground demonstrates to your shared fellow if open-with fails.
The preview seems to be another story.
Wait, Do you mean that I need to create a new fresh account to test how your file is unassociated with your app? How do you preview the files in your primary account? If you know how to preview you may answer my question, at least partially. But why do you associate authorization with preview?
I need some light on the matter of Chrome Webstore registration.
I'm still confused despite searching through the web: the "app" will be only private for the site (we're trying to develop a Elgg plugin for our website that will allow users to access their drives).
1) for testing, do I need to register it (I did a search but some say yes like in the Google Drive SDK documentation, some say no in the google-drive-sdk tags)?
2) when the plugin is finished, tested and ready to go live for our users, do I still need to register it and pay 5$?
Thanks you for the answer you can provide us.
You don't need to register your app on the Chrome Web Store if you don't want to integrate with the Google Drive web UI: having the option to create a new file or open a file with your app directly from Google Drive.
Also, it might be easier for you not to create a Chrome Web Store listing while developing.
If you do need to integrate with the Google Drive web UI, but don't want your app to be public, you can publish your app to Trusted Testers only.
I have released an app for Google Drive in the Chrome Web Store. I thought it might get added to the Google Drive Collection automatically, but that didn't happen. Is there any form I have to submit?
For your application to appear in the collection of Drive apps your Chrome Web Store app's manifest file need to specify the Google Drive container and your API console project ID as described in this document.
Then your app's listing should get the "Works with Google Drive" badge and, given a few minutes delay for indexing, your app will appear on the collection of Drive apps.
Beware: you may not see it there as a listing doesn't appear for you in that collection if you have already installed it on your browser. It will appear to all other users who have not installed your app yet. To make sure it's there: try looking at the collection with another browser (FireFox for instance).