I have deep links configured on iOS and Android using universal links. They're working fine. If the app isn't installed, the request goes through the web site, which I currently have an apache Rewrite redirecting them to the home page of the web site with links to install the app.
Emails that go through Outlook safe links protection, a feature of Office 365 subscriptions, rewrites all URLs in your received emails. So my deep link universal link is rewritten to an outlook handling URL (na01.safelinks.protection.outlook.com), so iOS nor Android have the chance to handle it immediately. This redirects to the original url, however Safari then doesn't treat is as a universal link, at least not in the way I have it configured and the user then gets redirected to the home page, and the app never opens. 😢
I can't be the only one facing this issue, as there are a lot of hotmail users out there.
Anyone got any suggestions on how to alleviate this issue and make universal links work with outlook safe links protection?
Note that this issue only is affecting iOS 13 and Android. It works ok on iOS 14.
I know it's possible, as we've got emails from other apps that seem to be successfully doing it, albeit via a lot of link forwarding it seems.
Related
I have developed a very basic Outlook Web Add In, with the purpose of loading a Power Apps app by using an iframe object with a URL pointing to the app, all this from Office 365 on desktop devices.
It works as intended and, when loading, Power Apps asks the user to login first, this isn't the app itself asking to login, but Power Apps asking the user to identify first and then loading the app. This also works, at least on some devices.
It has come to my attention that some users can't make it past the login request, as instead of opening a browser tab and showing the login form, the iframe in the Add In, shows this message, which, obviously, makes users think the app isn't working:
This app isn't working. Refresh your browser or try again later
Apparently this message is not that uncommon and at least from what I've read it isn't clear enough either.
Besides that, Windows is displaying this message:
You'll need a new app to open this about link
I'm not even sure what it means, but it shows a list with zero apps that can open this "about link", and the option to go the Windows Store.
What should happen (and happens on some devices):
User is shown login request (by Power Apps)
User logs in
App is loaded and shown to the user
What happens (only on some devices):
User is shown login request (by Power Apps)
Windows can't open a web browser, so the user can't log in
Message saying app isn't working appears, because app was never loaded.
As I don't quite understand why this only happens on some cases, I have been testing the issue, and I have found that when the Power Apps login button is clicked, a file called ielowutil.exe, which apparently stands for Internet Low MIC Utility Tool, is executed before the web browser is shown with the login screen, and this only happens on the devices that can eventually load the app, the ones that fail never run this program.
From what I understand this file is related to Internet Explorer.
The Outlook Web Add In is already working within a web browser, according to Microsoft the browser is chosen automatically (Browsers used by Office Add-ins), so if it's already opened then I don't quite understand why it can't open a new tab/window.
The combination of system requirements for Office Add-ins and Power Apps may be the cause of the error here. While some combinations of platforms and Office versions still support IE 11 for add-ins and may default to opening URLs in IE per Browsers used by Office Add-ins and Support Internet Explorer 11, it looks like IE is no longer supported by Power Apps (see Supported browsers for running Power Apps).
For users who experience the issue you mentioned because of IE, you may need to add an alternate experience for the add-in to gracefully fail (see Determine at runtime if the add-in is running in Internet Explorer) or consider a different solution for hosting the Power Apps app.
I have a simple webapp that I am showing as an app in Teams. I have set it up in App Studio and everything works as I expect and it's all great. It is showing my web app and that is what I want.
For some cases, I need to redirect to a different web app on a different domain. When testing from Microsoft Teams in my browser, it works fine. But when I test from Microsoft Teams in the desktop app, then the screen just turns grey when the redirect was supposed to happen.
I already added the domains to this dialog in Manifest Editor.
Because the screen just goes grey with no explanation, I am having a hard time troubleshooting this issue.
#NielsBrinch Could you please take a look at Redirect across domains in a Microsoft Teams tab? Also please make sure that the tab you want to redirect to, is iframable and that it meets all the Requirements for tab.
I'm working on an Outlook addin using the new Office-JS apis, and in building out the authentication flow, I've found that in the Outlook 2016 for Mac case, the dialog system seems to not work properly.
To be clear, we're using the Office Insider Fast Track build as it has much improved support for the Office-JS API.
I've been through several iterations of this particular piece (most of which worked fine both in the Windows client and the web client on Mac and Win), and have had no luck. The scenario is:
List item
Open up the task pane in outlook.
Hit the sign in button
A new window opens, pointed at our authentication portal
User signs in.
On auth completion, the window redirects to a page in the office add-in scope, and calls back to the parent frame with the auth token, where it can be further processed.
Steps 1 through 5 work fine on all platforms. Step 6 refuses to work on Outlook for Mac. Initially, this flow was built using the native js window.open and window.postMessage apis. As mentioned above, this worked everywhere but Outlook Mac, where, the API seemed to ignore the window options and just open the url in a new tab in whatever browser was open and never setting the child window reference (result of window.open being null).
Failing this, I followed the advice found here on SO to use the Office functionality, displayDialogAsync and messageParent. After some initial hurdles, this too was setup and working on every platform save Outlook Mac.
As there is no dev tools or JS console support in Mac Outlook, I followed the advice found here Howto: Outlook 2016 for Mac - Debugging/View Console Logs in Outlook Add-in and setup Vorlon to attempt to get some context, adding numerous logging points to try and get some context. Unfortunately, while Vorlon does pick up my auth landing page as a client, and sees the Office interfaces, none of my console outputs are presented, making it seem as though the JS isn't running at all.
At this point I'm not sure what to try next. Has anyone run into this issue, or gotten this to work on the Outlook 2016 for Mac client?
Clarifying context:
All auth pages are listed in the AppDomains section of the Manifest.
While initial versions pointed directly at our auth service (this worked on not Mac), the current version first opens up an in scope pre-auth page that redirects to the auth service.
The Office-JS api's block alerts, preventing their use in displaying useful information.
Authentication through all versions of this app have worked on both Outlook 2016 on Windows and OWA on both Win and Mac.
Thank you.
This issue in Outlook Mac has been fixed a few months ago. If anyone still encounters this issue with a recent Outlook Mac build, please reply with the build number.
The Office.context.ui is undefined in v16.17 (180909) build of Outlook for Mac 2016 using the following OfficeJS dist:
https://appsforoffice.microsoft.com/lib/1/hosted/office.js
Can't solve a problem that I have regarding windows phone jquery mobile https and asp.net mvc 2. I have a asp.net mvc 2 app that resides on my localhost. Some pages require https connection, so when I use my windows phone to browse through pages everything is fine (jquery mobile renders fine) until I accept the https message and go to the https page then it showes all html content with no javascript and css (white background with black text, jquery mobile not working, hidden divs now visible and so on). Seems like windows phone is blocking the files on https in this particular scenatio. Quite strange problem, especially that everything works on Iphone. Iphone renders everything just fine whether its http or https.
I'm not gonna try to paste any code since I don't event know where to start, and the app is too large to paste code snippets. Just wanted to know if anyone had similar problem, or has any idea how to overcome this issue.
Thanks.
EDIT: by searching through forums I stumbled upon problem of self signed certificate on the server and accesing pages with windows phone, dont know if this is the exact problem tho
I think I found solution to my problem, as I thought I need to add the same self signed certificate to my phone that I generated on the server. It is not necessary on the iphone, but for some reason Windows Phone requiers it.
When installing a Google Marketplace App, the flow usually ends with the admin in the app's settings on Google with the option to sign in now. Is there a way to end with the user actually using the app (i.e. not having to click the link to sign in to start using the app)? Could the user just be sent to the app on the optional setup without returning to the app settings page on Google without that causing other problems?
Some of the documentation says:
We strongly recommend that the administrator be directed through a short, linear series of actions and returned to Google quickly so additional users can start using the application.
I tried testing this out, but it seems like there's some lag between installing and the app showing up in the "more" drop down for Google (I tried installing another app and did end up on the final page but the app still didn't show up in another account. It's been a few hours and it still isn't there) so it's hard to tell if it's just slow or not actually installed on other users' accounts.
Sorry the last section was misleading. This is not a question about the link not showing up immediately.
The new experience for Google Apps Marketplace lets you land the user in the app instead of the admin console. There's now a popup for the app to request permissions and to agree to terms and then the user ends up in the app. One-step installation. Good work Google.