Sp-dev-docs: A web part is not rendered on a Single Web Part page in a mobile device

[jusper-dk]

Category

• [ ] Question
• [ ] Typo
• [x] Bug
• [ ] Additional article idea

Expected or Desired Behavior

An SPFx web part is rendered properly in a Single Web Part page in a mobile device

Observed Behavior

A web part is rendered properly in desktop mode but the page remains empty in mobile view. No constructor, nor onInit are executed.

Steps to Reproduce

• Create a Single Web Part Page with a web part
• Open it Chrome browser
• Expand the Dev Tools (F12) and emulate a mobile device, ex iPhone 6/7/8
• Refresh the page - no web part is rendered

[msft-github-bot]

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

[andrewconnell]

Repro'd...

Desktop view:

Mobile view when resized via emulator:

After refreshing mobile view via emulator:

[AndyBolam]

Same here, was able to reproduce in the same way as Andrew C did. This issue is affecting Single Page App Web Parts in our tenant, I have raised a ticket, will report back here if I get anywhere.

[AndyBolam]

Hi, any movement on this? I've been told that changing from Targeted release to Standard in the tenant will resolve, however that doesn't really help me!!

[lucs17]

Unfortunately, this bug is already rolled out to the Standard release in some tenants. So the solution to switch from Targeted to Standard release won't work anymore. We really need a fast bug fix from MS!

[AndyBolam]

Well that's torn it. Come on MS you are supposed to be seeing these bugs in preview before they are get to Standard, this has been a visible problem since 5 December!!

So another support ticket it is explaining exactly the same thing as before!!!!! As I don't seem to be able to reopen the one you closed without resolving. So frustrating.

Anyone else suffering with this, raise another ticket please :)

[idboyd01]

Hi, this is an issue for us too. A blank page loads when viewing Single Web Part pages on Android (Chrome) or iOS (Safari). Using the "Request Desktop Site" option on either browser loads the page correctly, but unfortunately this isn't a viable workaround for our end users.

I tested it with a completely default "Hello World" wepbart (v1.10, React Framework) and had the same issue.

[AndyBolam]

Hi idboyd01, yes Andrew Connell and myself have both also tested this and there is a proven issue. I am using Plumsail Forms which provides dedicated mobile forms using this type of page, it has led to several clients reporting broken business processes that rely on these. Plus, I'm unable to deploy any new projects that use these.

Highly frustrating and should be resolved asap. If MS want us to work within the confines of the spFX framework in Modern (which in the main is amazing), then they darn well ought to make sure tools that are used at the production level actually work before they deploy them into General release.

[Pietschik]

Any news here?

[miguelisidoro]

Any news about this issue? Will the update be made by MS without the need for developers to make changes on development side and redeploy the web part?
If development changes are necessary, which changes must be made on dev side?

Thanks

[andrewconnell]

MSFT SP engineering is aware of this and is investigating. I'll share updates if/when there's something I to share.

[miguelisidoro]

Thanks @andrewconnell, will wait for the update.

[cangot]

Thanks @andrewconnell : This is really critically for many important customers (>100.000 employees). We asked them to create support ticket referring to this thread to speed up the process if possible.

[andrewconnell]

@cangot understood... I can't fix it, I just help with the issue list & make them aware of a possible issue. They are investigating, but I need to defer to Microsoft to share updates, plans, timelines, etc.

[KevinTCoughlin]

We've identified the bug and are rolling out a fix. cc: @VesaJuvonen @lucabandMSFT @johnguy0

[cangot]

FYI : Microsoft Premier Support is telling me the fix deployment should take up to 3 weeks, but it could also be next week. Anyone can confirm ?

[andrewconnell]

@cangot If that's what MPS is saying, that's confirmation. :)

[KevinTCoughlin]

FYI - This was fixed in 2/21 build forward.

[msft-github-bot]

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