SPFX Teams Personal App Pop out app feature blank screen

Rtoribiog commented 3 years ago

Describe the bug

We created a spfx teams static app , using the following url. "https://{teamSiteDomain}/_layouts/15/TeamsLogon.aspx?SPFX=true&dest=/_layouts/15/teamshostedapp.aspx%3Fteams%26personal%26componentId={{SPFX_COMPONENT_ID}}%26forceLocale={locale}" it´s working ok in teams desktop app , when the user click in pop out app , new window is opened but blank screen appears. It works if it´s a sharepoint page but not spfx webpart.

https://windowsreport.com/teams-pop-out-apps/

Steps to reproduce

Provide steps to reproduce the behavior:

Go to Teams Desktop
Right click in Teams personal app in the left bar
Select Pop out app
Teams app is not loaded , blank screen

Expected behavior

Teams app needs to be loaded the same than in desktop app

Environment details (development & target environment)

Complete the following (if ignored you'll be prompted for it before we can address your issue... save the time and provide it in your initial submission).

Developer Environment : Windows 10
Target Environment: SharePoint Online
Framework : Node.js v10.13
Browser(s): Teams Desktop
Tooling: SPFx v1.11

Additional context

Provide any other context about the problem.

Thanks for your contribution! Sharing is caring.

Submission guidelines

Dear @VesaJuvonen

ghost commented 3 years ago

Thank you for reporting this issue. We will be triaging your incoming issue as soon as possible.

mrzyko commented 3 years ago

Yup, I can confirm this bug. It also appears with our personal app, using spfx.

andrewconnell commented 3 years ago

Have you tried using the latest version of SPFx, v1.11? The version you're using is ~12mo old... that's the first thing MSFT will ask you to do is to validate this against the latest version.

zakwht commented 3 years ago

I can confirm this appears with our personal app using SPFx 1.11

Rtoribiog commented 3 years ago

updated spfx to version 1.11 and it´s still happening the same. Thanks

andrewconnell commented 3 years ago

In your OP you say you're using Node.js v12... SPFx is only supported with Node.js v10 at this time. Although I suspect it's a typo as you should get all sorts of build errors if you try to use Node.js v12.

Rtoribiog commented 3 years ago

In your OP you say you're using Node.js v12... SPFx is only supported with Node.js v10 at this time. Although I suspect it's a typo as you should get all sorts of build errors if you try to use Node.js v12.

corrected it´s v10.13

RoelVB commented 3 years ago

I thought some technical information could be useful.

The embedded and pop-out window both load an iframe with a URL like: https://contoso.sharepoint.com/_layouts/15/teamshostedapp.aspx?teams&personal&componentId=00000000-0000-0000-0000-000000000000&env=TeamsPageWebView

The only difference I noticed is that the content of the embedded iframe contains a <div class="SPPageChrome isFluent"> (which contains the webpart) in the body, but the pop-out window is missing this div.

praveenpudi329 commented 3 years ago

Hi All,

Any updates. we are facing the same issue, no difference in fiddler trace for embedded & pop out

AhmadAlamili commented 3 years ago

I have the same issue, any updates?

giuleon commented 3 years ago

Hi everybody, we are facing the same issue, is there any progress here @andrewconnell @VesaJuvonen @lucabandMSFT, the product team is already informed about that?

giuleon commented 3 years ago

Hi everybody, I officially raised a ticket to Microsoft I'll keep you all in the loop as I have news

VesaJuvonen commented 3 years ago

Hi all, this issue has been fixed and is gradually rolling through eh Teams release circles. Hunting down more detailed ETA internally and hoping to update the thread within upcoming days.

giuleon commented 3 years ago

Thanks @VesaJuvonen for your update

VesaJuvonen commented 3 years ago

Here's visual proof from normal E3 that the issue is fixed. We have confirmed also that the issues on the support channels have been properly fixed. Thanks everyone for pushing on this.

Closing issue as fixed.

SalmanPadder25 commented 3 years ago

Thanks much @VesaJuvonen for the confirmation. Issue is resolved for my client after the update was pushed.

ghost commented 3 years ago

Issues that have been closed & had no follow-up activity for at least 7 days are automatically locked. Please refer to our wiki for more details, including how to remediate this action if you feel this was done prematurely or in error: Issue List: Our approach to locked issues

SharePoint / sp-dev-docs