I was working on a Teams Meeting App and as using a Teams Web web client to validate the changes when I found that the sidePanel functionality did not show up at all,
Also not in ring 3.6/preview
After opening up in the full client this started working straight away.
The documentation only mentions missing functionality on mobile, and limits for anon/guest users,
but no mention regarding missing functions on the web client.
relevant section from the app manifest:
"configurableTabs": [
{
"configurationUrl": "https://somewhere.ngrok.io/meeting/config.html",
"canUpdateConfiguration": true,
"scopes": [
"groupchat"
],
"context": [
"privateChatTab",
"meetingChatTab",
"meetingDetailsTab",
"meetingSidePanel"
]
}
],
"permissions": [
"identity",
"messageTeamMembers"
],
Unfortunately no, the in-meeting app experience is currently (18.11.2020) not available in Teams Web client, only in the native app.
Related
I created a bot which I integrated with MS Teams channel. The layout view as shown in the WebChat window and emulator is perfect which is exactly what I need but when I deployed my bot with MS Teams, the view looks messed up and very cluttered. Any advice how to fix this?
MS Teams view layout
Azure portal Webchat console view
Please excuse my shortcomings as I am a new user to Stackoverflow and don't know how to address questions but if there are any suggestions for this issue, those would be greatly appreciated. Thanks.
I would recommend using markdown in an Adaptive Card.
Bot Framework SDK v4 (Node)
await context.sendActivity({ attachments: [CardFactory.adaptiveCard({
"type": "AdaptiveCard",
"version": "1.0",
"body": [
{
"type": "TextBlock",
"text": "Top Options: \nOption 1: [https://microsoft.com](https://microsoft.com) \nOption 2: [https://microsoft.com](https://microsoft.com) \nOptions 3: [https://microsoft.com](https://microsoft.com)"
}
],
"$schema": "http://adaptivecards.io/schemas/adaptive-card.json"
})] });
Teams Screenshot
Web Chat Screenshot
Note, rendering behaviors do differ across different platforms.
Hope this helps!
I followed this document Add tabs to Microsoft Teams apps to add a static tab in personal scope for my Ms teams app which is nothing but a chatbot built based on botbuilder nodejs sdk. Here is how entry from manifest.json file looks
"staticTabs": [
{
"entityId": "spotify_g",
"name": "Show Spotify home page",
"contentUrl": "https://www.spotify.com/us/",
"websiteUrl": "https://www.spotify.com/us/",
"scopes": [
"personal"
]
}
]
I am just trying show spotify home page for fun to try out this functionality so later I can embed my website's home page. But, for some reason I don't see anything when Tab is clicked on the installed Bot. Looks like its not rendering in an . Any thoughts ?
Screen Shot can be found herew where is shows nothing is rendering on the tab.
Spotify doesn't allow themselves to be iframed by Teams. Here are console logs:
Try putting this URL for testing: https://www.bing.com/maps/embed
Best way to debug tabs would be by opening Microsoft Teams in web client and looking at console logs. Please have a look at documentation on how do tabs in Teams differ from a browser viewing the same content URL.
My team has recently started using review apps. However, before tests can be run on a review app, we need to manually change the configuration of an addon. This manual step breaks our test workflow. Is there any way to transfer addon configuration to a review app?
Heroku allows you to specify addons for review apps in your app.json like so:
{
…
"addons": [
{
"plan": "heroku-postgresql",
"as": "BACKUP_DATABASE",
"options": {
"version": "9.5"
}
}
]
}
Note that according to the docs, review apps are provisioned with the default "ephemeral" plan from the provider. Also, not all apps support review/CI apps.
If one of your addons does not support review apps, you should see an error message similar to <add-on service slug> has opted out of supporting Review and CI apps when the review app attempts to deploy.
i have to implement single use application for my Enterprise's devices where there is only one major android app that itself can use 2-3 other apps like call, sms and google maps, other than that user must not be able to use or access other apps and settings,
1) I have considered Corporate owned Single use through Enterprise Management Api which is more sophisticated and big, but more complete solution.
2) I have implemented and tested the sample
Lock task with an android device owner app
that looks more like being my solution, but there is a problem
How do i provision device owner for production level devices? for my test i was able to provision with adb shell commmand. i know that device must be new/Reset and unprovisioned thats not a problem.
I am seeking some suggestion here, if anybody has implemented it it could help.
Update
going with the android management Api QuickStartGuide, suggested by Fred seems like correct way.
where my policy is Multiple app from custom launcher
now i am stuck in a situation, i want to publish my launcher app or other app to play store only for my enterprise.
I have followed Upload your own app to the Google Play Store,which led me to publish private app, but i am not able to do so as i am not getting Restrict Distribution option.
I don't know how to perfectly achieve this.
for my current policy and enterprise, i have 2 active email ids,
first email_1 is the one which is connected to the initial project
and
all the google api call is done under email_1 .
and the other is email_2 the one is admin for the enterprise
and connected to managed Google Play Store.
both email_1 and email_2 has admin access to my company developer account
.
Now i need to figure out to publish app only for my enterprise, i think there is a issue with correct permission or otherwise,
need Help.
Thanks
It's easy, once you understand the missing links.
The documentation should definitely clarify these steps.
1 Setup the accounts
We created a Google Suite Account for our client and uploaded his app in the Google Play Console account created using a Google Account under their organization, and limited the app distribution to their organization.
We also added Android for Work to our organization here: https://admin.google.com/AdminHome?pli=1&fral=1#SelectServices
And added a role to our organization to manage Google Play Private Uploads:
https://admin.google.com/AdminHome#DomainSettings/notab=1&role=new-role&subtab=roles
2 Find the organization ID
This is the key part. You should find your organization ID here: https://play.google.com/work/adminsettings
3 Enroll the organization
When following the steps for the Android Management API, you need to enroll the organization ID found in your Google For Work account.
Follow the step detailed here using your enterpriseID:
enterprises/{enterpriseId}/enrollmentTokens/{enrollmentTokenId}
4 Add your app
Add your app using its PackageName in a ApplicationPolicy. Your devices will now be able to find it and install it.
You no longer need to implement a Device Policy Controller to manage Android devices, Google has recently released the Android Management API which allows you to set up a COSU device with just a few Cloud API calls.
If you have one main app and want to allow to open a few other apps, you can set the main app as a custom launcher and mark the other apps as lockTaskAllowed. You can simply do so by defining an ApplicationPolicy such as the one below (copied from Create a policy):
"applications": [
{
"packageName": "com.example.custom_launcher",
"installType": "FORCE_INSTALLED",
"lockTaskAllowed": true,
"defaultPermissionPolicy": "GRANT",
},
{
"packageName": "com.example.app1",
"installType": "FORCE_INSTALLED",
"lockTaskAllowed": true,
"defaultPermissionPolicy": "GRANT",
}
],
"persistentPreferredActivities": [
{
"receiverActivity": "com.example.custom_launcher",
"actions": [
"android.intent.action.MAIN"
],
"categories": [
"android.intent.category.HOME",
"android.intent.category.DEFAULT"
]
}
]
Google provides a good feature list here:
https://developers.google.com/android/work/requirements/features
If your devices have NFC, I would provision using NFC. You can look at the code here for your own implementation or you might be able to use the app with very few modifications.
https://github.com/googlesamples/android-NfcProvisioning
By tapping the welcome screen in the Google Setup Wizard 6 times will allow you to use QR code provisioning. It is a bit more cumbersome in my opinion and requires Android 7.0+.
Those are your only two options unless you become a Google EMM Partner or again, partner with them to support Zero Touch Enrollment on Android 8.0+ devices for your own homebaked solution.
You might want to also look at existing open source EMM/MDM implementations that already exist such as WSO2.
I am trying to create post on Google Plus using API. I am using http protocol for create post as below.
URL : https://www.googleapis.com/plusDomains/v1/people/me/activities
Method : POST
header parameter :
Content-Type :application/json
Authorization : "browser key"
I am using below json as Request Body:
{
"object": {
"originalContent": "Happy Monday! #caseofthemondays",
},
"access": {
"items": [{
"type": "domain"
}],
"domainRestricted": true
}
}
Now 1 got response:
Status : 401 Unauthorized
{
"error": {
"errors": [
{
"domain": "global", "reason": "authError",
"message": "Invalid Credentials", "locationType": "header",
"location": "Authorization"
}
],
"code": 401, "message": "Invalid Credentials"
}
}
I am using correct key and also enable Google Plus API and Google domain api enable. Can anyone help me how can I create post using Google Plus API. I am trying create new post on Google Plus using HTTP protocol.
I think you are conufusing Google+ Domains and Google+ the social media platform.
Develop business apps that integrate with Google+
Develop business apps that integrate with Google+ With the Google+
Domains API, Google Apps customers and ISVs can build custom
Google+ functionality and services for people who use Google Apps at
college, at work, or at home. Organizations can develop tools to
interact with Google+ features such as posts, comments, and circles.
These tools let your users share information, reinforce
communications, and grow productivity within your organization.
Getting Started with the Google+ Domains API
The Google+ Domains API offers a number of additional features
compared to the Google+ API v1: Write posts to the stream restricted to the domain.
This is google apps domain
This is Google plus
They are two different systems, with two different APIs. The Google+ website has the Google+ API which allows read only access to view things. It does not allow you to post to a users stream.
The Google APPs are used mostly by companies and has the Google+ Domain API which allows you to post messages to other members of the domain. This is not public no one besides the other members of the domain will see it.
You will need to play for a Google domain account for you company if you want to use it. it is not free