The page used to give approval to a third pary app at https://www.yammer.com//dialog/oauth is called when using the Log In With Yammer button.
When viewed on an iPhone 4 screen the Approve and Deny buttons are off the bottom of the screen, and the page isn't scrollable, so you can never get to them.
Are we missing something, or is this process completely impossible in a browser of that resolution. Any workarounds ?
We have encountered the same issue on a recent project that uses Yammer as an oAuth provider and small screen heights can not click the approve button.
We have opted to use JavaScript client detection to send a custom browser message to these users, the custom message advises users to visit the page from their desktop on a one time only basis.
The next time they visit the page from their mobile device they will be authed and will be able to get past the next stage.
The lowest sized screen that could still auth on Yammer natively had a window.height of 460 hence the solution below to notify these users:
jQuery(document).ready(function () {
if (jQuery(window).height() < 460) {
jQuery('#wpoa-title').html("IMPORTANT: ");
}
});
Related
I have the MS team's custom tab application for the team's. It is an angular application, it has some internal navigations like navigating from one view to another. When I am sending a notification using the sendActivityNotification API call, it reaches to the mobile app. With the click of the notification, the application loads and it works fine.
But after navigation, if I tap on the back button of the device or (<-) button from the MS team's app header then it behaves like loading the history instead of navigating back to the activity(Feed).
Thanks,
Pratap
We have a published app in the Teams App Store.
Our app supports task module.
It worked just fine but about a month ago we started to receive reports from our costumers that when they are trying to open a task module, teams app just freezes.
This is how i understand task module requests work, in 4 steps:
1. User clicks on the button with data {"msteams": {"type": "task/fetch"}}`,
2. Teams sends request with this data to the bot.
3. Bot handles the data.
4. Bot replies with the appropriate url to render.
So we tested what happens when we click on the task/fetch button.
First of all we saw an error in the teams console:
TaskModuleLaunchService: launchTaskModuleByInvoke failed: "could not find app definition for app 00000000-0000-0000-0000-000000000000" where *00000000-0000-0000-0000-000000000000* is out appID.
And we don't receive any requests from the teams on the bot's side. So basically we have an issue on the step #1.
Unfortunately, we couldn't reproduce this on our devices, using the same card with the exact same button.
How can we fix this? Any help would be appreciated.
Thanks in advance.
We are getting this error Error: Uncaught (in promise): BrowserAuthError: user_cancelled: User cancelled the flow. BrowserAuthError: user_cancelled: User cancelled the flow.
This error occurs in the MSTeams desktop applications while it's working fine in the browser.
Following is the code snippet for the reference,
const silentRequest = {
scopes:['openid', 'profile'],
loginHint:'EMAIL_ADDRESS',
domainHint:'DOMAIN_HINT'
};
await this.msalService.loginPopup(silentRequest).toPromise();
We would really appreciate your help, thanks
It's not possible to launch a popup from within Teams - it's blocked for security reasons. Fortunately, there's a capability specifically built into Teams to handle authentication - it launches a popup -for you-, which them can implement a -redirect- flow within that popup. It's all part of the overall tab SSO capability, and works well when you follow the guidance - see here for an excellent starting point, released just a few weeks ago: https://www.youtube.com/watch?v=kruUnaZgQaY
Here's a blog form of the video: https://devblogs.microsoft.com/microsoft365dev/lets-decode-single-sign-on-sso-in-microsoft-teams-tabs/
Another hair-pulling exercise. I am generating a link in a text message and when the user clicks on it then it would call the page, and take some action. Simple! But in the stock Android messages app (and perhaps others) it would appear that as soon as the message comes in it opens the link (effectively clicks on it like a user would = does a preview fetch?) even before there is an alert to the user. When the user then clicks on the link it is called a second time but that fails because the first call set a flag in a DB that the second call trips over. Is there some mechanism to programmatically thwart previews? Or detect that it is a preview?
In our botframework chatbot application we have URLs ( buttons - OpenURL) which will redirect to website / mobile apps links. How we will be able to get the statistics or number of hits happened to a particular website URL.
Thank you
AMR
This is not possible in the bot. The "OpenUrl" protocol tells the channel to just open the link on the button. This doesn't trigger a message so the bot will not know that the button was clicked.
The only solution I can think of is creating a special url which will first log the action and then redirect the user to the requested webpage. But this solution requires you to setup your own website or api.