Is it possible to submit Chrome extension for review without publishing it automatically using Chrome Webstore API? The publish endpoint submits the package for review and automatically publishes it after it had passed the review, but it is desirable to be able to manually publish the extension.
Basically, is it possible to achieve the same result as by unchecking the checkbox on the popup window seen on the screenshot? Submit for review confirmation window screenshot
Unfortunately this is impossible so far as you can see from the doc Publishing Docs. What you can do is to publish it just for a tester (closed group) and once you're sure publish to another time publicly. That way you can control it via the dashboard.
Related
Question
How can I create a link to navigate to a Team's channel, from within a custom personal tab?
Context
I'm trying to navigate from within a personal tab to a Team the user is a member of. I've tried the only 2 options I can think of so far:
using an a tag
using microsoftTeams.executeDeepLink
But they don't work.
When clicking the a tag, the tab contents are redirect to the general MS Teams navigation page, where you can choose to open in client or web.
When using the microsoftTeams.executeDeepLink function, a result is returned containing the error message The executeDeepLink API is not implemented in this client.
It seems the API only works on team (configurable) tabs on the desktop client.
#Nsevens This feature is not public yet. Could you please try this in the Developer Preview
What I want to build:
I want to build a website where users can connect their google calendars (this will use Google Calendar API's)
and view their calendar events, as well as edit them, and create new ones.
My problem:
In order to do so, google says my app needs to be verified, which can take weeks, and I also need to set up terms of services pages, privacy policy pages
I also need to supply authorised javascript origins which MUST start with https, which of course is a problem during development, since my origin is http://localhost
I also need to set up support emails and homepage link
Question
I just want to start building my application without having to set up a whole production-ready website eco system.
Is there anyway I can use these Google Calendar APIs for editing/creating calendar events locally, without having to set up everything mentioned above first?
Unverified apps can still be used by the developer who created the project on google developer console.
Unverified app screen
The app or script might display an "unverified app" screen before it displays the consent screen. This is based on the specific scopes that your app includes in the request.
You can still work on your app while you are going though the verification process. However that being said i would start that process asap it can take a long time to get verified.
Yes, you can. As far as I am able to tell, all the verification step does is remove the "unverified app" screen. As long as you click Advanced > Go To ... (unsafe), you should be able to create and edit calendar events for that user in your application.
In order to be able to create and edit calendar events, you need to use the most sensitive scope, which is https://www.googleapis.com/auth/calendar. I couldn't figure out how to edit and create calendar events in my web app until I changed my scope from calendar.events to calendar.
Creating Events: https://developers.google.com/calendar/create-events
So here I am again, exploring new Google platform and hunting down information and docs.
I'm trying to build a skeleton of a flow before I write any business logic code with actual use of the APIs, and as expected from Google, this process is excruciatingly painful.
I've tried to follow this doc:
https://developers.google.com/gsuite/marketplace/listing
Packaged the zip, put the flag DOMAIN_INSTALLABLE flag as was instructed in order for the app to be installible from the marketplace. In the dashboard of PRICING & DISTRIBUTION I've selected Private and added testers to the list of testers.
Now when I click View in Chrome Web Store (seen in image) it takes me to the extensions web store, and not to the marketplace store.
How can I get to the GSuite Marketplace flow, rather than the extension flow? Do I need to alter my manifest.json in some way that is not mentioned in the docs?
Thanks
it's true that the publishing flow is too complicated now. We are working on improvements and in the future everything will be in one place.
Unfortunately G Suite Marketplace does not support trusted testers (yet), that's why it doesn't show up.
What you might be able to do, is modify the url a bit after you clicked on 'View in Chrome Web Store'.
Just remove everything after the webstore id
I use this url:
https://chrome.google.com/webstore/detail/xxxxxx
xxxx should be your webstore id
You should be able to show your unlisted app in the Gsuite Marketplace, where you can initiate the install flow.
It works for me, but my test app
I checked all the Yammer developer documentation, I cannot find anyway to add a new action inside Yammer, integrated with another Yammer APP similar to the recognize button action in Yammer for Recognize APP (check image below).
Please let me know from where to start if you have any idea.
According to the Recognize site, the addition of actions to the Yammer publisher is done through Recognize's browser extension and not through any Yammer platform API.
I am testing web application using Cucumber. There's certain link on the web page when clicked will trigger Microsoft Outlook to create an email to be sent to someone.
How do I switch from web browser to Outlook email window created from Outlook? Check the Subject? Check the To: (email recipient)? Close the email window, switch back to web browser and pass the Then test.
what sort of libraries and methods do I need to use?
This cannot be achieved with Selenium WebDriver/Capybara/Cucumber.
You can potentially use Outlook 365 (the online version of Outlook) to log in and automated your verification on the email. It's possible that you may run into captchas there though.
Personally I have emails delivered to a mailinator account. I check an inbox there to verify end-to-end email deliveries. This has worked for me. This allows for complete integration testing of frontend/backend/smtp components.
You can't do this with Capybara. I suggest checking the content of the mailto link.