Jan 25 2019 11:12 AM - edited Jan 25 2019 02:42 PM
This issue needs to be escalated. I have opened a Microsoft Support ticket, I will post to GitHub if it is a PnP issue, which I think it is, please advise.
We have done some more testing on this problem and have found:
[1/25/2019 9:21 AM] We replaced the flickering Hero web part on this page and did an extraction. The guidFile # below was cut off but it is the same as the one in the next hyperlink.
[1/25/2019 9:21 AM] We used the extraction from the above site and page to provision the same page on this site but the problem persists. Note the guidFile # below was cut off but it is the same which we think maybe a problem because shouldn't it be different?
Jan 25 2019 04:15 PM
This is a little hard to debug without knowing what code you are using. Can you share the PnP Code you are using to set the hero web part? I'd gladly explore this.
Jan 25 2019 04:47 PM
This has all been working for the last 6 months so I think the Hero part has been published recently and changed or there are CDN issues.
I attached the XML file, inserted an image of the console showing the repeating error, and included the details of the error from the console below.
thumbnail:1 GET https://southcentralus1-mediap.svc.ms/transform/thumbnail?provider=spo&inputFormat=png&cs=UEFHRVN8U1... 404
Image (async)
fe @ sp-pages-assembly_en-us_fd7935d40583aa7d6c88123f98f14171.js:879
Xt @ sp-pages-assembly_en-us_fd7935d40583aa7d6c88123f98f14171.js:879
commitUpdate @ sp-pages-assembly_en-us_fd7935d40583aa7d6c88123f98f14171.js:887
commitWork @ sp-pages-assembly_en-us_fd7935d40583aa7d6c88123f98f14171.js:879
x @ sp-pages-assembly_en-us_fd7935d40583aa7d6c88123f98f14171.js:879
C @ sp-pages-assembly_en-us_fd7935d40583aa7d6c88123f98f14171.js:879
y @ sp-pages-assembly_en-us_fd7935d40583aa7d6c88123f98f14171.js:879
v @ sp-pages-assembly_en-us_fd7935d40583aa7d6c88123f98f14171.js:879
h @ sp-pages-assembly_en-us_fd7935d40583aa7d6c88123f98f14171.js:879
s @ sp-pages-assembly_en-us_fd7935d40583aa7d6c88123f98f14171.js:879
enqueueSetState @ sp-pages-assembly_en-us_fd7935d40583aa7d6c88123f98f14171.js:879
window.spModuleLoader.o.setState @ sp-pages-assembly_en-us_fd7935d40583aa7d6c88123f98f14171.js:779
t.setWebPartWidth @ sp-hero-webpart-bundle_en-us_1f9064ffbbf132ffd004ba4829856a67.js:202
t.onAfterResize @ sp-hero-webpart-bundle_en-us_1f9064ffbbf132ffd004ba4829856a67.js:202
t._internalOnAfterResize @ sp-pages-assembly_en-us_fd7935d40583aa7d6c88123f98f14171.js:1463
(anonymous) @ sp-pages-assembly_en-us_fd7935d40583aa7d6c88123f98f14171.js:1463
(anonymous) @ sp-pages-assembly_en-us_fd7935d40583aa7d6c88123f98f14171.js:1463
e._onContainerResize @ sp-pages-assembly_en-us_fd7935d40583aa7d6c88123f98f14171.js:1463
e @ sp-pages-assembly_en-us_fd7935d40583aa7d6c88123f98f14171.js:865
c @ sp-pages-assembly_en-us_fd7935d40583aa7d6c88123f98f14171.js:865
f @ sp-pages-assembly_en-us_fd7935d40583aa7d6c88123f98f14171.js:865
setTimeout (async)
u @ sp-pages-assembly_en-us_fd7935d40583aa7d6c88123f98f14171.js:865
s @ sp-pages-assembly_en-us_fd7935d40583aa7d6c88123f98f14171.js:865
Jan 28 2019 04:06 PM
I am getting the same experience when applying a PnP template that contains a hero web part. When manually adding a new hero web part to a page, it looks like the JSONProperties property has a new object property called imageUrl: {"imageUrl": "https://eastus1-mediap.svc.ms/transform/thumbnail?provider...}. This property not included when creating the Hero webpart from the PnP template. Do you think the web part was updated to retrieve thumbnails?
Jan 28 2019 04:18 PM - edited Jan 29 2019 03:42 PM
Here are my concerns . . .
I have reported this to Microsoft Support who cannot do anything because they don't cover PnP and on GitHub where PnP issues are supposed to be. I am hoping someone will consider this important because we really can’t afford for the different Microsoft entities to be passing the buck on these problems.
Just consider this, let’s say we deploy applications with Hero web parts by PnP with there being only 3 pages per client. If we have 20 clients, then someone needs to go and manually remove, add, and setup the Hero web parts 60 times. But each tile image and link setting needs to be noted and subsequently recreated because the interface does not store the Hero tile setting information in a list that can easily be managed. That is a potential of 300 individual Hero tiles needing to be preserved, and re-setup. That takes a long time using the current interface.
This is not just a PnP problem, the Hero web part does not fail gracefully in the absence of this configuration element. The Hero web part has been out for more than a year and until this has been resolved, Hero web parts that are PnP provisioned will constantly loop to access a thumbnail that does not exist. This will in turn throttle your tenant if too many pages are opened that have this problem, and the web sites in the tenant become unavailable for a period of time.
It seems that the Hero web part code has been updated to reference a thumbnail image for each Hero tile. There is a new JSON property for this thumbnail which is probably generated if the Hero part is added via the user interface. However PnP, which is the only way we have been given to automate installs, does not yet accommodate this property. My final comments are:
Feb 04 2019 12:00 PM
Hi,
We are seeing the same issue in our tenant,for multiple hero web parts.
we logged a prem support call with MS, and they have pointed us to this thread......
issue is we have not used PNP to provision anything in our tenant we added all the hero web parts manually. we are seeing the same issue with the Auseast error.
investigation found that Chrome and Firefox had the flickering image but edge did not.
Since receiving the last message fro MS saying it was the PNP provisioning system the issue is no longer an issue.
Hope your issues are sorted too.