I created a simple app to get and send data to SharePoint lists. It looks fine if I browse outside SharePoint (on PowerApps mobile app, on PowerApps desktop app, on browser directly through web link, etc.). But, if I embed the app (any app) in a SharePoint Page, a black cover is beign showed. All controls are enabled and I can input text and click on buttons; but I can't see them.
It seems like a screen resolution related issue. I just tested using a 1366 x 768 resolution and this black section appears and seems to be growing as scroll down (like a parallax effect). After that, I tested using a 1920 x 1080 resolution and, as screen don't need scroll-bar and there is no way to scroll down, black cover doesn't appear.
1366 x 768 resolution:
1920 x 1080 resolution:
It would be great if anyone has resolution.
Hi @BrianGarnica ,
Do you mean that this issue would be shown up when the Scroll bar is existed?
Based on the issue that you mentioned, I have made a test, and the issue is confirmed on my side. If I embed a canvas app through the "PowerApps web part", the issue would show up. I think this issue may be related to layout.
As an fixed solution, I agree with your thought almost. You could consider change your canvas app resolution to 1920 x 1080 to fix this issue.
Currently, I could not come up with other better solution to fix this solution. I would post this issue to my Product Team, if this issue is fixed. I would reply here. As an temporary solution, please try to change your canvas app resolution to 1920 x 1080 to fix this issue.
I have the same issue in Edge and Chrome however when I view the page in Firefox, it shows up ok. Not sure why. Glad I found this post. I will try changing resolution.
Just chiming that this also first started happening on my company's SharePoint on 6/3/2020. My current solution has been to shrink the size of the embedding so the app fits without having to scroll down the page, but this makes any small text or buttons harder to read/use.
Yes Please, this problem seems to have started recently, and I never had this issue before June. Can we get this issue up the chain to Microsoft and PowerApps somehow?
I have a ticket opened with Microsoft and was on the phone with them yesterday. They were able to reproduce the issue and are working on it. More to come ...