We have set up our application as a custom Microsoft Teams app. The application is working just fine in the browser but fails to load in the Desktop APP. The application uses Azure Active Directory to perform the login through the saml2.0 implementation and is embedded through an iFrame.
Can't find a good way to debug what the issue might be. The AAD logs are always empty and the DevTools do not show what's happening in the embedded iFrame.
Has anyone encountered this issue before or might know of a way to try and debug it?
This is actually quite common, that it works fine in browser but not in desktop, and there are probably several reasons for that, not least of which that the popup experience is easier to control in browser versus the actual Teams desktop sandbox. It's also common, I think, that people try to launch their own popup to handle the login, which you can't actually do in the Teams desktop. It's a bit wierd, but basically Teams desktop launches a popup for you, which loads your login page, which in turn then needs to do a -redirect- because you're now in a new browser page.
In any case, in my experience, it's always because I've done something wrong, that's why desktop doesn't work correctly. My suggestion is to follow the docs -exactly- and it should work fine.
The most important doc is this one, which really does give some quite straightforward step-by-step. You can also check out this video which helps as well.
Related
When loaded a PWA (Progressive Web App) inside a iframe, it will work normal (saving Web Workers, offline availability, etc) or some features will be blocked?
I have a PWA that uses an iframe. It uses some pretty advanced features, including a web-worker (in addition to the service worker) that I implemented long before recently porting it over to a PWA. All of those features work the same, with the additional benefit of controlled caching of specified resources. I haven't seen anything in the documentation to suggest otherwise, and can honestly say it works amazing! So fast to load now, it's in the app drawer, etc., even installs and looks like a normal app on desktop. My only issue is the soft-keyboard overlaps in fullscreen, but there is a solution, I've seen it work.
My suggestion-- try it. It's pretty easy to set up. Test your features. I am sure you will be impressed.
We need to build a WAP interface for our web application, something like the m.domain.com, i.e wap.domain.com. i am a web developer and i need a quick and dirty tutorial or guide that would get me started immediately. My searches haven't produced much, i mean i have found a few tutorials but none of them was much helpful. Can someone please point me to the right direction? what i am essentially trying to do is integrate it into the same application, which is a Spring mvc web app, and use the same domain objects to send the data to the WML pages. i am not even sure if that is entirely possible.
Developer's Home may help you. Its link is : http://www.developershome.com/wap/wml/wmlIntro.asp
I also had to make a WAP application these days, and this website helped me a lot.
To display your webpage onto a mobile with low res/ or using wap you need to check the version of the browser and os reaching to your device.
That can be done via js. Once you have identified that the page to be displayed if for low res devices, you can create a web header that redirects to your subdomain # m.yourdomain.com.
In your subdomain you will use different css files and low resolution images destined towards displaying on old browsers like symbian OS .etc. "
I had the same issue. There is a team at '999Studios' who had made this tool to automate the process of making your WAP based services. You can contact them info#999Studios.com. They gave me a free version of the tool. Worked like a charm.
Is there a way to perform basic authentication using StageWebView on mobile devices in Flex?
The problem is that mobile (iOS, Android) implementations don't provide authentication dialog and documentation about this is pretty unclear.
On this link:
http://helpx.adobe.com/air/kb/stagewebview-differences-platforms-air-sdk.html
it's suggested to use URLRequest as a workaround, but I already have URLLoader that successfully authenticates and loads data from the same service and it doesn't affect StageWebView.
I'm having the same issue. The problem is after authentication (after the app install page through facebook), it goes blank. I at least found that the url is "m.facebook.com/dialog/permissions.request" and then continues with a massive amount of get variables.
From my research, I believe this is a pop-up window that runs an auto-close function but doesn't seem to work in Adobe AIR. I've tried running a TimerEvent in a "LocationChangeEvent" to nav back (have to run 2 back to back because the webViewObject.historyBack() method does not support parameters), and this works but only after the app has been installed on their facebook account successfully which in turn affects the ability to even install it to their Facebook in the first place.
I also tested reading the url to trigger callbacks but the one major problem is the "Install" page and the "login successful" page have the EXACT same url entirely, at least from start to finish. Haven't tested the title yet due to my frustrations lol...working on that.
If anyone has any suggestions, this would be supremely helpful and seriously appreciated!
I am working on an ASP.Net application and I want users to be able to take a picture with their local webcam and then upload it to the server.
I can, of course, rely on users doing this manually via their locally installed software, save the image as a file and do a normal file upload. However, what I really want to do is incorporate it all into a UI in the browser.
I know this means accessing local resources so do I need an ActiveX control or Silverlight or is there something I could do in Javascript for example?
This is initially intended for an Intranet app so I can have control of the client's environemnt, including stipulating the browser etc, which means I can use an ActiveX control if I have to. However, it would be nice if I could write this in a generic way so it could be used in an internet app generally (happy to stipulate that it only works on Windows clients but would be good to get it to work in FireFox).
Thanks.
The only acceptable and universal way to this for now is Flash/Flex application. Flash player presets literally in every browser in the world and all of them has such capability.
VideoCap Pro is quite popular, and it offers an ActiveX version, have you checked it out?
This sounds very suspicious to me. You realize the nefarious applications this could be applied to, right? A web page that when a user browses to it, unknownst to them, their webcam snaps a pic of them. ... I don't like it.
You could use the Nimbb API to do the webcam video recording inside a browser.
It is possible to get the image from client webcam in asp.net, you have to install the Silverlight 4 with Visual Studio 2010:
Go to following link:
http://wildermuth.com/2009/11/23/Taking_a_WebCam_Photo_with_Silverlight
I've included a mobile web form in my asp.net project, I thought that it could/should be seen just for my mobile users but I realize that it can also be seen from any browser, I don't see problem there cause I could diff the access using HttpBrowserCapabilities.IsMobileDevice=true and transferring to the appropiate aspx page, but it results that when I access to the web form from my mobile device it is identified as IsMobileDevice = false and sends me to another page.
How could it be possible that?
The mobile device runs Pocket PC 2003.
IMHO: The value of HttpContext.Current.Request.Headers("User-Agent") is a much safer bet as it actually indicates the browser that is making the request, and not the type of device per-se.
I've learnt from experience that if a smart phone makes a request through a third-party browser to your service, more-often-than-not any sort of "what type of device are you" test (HttpCapabilitiesBase.IsMobileDevice and/or HttpContext.Current.Request.Browser.IsMobileDevice) will fail.
Unfortunately though, short of a big list of allowed user-agents (or disallowed user-agents for that matter), you'll just have to make sure it doesn't start with Mozilla, iPhone or Opera before you render the page...
It's a hard arena to play in.
Good luck.
Some are not recognized, because the UserAgent has been messed with or a new browser is being used. Such as Opera Mobile 9.5. To fix this you need to create a Browser (*.browser) file specifically for defining this. I had to do it for the new Mozilla based UserAgent that is being sent from Google.
I think you should use other DDR better than Microsoft Browser Capabilities. I´m using http://wurfl.sourceforge.net>WURFL, it is open source and maybe it is more extended and updated. There is other commercial DDRs like DeviceAtlas.
There is many some .net libraries but i´m using Marg.Wurfl. It allows to rendering web mobile page using wurfl capabilities.