Teams App loading Microsoft Form - blank page

%3CLINGO-SUB%20id%3D%22lingo-sub-1010756%22%20slang%3D%22en-US%22%3ETeams%20App%20loading%20Microsoft%20Form%20-%20blank%20page%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1010756%22%20slang%3D%22en-US%22%3E%3CP%3EHello%3C%2FP%3E%3CP%3EFor%20my%20client%20I%20have%20built%20a%20form%20in%20Forms%20which%20has%20been%20wrapped%20up%20into%20a%20simple%20Teams%20app%20and%20added%20to%20the%20main%20navigation%20bar%20in%20Teams.%3C%2FP%3E%3CP%3EThe%20app%20manifest%20just%20contains%20a%20single%20staticTab%20with%20the%20contentURL%20being%20the%20link%20to%20complete%20the%20Form%2C%20as%20generated%20by%20Forms%20(starting%20%3CA%20href%3D%22https%3A%2F%2Fforms.microsoft.com%2FPages%2FResponsePage.aspx%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fforms.microsoft.com%2FPages%2FResponsePage.aspx%3C%2FA%3E)%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThis%20works%20fine%20in%20the%20web%20Teams%20client.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHowever%2C%20in%20the%20desktop%20client%2C%20it%20only%20works%20if%20we%20have%20set%20the%20Form%20to%20%22anyone%20with%20the%20link%22.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIf%20we%20set%20it%20to%20%22people%20in%20my%20organisation%22%20then%20the%20when%20we%20load%20the%20app%20it%20shows%20the%20green%20%22loading%22%20message%20for%20a%20second%2C%20then%20goes%20completely%20blank.%20No%20form.%20I%20guess%20the%20problem%20is%20something%20to%20do%20with%20the%20authentication%2C%20but%20I%20didn't%20think%20I%20would%20have%20to%20do%20anything%20special%20to%20get%20this%20to%20work.%20Again%20it%20works%20perfectly%20in%20the%20web%20client%2C%20we%20only%20see%20this%20error%20in%20the%20desktop%20client.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIs%20anyone%20able%20to%20replicate%20this%3F%20Any%20ideas%20on%20a%20resolution%3F%3C%2FP%3E%3CP%3EMany%20thanks%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1010756%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EAuthentication%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EDeveloper%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EForms%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EMicrosoft%20Teams%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1010987%22%20slang%3D%22en-US%22%3ERe%3A%20Teams%20App%20loading%20Microsoft%20Form%20-%20blank%20page%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1010987%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F56573%22%20target%3D%22_blank%22%3E%40Matthew%20Lamb%3C%2FA%3E%26nbsp%3Bgood%20question%20it%20is%20something%20with%20SSO%20and%20the%20client%20app.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1011509%22%20slang%3D%22en-US%22%3ERe%3A%20Teams%20App%20loading%20Microsoft%20Form%20-%20blank%20page%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1011509%22%20slang%3D%22en-US%22%3E%3CP%3EI%20have%20found%20a%20method%20which%20works%20for%20embedding%20SharePoint%20pages%20where%20you%20set%20the%20URL%20of%20the%20tab%20to%26nbsp%3B%3CEM%3E%3CA%20href%3D%22https%3A%2F%2Ftenancy.sharepoint.com%2F_layouts%2F15%2Fteamslogon.aspx%3Fspfx%3Dtrue%26amp%3Bdest%3D%2FSitePages%2FNew-Teams-Request.aspx%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Ftenancy.sharepoint.com%2F_layouts%2F15%2Fteamslogon.aspx%3Fspfx%3Dtrue%26amp%3Bdest%3D%2FSitePages%2FNew-Teams-Request.aspx%3C%2FA%3E%3C%2FEM%3E%20which%20handles%20the%20authentication%20without%20causing%20Teams%20to%20bring%20down%20the%20hammer%20and%20redirects%20to%20a%20SharePoint%20page%20of%20your%20choosing.%20However%20this%20doesn't%20work%20for%20redirecting%20to%20Forms.%20And%20adding%20the%20Forms%20form%20to%20the%20SharePoint%20page%20using%20a%20Web%20Part%20doesn't%20work%20because%20it%20gets%20loaded%20in%20a%20frame%20which%20just%20gets%20blocked.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThe%20only%20thing%20that%20works%20is%20to%20put%20a%20button%2Flink%20on%20that%20SharePoint%20page%20which%20opens%20the%20Forms%20URL%20in%20a%20new%20tab.%20When%20in%20the%20Teams%20client%20this%20then%20launches%20the%20Form%20in%20the%20browser%20window.%20Not%20ideal%20though.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1057119%22%20slang%3D%22en-US%22%3ERe%3A%20Teams%20App%20loading%20Microsoft%20Form%20-%20blank%20page%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1057119%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F56573%22%20target%3D%22_blank%22%3E%40Matthew%20Lamb%3C%2FA%3E%20Could%20you%20please%20try%20adding%20Form's%3CCODE%3EwebApplicationInfo*%3C%2FCODE%3E%26nbsp%3Bsection%20to%20your%20manifest.%26nbsp%3B%3C%2FP%3E%0A%3CDIV%20style%3D%22box-sizing%3A%20border-box%3B%20font-family%3A%20'Segoe%20UI'%2C%20'Helvetica%20Neue'%2C%20'Apple%20Color%20Emoji'%2C%20'Segoe%20UI%20Emoji'%2C%20Helvetica%2C%20Arial%2C%20sans-serif%3B%20font-size%3A%2014px%3B%20font-style%3A%20normal%3B%20font-variant-ligatures%3A%20normal%3B%20font-variant-caps%3A%20normal%3B%20font-weight%3A%20400%3B%20letter-spacing%3A%20normal%3B%20orphans%3A%202%3B%20text-align%3A%20start%3B%20text-indent%3A%200px%3B%20text-transform%3A%20none%3B%20white-space%3A%20normal%3B%20widows%3A%202%3B%20word-spacing%3A%200px%3B%22%3E%0A%3CDIV%3E%3CSPAN%3E%26nbsp%3B%26nbsp%3B%3C%2FSPAN%3E%3CSPAN%3E%22webApplicationInfo%22%3C%2FSPAN%3E%3CSPAN%3E%3A%26nbsp%3B%7B%3C%2FSPAN%3E%3C%2FDIV%3E%0A%3CDIV%3E%3CSPAN%3E%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%3C%2FSPAN%3E%3CSPAN%3E%22id%22%3C%2FSPAN%3E%3CSPAN%3E%3A%26nbsp%3B%3C%2FSPAN%3E%3CSPAN%3E%22c9a559d2-7aab-4f13-a6ed-e7e9c52aec87%22%3C%2FSPAN%3E%3CSPAN%3E%2C%3C%2FSPAN%3E%3C%2FDIV%3E%0A%3CDIV%3E%3CSPAN%3E%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%3C%2FSPAN%3E%3CSPAN%3E%22resource%22%3C%2FSPAN%3E%3CSPAN%3E%3A%26nbsp%3B%3C%2FSPAN%3E%3CSPAN%3E%22%3CA%20href%3D%22https%3A%2F%2Fforms.office.com%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fforms.office.com%3C%2FA%3E%22%3C%2FSPAN%3E%3C%2FDIV%3E%0A%3CDIV%3E%3CSPAN%3E%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%7D%3C%2FSPAN%3E%3C%2FDIV%3E%0A%3C%2FDIV%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1061236%22%20slang%3D%22en-US%22%3ERe%3A%20Teams%20App%20loading%20Microsoft%20Form%20-%20blank%20page%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1061236%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F359599%22%20target%3D%22_blank%22%3E%40Gousia_Begum%3C%2FA%3E%26nbsp%3BThanks%20for%20the%20suggestion%20but%20this%20didn't%20work%2C%20we%20get%20the%20same%20result.%26nbsp%3B%20Would%20I%20need%20anything%20in%20the%20validDomains%20section%3F%20Do%20you%20have%20this%20working%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1071251%22%20slang%3D%22en-US%22%3ERe%3A%20Teams%20App%20loading%20Microsoft%20Form%20-%20blank%20page%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1071251%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F56573%22%20target%3D%22_blank%22%3E%40Matthew%20Lamb%3C%2FA%3E%26nbsp%3BThanks%20for%20trying%20this%20out.%20Unfortunately%2C%20after%20some%20further%20investigation%2C%20it%20appears%20that%20their%20is%20yet-another-thing%3A%20the%20URLs%20that%20Forms%20use%20are%20different%20than%20the%20canonical%20URLs%20you'd%20get%20from%20the%20browser.%20At%20this%20point%2C%20what%20you%20are%20trying%20is%20not%20supported.%20Even%20if%20you%20got%20the%20%3CEM%3Eexact%20%3C%2FEM%3EURL%20correct%20and%20are%20able%20to%20host%20Forms%20as%20your%20own%20app...%20there's%20no%20guarantee%20that%20Forms%20doesn't%20change%20this%20URL%20in%20a%20few%20months%20from%20now.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E
Highlighted
Occasional Contributor

Hello

For my client I have built a form in Forms which has been wrapped up into a simple Teams app and added to the main navigation bar in Teams.

The app manifest just contains a single staticTab with the contentURL being the link to complete the Form, as generated by Forms (starting https://forms.microsoft.com/Pages/ResponsePage.aspx)

 

This works fine in the web Teams client.

 

However, in the desktop client, it only works if we have set the Form to "anyone with the link".

 

If we set it to "people in my organisation" then the when we load the app it shows the green "loading" message for a second, then goes completely blank. No form. I guess the problem is something to do with the authentication, but I didn't think I would have to do anything special to get this to work. Again it works perfectly in the web client, we only see this error in the desktop client.

 

Is anyone able to replicate this? Any ideas on a resolution?

Many thanks

7 Replies
Highlighted

@Matthew Lamb good question it is something with SSO and the client app.

Highlighted

I have found a method which works for embedding SharePoint pages where you set the URL of the tab to https://tenancy.sharepoint.com/_layouts/15/teamslogon.aspx?spfx=true&dest=/SitePages/New-Teams-Reque... which handles the authentication without causing Teams to bring down the hammer and redirects to a SharePoint page of your choosing. However this doesn't work for redirecting to Forms. And adding the Forms form to the SharePoint page using a Web Part doesn't work because it gets loaded in a frame which just gets blocked.

 

The only thing that works is to put a button/link on that SharePoint page which opens the Forms URL in a new tab. When in the Teams client this then launches the Form in the browser window. Not ideal though.

Highlighted

@Matthew Lamb Could you please try adding Form's webApplicationInfo* section to your manifest. 

  "webApplicationInfo": {
        "id""c9a559d2-7aab-4f13-a6ed-e7e9c52aec87",
        "resource""https://forms.office.com"
      }
Highlighted

@Gousia_Begum Thanks for the suggestion but this didn't work, we get the same result.  Would I need anything in the validDomains section? Do you have this working?

Highlighted

@Matthew Lamb Thanks for trying this out. Unfortunately, after some further investigation, it appears that their is yet-another-thing: the URLs that Forms use are different than the canonical URLs you'd get from the browser. At this point, what you are trying is not supported. Even if you got the exact URL correct and are able to host Forms as your own app... there's no guarantee that Forms doesn't change this URL in a few months from now. 

Highlighted

@Matthew Lamb- just checking to see if you made any progress on this.  I know that Gousia stated that it couldn't be done but I figured I'd check to see if you ever found another alternative to making this work.  Thanks in advance.
Mike

Highlighted
Hi MIchael - no, we have settled with embedding a SharePoint page with a link on it to launch the Form in a new tab.