none
Office 365 Dialog API throwing error "ADD-In ERROR A problem occurred while trying to reach this add-in" RRS feed

  • Question

  • We are using dialog api for (non-office 365) authentication flow. It successfully launches dialog (using dialog API i.e Office.context.ui.displayDialogAsync). However after providing credentials and submitting form, it throws error:

    ADD-In ERROR
    A problem occurred while trying to reach this add-in

    This found to be working in few laptops but does not work in others.

    What could be the cause of this? How do we get rid of the error.

    Wednesday, November 23, 2016 3:00 AM

All replies

  • Looks like it was working with outlook version 1610 but stopped working after upgrade to outlook version 1611. There is a security update recently provided by office 365 (https://support.microsoft.com/en-us/kb/3115135). Could this be related to this?
    Wednesday, November 23, 2016 5:01 PM
  • Hi,

    I followed the steps from http://simonjaeger.com/lets-have-a-dialog-about-the-dialog-api/ and tested in Version 1611 (Build 7571.2006). After submitting, the message could successfully be retrieved.

    Could you share us the detail steps, we could try to reproduce.

    If you think it might be related to update, you could follow the KB below to convert an earlier version to check if the issue causes from Office or your project.  https://support.microsoft.com/en-us/kb/2770432

    Regards,

    Celeste


    MSDN Community Support
    Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact MSDNFSF@microsoft.com.

    Thursday, November 24, 2016 9:48 AM
    Moderator
  • Yes, it works fine after reverting to version 1610 from version 1611. Multiple users have verified this.

    The issue occurs during authentication, so there are few redirects which happen during the flow. The login page is correctly displayed but as soon as user clicks on "Sign In" button, it gives this error.

    Can you think of something changed in version 1611 which might be causing it? Is there a way to debug and see the error in the dialog API?


    • Edited by Piyukuls Monday, November 28, 2016 4:32 PM
    Monday, November 28, 2016 4:16 PM
  •  

    Hi,

    Since it has confirmed that the issue causes from the update of Office, I do apologize that I could not offer any other suggestion to narrow down the issue in the newest version.

    Since your issues is complicated, I'm trying to involve some senior engineers into this issue and it will take some time. Your patience will be greatly appreciated.

    Sorry for any inconvenience and have a nice day! 

    Regards,

    Celeste


    MSDN Community Support
    Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact MSDNFSF@microsoft.com.

    Tuesday, November 29, 2016 6:47 AM
    Moderator
  • Please let me know.
    Thursday, December 1, 2016 4:19 PM
  • Hi,

    We are investigating this issue, thank you for working with us.  Could you please give us:

    • The build number (not the version number but build number) of the Outlook build in which the dialog API works
    • The build number in which the API doesn't work for you
    • What channel are you subscribed to (e.g. Insiders Fast, or any other)?

    You can get all the information above by going to File>Office Account while in Outlook.  Look under "Office Updates". You should also verify that all your URLs are HTTPS, otherwise the url won't work; there where recent changes that enforce that restriction more stringently

    Thank you.


    Program Manager, Office Developer Platform.

    Monday, December 5, 2016 7:04 PM
    Moderator
  • Thanks for the above details. Please find below requested details.

    - Build number of outlook on which dialog API works = 7466.2038 (version 1610)

    - Build number of outlook on which dialog API does not work = 7571.2006 (version 1611)

    - We have mixed users. Some users use Insider program where as others install office 365 2016 from portal

    Could you please confirm if the changes related to HTTPS is present only in build 7571.2006 and not in build 7466.2038?

    Regarding all URLs to be HTTPS: Will check on this. Is this change permanent and will remain as it is going forward? Is there a way to enable or disable this restriction and verify?


    • Edited by Piyukuls Monday, December 5, 2016 10:13 PM
    Monday, December 5, 2016 10:07 PM
  • Yes, we added more HTTPS enforcement since build 7571. Now every page loaded in dialog (including redirecting) needs to be HTTPS.

    Yes, this change is permanent and will remain as it is going forward. For now, this restriction cannot be disabled.

    Thursday, December 8, 2016 1:44 AM