Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

SPFX Teams app blank screen when you open it for second time #8191

Closed
1 of 9 tasks
Rtoribiog opened this issue Jun 14, 2022 · 13 comments
Closed
1 of 9 tasks

SPFX Teams app blank screen when you open it for second time #8191

Rtoribiog opened this issue Jun 14, 2022 · 13 comments
Labels
area:spfx Category: SharePoint Framework (not extensions related) status:fixed-next-drop Issue planned to be fixed in an upcoming release. type:bug-suspected Suspected bug (not working as designed/expected). See “type:bug-confirmed” for confirmed bugs.
Milestone

Comments

@Rtoribiog
Copy link

Target SharePoint environment

SharePoint Online

What SharePoint development model, framework, SDK or API is this about?

💥 SharePoint Framework

Developer environment

Windows

What browser(s) / client(s) have you tested

  • 💥 Internet Explorer
  • 💥 Microsoft Edge
  • 💥 Google Chrome
  • 💥 FireFox
  • 💥 Safari
  • mobile (iOS/iPadOS)
  • mobile (Android)
  • not applicable
  • other (enter in the "Additional environment details" area below)

Additional environment details

browser version Teams desktop App
SPFx version 1.13
Node.js version V 12.13
etc

Describe the bug / error

When you load your custom sfpx teams app for second time after clicking in any other section in teams it doesn't load up and it shows white screen.

After digging in the developer tools i've seen this error

image

Steps to reproduce

You have a custom spfx teams app , you click on the app and it's loads fine

loads

Later you click in any option in the menu like calendar , teams chat

otherfeature

You click in teams app again and then it show up white screen

Error

Expected behavior

The app it works fine without taking in count where do you click or if you want to return to the app after doing any other action.

@Rtoribiog Rtoribiog added the type:bug-suspected Suspected bug (not working as designed/expected). See “type:bug-confirmed” for confirmed bugs. label Jun 14, 2022
@ghost
Copy link

ghost commented Jun 14, 2022

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

@ghost ghost added the Needs: Triage 🔍 Awaiting categorization and initial review. label Jun 14, 2022
@Rtoribiog
Copy link
Author

@AJIXuMuK
Copy link
Collaborator

Hi @Rtoribiog - thanks for reporting this one.
Could you please share your custom manifest either here or you can send it to me aterentiev@microsoft.com

@AJIXuMuK AJIXuMuK added area:spfx Category: SharePoint Framework (not extensions related) Needs: Author Feedback Awaiting response from the original poster of the issue. Marked as stale if no activity for 7 days. and removed Needs: Triage 🔍 Awaiting categorization and initial review. labels Jun 14, 2022
@Rtoribiog
Copy link
Author

Rtoribiog commented Jun 14, 2022

you have it in the email.

Basically we want to do the same of viva app showing the top ribbon.

The first time the app loads it works fine, but when you click in another section and return it fails, due that it’s not able to construct the url due the ?app=portals

Thanks

@ghost ghost added Needs: Attention 👋 Original poster responded to request for feedback, awaiting attention from Microsoft / community. and removed Needs: Author Feedback Awaiting response from the original poster of the issue. Marked as stale if no activity for 7 days. labels Jun 14, 2022
@AJIXuMuK
Copy link
Collaborator

Thank you @Rtoribiog!
I don't see ?app=portals in your manifest.
Are you saying it is added when navigating back to the app?

Also, the manifest is not completely correct. As pointed out in the article you've mentioned, in webApplicationInfo you should set resource as https://{teamSiteDomain}, not the actual domain name.

Could you please also update the manifest and test it again?

Thanks!

@AJIXuMuK AJIXuMuK added Needs: Author Feedback Awaiting response from the original poster of the issue. Marked as stale if no activity for 7 days. and removed Needs: Attention 👋 Original poster responded to request for feedback, awaiting attention from Microsoft / community. labels Jun 14, 2022
@Rtoribiog
Copy link
Author

hello @AJIXuMuK , sorry my fault, i've sent you old version of the app. Because all the things you mentioned were fixed some time ago. I sent you current version by email again. Thanks

@ghost ghost added Needs: Attention 👋 Original poster responded to request for feedback, awaiting attention from Microsoft / community. and removed Needs: Author Feedback Awaiting response from the original poster of the issue. Marked as stale if no activity for 7 days. labels Jun 15, 2022
@Rtoribiog
Copy link
Author

hello @AJIXuMuK , have you seen anything that can be wrong or it's a bug as i'm thinking. Adding also @GrahamMcMynn to the thread, maybe he knows what is going on. Thanks

@AJIXuMuK
Copy link
Collaborator

Hey @Rtoribiog - we're looking into it and will update the thread as soon as have further details.

@AJIXuMuK
Copy link
Collaborator

@Rtoribiog - this has been fixed and will be rolled out WW in the next couple of weeks.

@AJIXuMuK AJIXuMuK added status:fixed-next-drop Issue planned to be fixed in an upcoming release. and removed Needs: Attention 👋 Original poster responded to request for feedback, awaiting attention from Microsoft / community. labels Jun 21, 2022
@AJIXuMuK AJIXuMuK added this to the 06-17 milestone Jun 21, 2022
@Rtoribiog
Copy link
Author

thanks so much

@Rtoribiog
Copy link
Author

hello @AJIXuMuK , the deployment to teams app was released week ago. But still is not working properlly. Now when you click again in the app open the browser of the url instead of open the app inside teams.

Attached screenshot with the problem , feel free to reach me for more info

error

@AJIXuMuK
Copy link
Collaborator

That seems to be a separate bug.
I will create a new one to track it properly.

@ghost
Copy link

ghost commented Jul 21, 2022

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

@ghost ghost locked as resolved and limited conversation to collaborators Jul 21, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
area:spfx Category: SharePoint Framework (not extensions related) status:fixed-next-drop Issue planned to be fixed in an upcoming release. type:bug-suspected Suspected bug (not working as designed/expected). See “type:bug-confirmed” for confirmed bugs.
Projects
None yet
Development

No branches or pull requests

2 participants