I want to enable SharedArrayBuffer in a web app in which I'm already using the Google Picker and Google Drive "embed item" UIs. I'm testing in Chrome 103.
I changed my web server settings to use COEP "credentialless" and COOP "same-origin". After doing this, Dev Tools' Application pane confirms that SharedArrayBuffers is available, and I'm able to instantiate them in code. However, now the i-frames containing Google Picker and Google Drive embed UIs fail to load due to missing CORP response headers.
Is this a known issue with these Google widgets, or am I missing something?
Here are the failing requests:
https://drive.google.com/file/d/[GOOGLE DRIVE FILE ID]/preview
https://docs.google.com/picker?protocol=gadgets&origin=https%3A%2F%[MY_ORIGIN]&oauth_token=...
Picker error
Google Drive embed item error
dev tools application error report
dev tools network error report
Related
I have uploaded APK since 24 hours in internal app sharing as a any one can download app from link.
but when try to open that link it's showing "Item not found".
Here is screenshort of Manage testers settings.
I want to do something like any can download app from link(without adding tester accounts)
Tick the option you can see on the screenshot below.
According to the internal app sharing documentation (See "Troubleshoot issues"), there are many reasons why this could be the case, but they often boil down to the users not being eligible to receive the app in production (e.g. incompatible device, not in the country the app is distributed in, etc.).
Note that we (Play Console team) understand that this is not ideal and are actively working to remove this limitation.
From Developer Side
1.Go to PlayStore
2.Select Your app from List
3.in Side Bar select "Development Tools"
4.select "Internal App Sharing"
5.In "MANAGE UPLOADERS" try to add email id of ur tester
or go to "MANAGE TESTERS" and check "Allow testers outside of email lists to download internally shared builds" and Save it
upload app using this https://play.google.com/apps/publish/internalappsharing/
7.share url of InApp Shared with testers.
From Tester Side
How authorized testers turn on internal app sharing
Before authorized testers can download apps using internal app sharing, they need to turn on internal app sharing on their Google Play Store app.
Open the Google Play Store app Google Play.
Tap Menu Menu > Settings.
In the “About” section, tap the Play Store version 7 times.
After the Internal app sharing setting appears, tap the switch to turn on internal app sharing.
Tap Turn on.
In Google Cloud Platform I have enabled the Apps Marketplace SDK to publish a sheets-on to Marketplace.
In APIs & Services > Apps Marketplace SDK > Publish I am unable to upload a screenshot. I keep getting Not saved.
see here:
I am using the correct size screenshot and have tried many different sizes and image types. ex. 640x400, 1280x800 all the recommended sizes. I have used png and jpg.
I can't click the publish button until a screenshot is uploaded. This is weird because I was able to upload an image for application banner without issue (as shown in the image above).
Any ideas why I am getting this Not saved message?
You have to upload your screenshots into the Chrome Web Store Developer Dashboard.
Look at this FAQ.
Please see the warning at the top. The Publish tab should not be used yet for add-ons created in Apps Script (Docs, Sheets, Slides and Forms).
Those details have to be filled in Chrome Web Store and after about 48hs the publication should be available in G Suite Marketplace.
The G Suite Marketplace team is working on simplifying the publishing process and in the future it won't be required to publish in Chrome Web Store.
Is it possible to disable Google Drive UI integration, for our new Google Webstore App?
Our web app uses the Google Drive API scope for managing users' documents, but we don't yet support Google Drive UI integration (i.e. we don't have a page which can take in a document ID and show appropriate content. The user would have to navigate from the home page instead). The app has been rejected from the GAM on this basis, and Google directed us here for technical support.
I have seen the following in the UI:
In the 'Apps Marketplace SDK' settings, the checkbox for 'Google Drive SDK' is checked & disabled here (project ID replaced with XXXXX): https://console.developers.google.com/project/XXXXX/apiui/apiview/appsmarket_component/googleapps_sdk.
In the 'Drive SDK' settings, I cannot find a setting to disable Google Drive UI integration here (project ID replaced with XXXXX): https://console.developers.google.com/project/XXXXX/apiui/apiview/drive/drive_sdk
We do hope to integrate with the Google Drive UI in the future. In the meantime we would like our new app to be available to our customers, for installation by their domain administrators.
Is there a known way to achieve this?
Thanks
You should be able to disable the UI integration from the Developer Console.
In the Drive API's "Drive UI Integration" tab, find the "Creating files" checkbox and make sure it is unchecked. Also remove any MIME types you specified. You may want to uncheck any of the other checkboxes below "Creating files" that you may have checked. Save those changes.
In the GAM SDK settings, you can uncheck the "Drive extension" box and save. That should disassociate your GAM app from being a Drive app as well.
I'm using my android app's website (http access) to host the receiver code during my development of my app w/ Chromecast. I have it working fine and ready to get the custom receiver code (html, css, js files/directories) on my Google drive. The directory on my Google drive holding all those files/directories is shared publicly.
The problem comes in when I setup my Chromecast (in Google Cast SDK Developer Console) to point to the new location of the index.html file, I right mouse click (in the Windows 7) the index.html and choose Google Drive/Share. The "link to share" value isn't the correct value to put into the Google Cast Dev Console. When I go to cast my app I get the .html content shown on the casted screen.
Any help would be appreciated.
Thanks,Jim
I wrote a web site with google earth api and it is working fine.
I want to open this site via mobile browser, and it's giving me the following error:
"the plug-in of google earth is available only for win and mac".
How can i get through it?
Thanks.
:)
I am having a similar issue. I wish to try and use Android WebView instead of setting up GooglePlayServices at this time for an art project
I have the example loading just fine on Windows and Mac, but I need this for my Android art project.
My source code can be viewed at this link below:
www.rennakanote.com/earthdraw
I will attempt to see what I can try from Google Maps V3 APIs as per your instruction JasonM1 and see if I find a way to load this in Android.
Unfortunately, the Google Earth Plugin and Google Earth API is currently only supported on the Windows and Mac platforms.
Full list of which OS versions and browsers are supported can be found here:
https://developers.google.com/earth/documentation/index#installing_the_google_earth_plugin
The mobile version as well as the Linux version of Google Earth does not currently support the Google Earth plugin.
If you redesign your web site using Google Maps V3 APIs then it would be supported by mobile and desktop web browsers. Google Earth is a thick desktop and has restrictions especially with respect to mobile devices that a pure web application such as using Google Maps APIs can avoid.
Although the Google Earth plugin doesn't work on mobile devices, both Android and iOS devices have a Google Earth app available for them.
Thus a good way to show your data on both desktop and mobile devices is simply to publish it as a KML file, which will load in all versions of the program. The mobile devices don't actually offer a "load file" option, but instead rely on the fact that if you present the device with a KML file with the correct mime type, then the system works out that the Google Earth app is the appropriate one to display the file.