search

OfficeDev / office-js-docs-pr

Microsoft Office Add-ins Documentation
https://learn.microsoft.com/office/dev/add-ins
Creative Commons Attribution 4.0 International
403 stars 249 forks source link

Add-In Sample Failing #2529

Closed elthombre closed 3 years ago

elthombre commented 3 years ago

I have an outlook.office.com account and I created a developer ID per the instructions. It fails to properly launch giving me a 401 "unauthorized" error.

It's so frustrating when your samples don't work. As a developer... it just makes you wanna pull your hair out.

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

AlexJerabek commented 3 years ago

Hi @elthombre,

I'm sorry to hear about your frustration. Can you please tell us where in the quick start you're encountering the error? Also, are you using the yeoman generator or Visual Studio to create your add-in?

elthombre commented 3 years ago

Presently, I'm using the Visual Studio version. It launches the new window in Chrome where I receive this error:

"Something went wrong and we couldn't start this add-in..."

When I bring up the 'Developer Tools' -> Console, there's a bunch of 404 errors.

I will ad that I had to change the "~remoteAppUrl" in the source to point to the localhost in order to get it to run.

Also, if I do not close the OWA window when I stop debugging, the context add-in options within the message window don't show up

AlexJerabek commented 3 years ago

Thank you for sharing those details. Are you encountering the same issues when following the yeoman generator path?

@ElizabethSamuel-MSFT. are you able to repo the issue in Visual Studio?

ElizabethSamuel-MSFT commented 3 years ago

@elthombre You should be able to keep ~remoteAppUrl in the manifest. We'll investigate the issues you're facing.

It's great that you joined the developer program! If you haven't already read them, can you also see if the developer program docs are helpful with configuring your tenant/account?

elthombre commented 3 years ago

The problem with the Yeoman version of the tutorial is that its functionality is not the same.

ElizabethSamuel-MSFT commented 3 years ago

@elthombre I haven't been able to repro your situation.

What I did:

If I missed anything in my repro, let me know so I can include and try again.

Also, can you clarify what you mean by "if I do not close the OWA window when I stop debugging, the context add-in options within the message window don't show up"? Do you mean the context menu if you, for example, right-click in the message? If that's what you mean, then that's expected since Outlook web add-ins are not included in that menu whether or not you're debugging.

Thanks.

ghost commented 3 years ago

This issue has been automatically marked as stale because it is marked as needing author feedback but has not had any activity for 4 days. It will be closed if no further activity occurs within 3 days of this comment. Thank you for your interest in Office Add-ins!

ghost commented 3 years ago

This issue has been closed due to inactivity. Please comment if you still need assistance and we'll re-open the issue.

elthombre commented 3 years ago

@elthombre I haven't been able to repro your situation.

What I did:

  • Created a dev program subscription and set it up
  • In VS 2019, created a new project and made updates per the quick start instructions (Note: I did NOT replace ~remoteAppUrl in the manifest)
  • In VS, set browser to Google Chrome then pressed "Start" to start debugging
  • In the "Connect to Exchange email account" dialog box, entered user name (e.g. username@domain*.onmicrosoft.com) and password of the account I created in dev program subscription setup
  • VS automatically opened outlook.office365.com in Chrome. I had no emails so I sent myself one then clicked on it to view in the Reading Pane. Clicked ellipsis (...) for more actions then clicked the name of the add-in in the menu. The task pane opened with the message properties as expected.

If I missed anything in my repro, let me know so I can include and try again.

Also, can you clarify what you mean by "if I do not close the OWA window when I stop debugging, the context add-in options within the message window don't show up"? Do you mean the context menu if you, for example, right-click in the message? If that's what you mean, then that's expected since Outlook web add-ins are not included in that menu whether or not you're debugging.

Thanks.

Yes, right-click context menu