New Bug Encountered: Images not showing consistently on Safari

[Kirk_Masden]

Hi! I think there may be a new problem with how apps are rendered on the Safari browser on Macs. As you can see from the images, everything seems fine on Chrome but not on Safari. Using Chrome is no big deal for me personally but it would be nice if the platform worked on all major browsers.

[Kirk_Masden]

Oh dear . . . I thought this was just a browser issue but I’m having the same problem on my Android phone.

By the way, on Safari a erased the cash but that didn’t help.

This is all very odd because I haven’t edited this app for a long time and now I’m suddenly having a problem.

[Steve]

I would take triangle to mean the image is not publicly accessible or does not exist.

[Kirk_Masden]

Thanks! That seems to be how the app began to interpret these images on Safari and on my Android phone – but not on Chrome for some reason. I erased the AppSheet app from my Android phone, reinstalled it and all is well again.

The images that are getting the triangle are on the server I have access to at my work place but they are accessible. Hmmm. Wonder what the cause is.

P.S. This is the second time in recent history that reinstalling my app on my Android (Huawei) phone has made a problem go away:

Had to reinstall app on Android phone Questions

Hi! I’m using a Huawei P9 lite. The “System update” section of the settings says “EMUI 5.0.4” and no updates are available. I was using an app I built on AppSheet but, for some reason, I suddenly found myself unable to start it up. It seems to have been stopped at an early stage of the app’s startup sequence, where data is being loaded into the app. I tried restarting the app but no luck – same issue. Rebooting the phone didn’t work either. Uninstalling the app and then reinstalling it wo…

[Kirk_Masden]

I’ve saved the html source for both browsers and, as expected, the code is the same. Interestingly, however, the browsers respond differently to the graphic url addresses. First, here’s a sample address (taken from the html):

“https://www.appsheet.com/remote/www2.kumagaku.ac.jp%2Fteacher%2F~masden%2F2017%2FICS%2F1017%2Flogo%2...”

This works when pasted into Chrome but not in Safari, even though I’m logged into the same account on Safari.

It works without a hitch on Firefox, though, even though I’m NOT logged in to AppSheet there.

Could something have changed on the AppSheet platform that might have caused this? If it were only Safari that would be less of a concern but basically the same thing happen on my Android phone.

Finally, here’s what happened with the same URL on Safari:

[Steve]

I think you should engage support@appsheet.com on this one.

[Kirk_Masden]

Thanks! I was just in the process of doing that.

[Adam-google]

Hi, we tried loading the same url in Safari and it was working here. Trying to understand what this error message might imply.

Is there any pattern you can identify to the images that aren’t working (or is it all of them)? Are they images that were recently added through the app?

[Kirk_Masden]

Thanks Adam!

All of the images are old ones that I put on my server and that I access in the app through expressions.

The URL now works properly in my Safari browser and the app itself is working well too. I would say that it’s probably a quirk of my own browser on my particular machine except that I had the same issue on my Android phone for a while too. Fortunately, the phone is also fine now.

Thanks for your help. I’ll post here again if the same issue comes up again.

[Steve]

Possible that your server is sporadically unavailable?

[Kirk_Masden]

Thanks Steve! In this case, I was going back and forth between Safari and Chrome and everything was working consistently in Chrome but failing equally consistently on Safari. So, I don’t think it was an issue with my server. Since then, by the way, everything has been fine.

[Adam-google]

We saw another report of the same error message around the same time, and we think now that this was related to an issue with one of our servers that should be resolved now. If you see it happen again, please let us know.