Web Browser View not working

psfulgham · 08-13-2019 01:24 PM

Is there are problem or system wide error happening? I am able to view apps in android app but not in browser or in the preview pane. Those are just showing bottom menu without any data.

GreenFlux

I can confirm this. It just started happening to me on MacOS/Chrome. It DOES work in Brave browser though.

psfulgham

I am using Chrome Browser as well on Windows 10

GreenFlux

It’s working in Chrome Incognito mode though.

GreenFlux

More weirdness in Chrome:

Adam-google

@psfulgham Can you show a screenshot of what you’re seeing?

psfulgham

Basically it’s not showing any data in the web browser whereas in the android app it looks as it should. I can’t screenshot everything due to PI.

GreenFlux

Same here. Only the bottom buttons render in Chrome, unless you use Incognito mode.

Steve

No view selected. Possible your starting view is invalid or blank?

GreenFlux

@Steve, I confirmed the starting view is not blank. Also, it works normally in older versions of Chrome, and current version of Brave.

Adam-google

If either of you would be OK with me checking the app can you email the name of the app and account number to adam@appsheet.com?

GreenFlux

It’s affecting all of my apps on multiple accounts, tested from Mac and Windows when using Chrome v76 (current build). Incognito mode still works normally.

I had a Windows10 Machine still running Chrome v75 and that works in both modes. I’m reviewing the Chrome v76 changelog now.

psfulgham

I’m on Version 76.0.3809.100 (Official Build) (64-bit)

My other app builder is on Version 75 and he can see it so I agree it must be an issue with that version of Chrome.

psfulgham

@Adam, I sent you the information requested.I also confirmed that no starting view is blank but the problem is happening with all my apps.

Adam-google

@psfulgham Can you check which version of Chrome browser you’re running? If you try in incognito mode does it make any difference?

psfulgham

I checked it on my Pixelbook running Chrome OS Version 75.03770.144 . It works on that version.

GreenFlux

There were changes regarding lazy load, and also site specific cookies. I’m betting on the cookies since it works in incognito mode.

GreenFlux

So this definitely seems related to the current build of Chrome, but the really weird thing is, it just stopped working while I was in the middle of using the app editor.

@psfulgham, did yours stop working while you were using it as well? I updated a few days ago, and this just started within the hour.

Unless Google is pushing live updates without prompting the user (and I wouldn’t put it past them), then maybe it was an update to the AppSheet servers that triggered the outage to start for both of us within the last hour.

psfulgham

I am not sure how to verify when my browser updated. With that said, I was working in appsheet all morning and most of early afternoon and then next sync it stopped. First it was noticed by my other app developer about 1 hour ago running on 75 but then his came back. Mine has not on 76

Adam-google

Just a few more questions, when the app loads like this with the buttons but no view, are the buttons responsive at all? For example, showing the click animation / highlight behavior, if not showing the view itself?

If you fully restart the browser, does that have any effect? Or if you go into chrome settings and clear cached data / cookies / temporary files etc?

As for the timing, it may be related to platform changes that took effect today. But I don’t understand the problem well enough yet to be sure.

psfulgham

Well, it’s now come back. So I suppose it was a temporary problem. I didn’t do anything different but it is now back. To answer your question, when it was blank non of the buttons had responsiveness.

GreenFlux

@Adam, mine just started working again. But to answer your questions:

No, the buttons were not responsive.
Restarting, and deleting cookies did not help, but Incognito mode did.

So now it’s working again in v76. Perhaps they rolled back the platform update?

Adam-google

Thanks for all that information. We found some relevant error logs that indicate the proximate cause of the issue, but we’re still trying to understand what led to that state. Please let us know if you continue to see any new issues.