I'm trying to debug one of the tutorial apps with MS Teams Toolkit for VS Code on a Mac.
When I press F5, it opens a new Chrome window and loads Teams, this message appears:
App not found, Please verify the app and it's access permissions.
For more information, please visit aka.ms/teamsdocs
I followed the instruction to open my app (https://localhost:3000/tab) and allow the insecure connection, but it made no difference.
Also tried manually uploading the app through Teams -- it shows as installed but debugging still doesn't work.
The app works if I upload it through Teams as a custom app, just debugging does not.
Versions:
VSCode 1.53.1
Toolkit 1.1.8
Teams for Mac 1.3.00.33671
Any ideas?
If you're unable to see the side load option in the Apps menu, you may need to create a Teams account through the Microsoft 365 developer program, which you can find the steps to do so on the Teams Microsoft Docs.
If you are able to side load apps, then you may need to configure permissions to allow your account to debug local apps. Go to admin Teams panel and choose Teams apps > Setup policies (or visit this shortcut). Click on Global and tick "Upload custom apps" to allow all users to upload local Teams apps. Remember to hit save!
If you want to specify which users can upload custom Teams apps, create a new policy that allows uploading custom apps, select said policy from the policies list, choose Manage users, and select the user you want to assign the policy to.
Related
I just can't find app licence API Key in the new Google Play Console. In the help, it says you select your app then click on Development Tools and click on Services & API link. However there is no Development Tools or Services & API links in the new Play Console. Please someone show me where is it?
I need it to activate Unity IAP Services.
Many thanks
In Play Console, select your app.
Then navigate to Monetize on the left bar.
Under this, you will find Monetization Setup.
Your license key will be there.
We are developing a google smart home action. As per this and this guides we added testers as viewer and shared action and it worked few months ago. Now we don't see this share button in our simulator anymore. Wonder how to share with testers anymore? As guides still wants us to share the project through this button.
Screenshot from documentations:
Screenshot of my simulator:
We are able to add the tester in IAM project, but tester is unable to see the action like owner does ([test] ABC agent) in google assistant app.
Edit 1:
It doesn't work even sharing an action with owner rights. Second user is unable to see that action in Home Control under google assistant app
As per discussion with 'Actions on Google Support Team' they say that "There has been a slight modification on the interface in the simulator page. Unfortunately, the current documentation hasn't been updated yet to reflect this change."
You can still share your Action without the share button. To recap:
Go to the Actions console and select your project.
In the right navigation menu, select the three dot icon and then Manage User Access.
This redirects you to the IAM page for your project.
Click ADD to set a team member's access to your project. You must be an owner of the project.
Type the member's email address in the Members box. To assign view access, from the Roles menu, select Project and then Viewer. The members you add will be able to see the Action on their console. Please note that the system does not proactively notify the added members.
Tester/Viewer will have to login in to console and Enable testing in simulator to see the action in Google Assistant App.
Happy Coding !
Its been three weeks my app (GSuite spreadsheet add-on) is in "Pending Review" state after unpublishing it through chrome web store developer dashboard.
I also don't know why it is visible in marketplace as well when I already requested Google for unpublishing this item.
Query: Its already three weeks gone, any idea how much max time Google takes to unpublish an GSuite marketplace app from Chrome web store developer dashboard?
Here is a related SO post about the unpublished apps in web store.
See this full answer from the post:
if app is unpublished then is will not be available for download, will
not appear in in-store search results, and simply cannot be installed
from store. No details information from Google Play can be received
even with direct URL to the application. Unpublishing however does not
affect existing installations (so apps will not be automatically
removed from any device that got it installed already). Also existing
users still would be able to update if they are on older version.
And you cannot have another application with the same package name, no
matter what.
EDIT
Please note that you unpublish (and this means just what name says,
nothing more) not just APK - you hide all related stuff (app's page in
Google Play etc). To end user it looks like the app is gone. For you -
it is still in your console, you can edit description, images, see
comments, stats or update APKs etc., but unless you publish it again,
nobody will see these changes.
I have added community applications to our Dashboard by clicking on Add Apps(home page), and assigned to the people. its working fine, people able to access Community Software, but whenever we are intended to create our custom app(Jive demo sandbox) from admin panel and assigned people its not working as expected. even the admin not able to access the app it is showing message "Sorry, you can't access Jive Software because you are not assigned this app in Okta".
i have followed the integration process from
http://developer.okta.com/use_cases/integrate_with_okta/
please help me that i am missing any integrations or configurations
There is not sufficient information in this question to be able to answer. Have you tried reaching out to Okta Support? They should be able to check your configuration with your permission and help you with it.
I work a lot with AppsScript within my workplace. I've built lots of custom OAuth2.0 flows within AppsScript, that allow the application to call Google's REST APIs, and I've also worked with enabling the 'built in' API interaction objects (GmailApp, CalendarApp, etc). If you enable any of the built in APIs, the script editor adds the relevant scopes to the project information, and then asks the user for permission to interact with these APIs, when the web app first loads.
If I need to interact with both REST APIs and the few built in API calling objects, the user needs to first grant permission to the built in API scopes, then has to follow a separate OAuth flow, for the REST APIs. This makes for a really ugly user experience.
Is there a way to add REST API scopes to the list of scopes within the project information, so that when the user first loads the app, it asks them to grant permission for ALL scopes that the project will need? I could then retrieve the users oauth token from the script session with ScriptApp.getOAuthToken(), and use that in all external REST API calls.
EDIT (~12:00:05 18/DEC/15):
Please note, I already know how to enable APIs through the Developer Console Project that's linked to the AppsScript project - I want to find a way to add ALL APIs that are enabled to the Scripts properties, so that when the user launches the app, it asks them to grant permission to access all enabled APIs on their behalf (even REST apis), so that I don't need a second manual OAuth flow / token for the REST APIs.
EDIT (~14:00:08 18/DEC/15):
I've also looked into the Import/Export functionality within Drive, documented here:
https://developers.google.com/apps-script/import-export
and can't find any way to alter the scopes (or supply any scopes) for the project, this way.
In apps script you can enable specific API if you go to the menu "Resources > Advanced Google Services". It will open a Popup with a list of API, but there you also have the option to go to the Developer Console with the project associated with your Apps Script project.
And from there you can get the necessary information (clientId, etc.) related to the same Apps Script project and use it in you OAuth flow.
If you already have a project with all the required configurations and all the necessary API already enabled, you can also link your current Apps Script project to that app, so you don't have to do the same again.
In the menu "Resources > Developer Console Project", a popup will open and there you will have the option to access the Developer Console, but also you will have the option to associate the current Apps Script project to any other app you already have.
Just keep in mind that when you are trying to use an API you will have to enable it in the "Advanced Google Services", both in the list that the popup shows as well as in the Developer Console.
After doing this, the access tokens will be related to the same app and the users will grant permissions only one time when enabling a new API.
I hope this helps.