I'm actually developing an application using Google Drive SDK. I don't want to create a listing or register my app into Chrome Store. Anyways, my web app is able to connect to my personal GDrive account and upload a file without Chrome Store intervention just using Oauth authentication and my own API key.
But if I want "Open with" feature in my application, is it necessary to register it in Chrome Store, or can I use it without registration?
"Open with" feature allows to open file from Google Drive directly with any application associated for its file extension. For example, 8reader app allows me to open .epub files
Correct, currently for "Open with" functionality you need to register your app in the Chrome Web store. You no longer need a Chrome Web store app to access the Drive API (as you say). We are looking to improve this usability so users can install your app without the Chrome We store. Stay tuned!
Related
I'm looking to launch a single web app that works as a PWA for web users and a TWA for users wanting to download it from the Google Play Store. The app includes a yearly subscription so I'll need to implement separate payments methods for the PWA and TWA in order to comply with Google Play policies.
With this being said, is there a way to identify with JS if the user is viewing the PWA vs the TWA app from the play store? Perhaps something unique to check in the global window object?
Or, is it recommended to publish a whole new version of the app used for the TWA to a different URL that only supports the Google Play payment option.
Any info would be great. Thanks in advance.
Hello is a possibility to detect when app is opened using google assistant. My initial plan is when the app is opened by google assistant it will run a specific command on my app and run that command.
App Actions "let users launch specific features in your app using the Google Assistant."
Along certain verticals you are able to add information to your manifest that will allow a user to open your app to a specific activity with some additional information like parameters.
My app has been published for a couple years and all was well, Google play services was working and the app was integrated with Firebase. Then I upgraded to app signing, and in doing so somehow I managed to have the wrong OAuth client ID show up in the google_services.json file. In the Firebase developer docs it says you can delete your Firebase project then create a new one, importing existing app. When I do that it creates yet another OAuth client ID, ignoring the one in Game Play Services.
Signing in with Google works, but scores and times are not being posted to Leaderboards. I want to continue using Firebase for analytics, dynamic links and app invites. Does anyone know how to proceed to get back to having functioning leaderboards and achievements?
I have solved this issue. First, you'll know you have this issue if the OAuth client ID in your google_services.json file does not match the Oauth Client ID under "linked apps" in game play services.
The solution is to:
1) Unlink your app in Firebase, by going to settings, integration, and clicking un-link.
2) Next, go to the developer console and under game services, app details, you should be able to click through a link to see your app in the app console. There you'll see the Oauth ID. If it does not match the one in your google_services.json file, delete it.
3) Go to "linked apps" in game services, and create another Oauth client ID by clicking "link another app".
4) Once you have linked your app again, you should see a link that says "Add Firebase to your app". Click that link to add Firebase, and follow the steps.
5) Make sure to download the new google_services.json file into the app\ directory of your Android Studio project.
6) Re-build your project and you should be all set. Note that the Oauth client ID in your google_services.json file will now match the new one you created in the Developer Console.
Creating an AIR desktop application that has the ability to upload images to a Facebook user's account.
Even though this is a desktop application, in order to integrate with Facebook you need to embed a 'webview'. So I am confused as to how I should define this on Facebook? From Facebook's point of view, is this a web application or a desktop application?
https://developers.facebook.com/docs/facebook-login/review/requirements#platforms:
“Desktop apps should submit a Web platform and include detailed screenshots or a screencast of the integration.”
Choose a dummy address for the Website platform (such as http://localhost/), and mention the fact that this is not actually a website app, but a desktop app, very explicitly in your review instructions.
Actually i followed this link google drive sdk for develoeprs
And i configured all things what they mentioned in the above link. But the problem i am facing was the sample app DrEdit was not listing the text files on ios simulator after logged in and after i gave the permission "Allow Access" even i am having some text files in my google drive. Any thing i did wring here?. My another doubt was why there is a difference between DocuDign Ink ios app permissions and DrEdit app permissions. Please check the screen shots here i attached one i took it from DrEdit from simulator and another one from DocuSign Ink ios app from my iPad.
Note:
DrEdit app shows the permissions: "View and manage Google Drive files that you have opened or created with this app". But I would like to see the permission like this: "view and manage any of your documents and files in Google Drive". How and where I can change the permission?
DrEdit uses the limited drive.file scope that only allows it to access files that it created or that the user opened with it.
DocuSign instead requests the full drive scope that allows the app to manage all user's Drive files.
It is strongly recommended to request the limited scope when possible. For more details about all available scopes, check the Google Drive SDK documentation:
https://developers.google.com/drive/scopes