I am trying to debug task pane app on a Mac. Already tried https://dev.office.com/docs/add-ins/testing/debug-office-add-ins-on-ipad-and-mac. I can see it detects browser instances but it CANNOT detect task pane app.
I followed all steps properly. Except, that I don't have "Staff" user group on my mac. Should that make difference?
How do I detect/debug office task pane app on a mac?
I used chrome before that allowed me to access vorlon by choosing option to navigate to untrusted https website. So I never got to go on step 13 in the documentation. This time I used safari and then I had to trusted certificate and then after it worked like charm.
Related
Currently I am developing my custom add-in for outlook 365/
Then I am trying to use it for testing for example it shows me error. I investigated and found what it opens addon in iframe in edge browser. So question is how to add certificate/s to edge to allow my app to work in it?
I am using :
Outlook 365 desktop edition
What I tried
Switching flag in Edge browser to allow not certified certificates to "work"(same thing was done in chrome and it worked there)
As suggested in comments to use office-addin-dev-certs. Well I installed them on my project by using npm install office-addin-dev-certs and then I am trying to verify it by this command office-addin-dev-certs verify it throws error in console see image 3
exported certificates from chrome and imported them in edge browser and also on my machine . It did not helped.
The easy solution that worked for me was remove .office-addin-dev-cer from User folder. Then by running my Add-Ins by npm start I got popped by a message box to remove existing certificates (ca.crt, localhost.crt). After clicking on Yes for 3 messages I have been asked to install new certificates and all certificates re-installed and my Add-Ins works fine now.
While not strictly required in all add-in scenarios, using an HTTPS endpoint for your add-in is strongly recommended. Add-ins that are not SSL-secured (HTTPS) generate unsecure content warnings and errors during use. If you plan to run your add-in in Office on the web or publish your add-in to AppSource, it must be SSL-secured. If your add-in accesses external data and services, it should be SSL-secured to protect data in transit. Self-signed certificates can be used for development and testing, so long as the certificate is trusted on the local machine.
See Server requirements for more information.
This may be an old issue which has resurfaced. You can see more info here
Well I found the solution. solution was to create and add certificate to app. In desktop outlook aka office outlook for desktop it uses Edge browser as sidebar for Add-ins.
Reason is what browsers need Subject Alternative Name in certificate.
So need to create a trusted self-signed SSL cert for localhost (for use with Express/Node) . So the solution was found in this post.
I'm currently learning Teams development and I just installed the Teams Toolkit extension. Following the quickstart guide, launching the app opens my browser with the Teams web app and the message
App not found, Please verify the app and it's[sic] access
permissions.
Fortunately, this app can still be launched when selecting the "Preview in Teams" option in the Developer Portal.
Quoting the GettingStarted.txt:
If you Start Debugging in a browser and Teams shows the message "App not found, Please verify the app and it's access permissions", it means the app hasn't been uploaded to Teams Dev Portal. To resolve this, follow the steps in the Quick start section above. The Project > TeamsFx > Configure for SSO menu command will do this step for you.
Except it was successfully uploaded to Dev Portal.
What I did
Did this "Configure for SSO" thing. No problems with that and the app was successfully added to the Developer Portal.
Where I searched for an answer
VS Marketplace page for Teams Toolkit (Reviews, Q&A)
Github page (issues) for Teams Toolkit
This very site - Stack Overflow.
Obviously, I'm not 100% sure that I haven't missed anything.
Temporary solution
In the meantime, I set the "launchBrowser" property to "false" in launchSettings.json. However, it's a waste of time to constantly go back to the Developer Portal to launch it, especially when the functionality is there.
Visual Studio 2019, Microsoft Development Account.
Thanks in advance.
We tried to repro this issue at our end and it is working fine for us. Could you please make sure app is opened in same tenant with which you configured for SSO. Also please remove all credentials from cache to make sure its not taking another credentials and try again.
Assuming nothing else was changed from the new project template, there are a few things you can try to narrow down the issue.
Open your browsers web dev tools and watch the console after clicking the Add button (before you see the error message). Sometimes a useful error message from the developer portal helps identify the issue.
Verify that when Visual Studio launches the URL, the correct tenant is loaded in Teams.
Run the project in VS, then manually navigate in your browser to the endpoint of your tab that you expect to work. It would be something like https://localhost:44357/tab by default (the value is in the manifest.json). The sample won't work completely because it's not running inside Teams, but you should be able to verify it's working locally.
If none of that helps, please log an issue on the GitHub page and we can investigate a bug.
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
It is possible to distribute a packaged app via Firefox Marketplace for installation on Firefox for Desktop. Apps for Firefox OS devices I can test comfortably via about:app-manager either on a USB connected device, or with the simulator.
How can I test a packaged app on Firefox for Desktop?
Update
I found that I can debug an app that I have installed from Marketplace by starting it with the -debug option and an optional port number:
C:\Users\Felix\AppData\Roaming\thetacontrol-56cab87ea3eecf190668cfb505f92c56>"Theta Control.exe" -debug 6000
The next step is to connect to the port from Firefox developer tools:
Still I don't know how to debug an app that is not (yet) on Marketplace.
Didn't found the way to debug privileged app either, so I've created bug on bugzilla, vote, please to solve this issue faster: https://bugzilla.mozilla.org/show_bug.cgi?id=1038533
You can refer to debugging guideline of web apps for Friefox desktop.
To access the console (and other remote developer tools), start the
app from a command line with the -debug flag and optionally
specifying a port (default: 6000). For example, on a Mac the Mykzilla
test app is started with:
/Applications/Mykzilla.app/Contents/MacOS/webapprt -debug 6000
Then, in Firefox, on the Developer Tools menu click Connect… and
connect to the “localhost” host at the port you specified. After
clicking Connect in Firefox, go back to your app and confirm the
connection. Then return to Firefox and select a “tab” (i.e. an open
window in your app) or “Main Process” to debug the Web Runtime’s
chrome code.
Then a copy of Firefox’s Remote Developer Tools should open in a new
window, and it should be connected to the “tab” you selected.
I have a bunch of iPads that are all supervised, and that are enrolled into a MDM server (Mavericks Server). I've added the app to the specific device group, but when I go to the profile settings and Single App Mode the only apps I can select are the builtin ones.
Is there no way to use a third party (enterprise) app as the app for Single App Mode?
EDIT: If you use Apple Configurator and add the app there you can set Single App Mode to use that app, I would imagine that would be possible when doing the same in Apple's Profile Manager, but it doesn't seem to be working here.
EDIT2: Looking at Apple's documentation it does indeed seem to be possible to select a third party app for single app mode using their Profile Manager, so why isn't the app showing in the list for me?
http://images.apple.com/education/docs/assessment_with_ipad_mar2013_v2.pdf
Go to the Device Group, after installing the app (that you want to show in Single App Mode dropdown and lock it to) do "Update Info" (small icon in bottom-middle-left of screen) on all the devices in that group. Wait a bit, then go to Single App Mode screen again, the app should start appearing.Works for me. The "Update Info" thing also works for Single Device as well and you can lock to any new app installed from Profile Manger, doesn't matter if the app was installed while supervising through Configurator or not.
So interestingly enough in the new update for Server (3.1.1) this seems to be working. The Enterprise app is now listed in the dropdown box.
However there also is about 10 empty items in the box with no text description. So it's clearly still a bit buggy.