Link to image stopped working last 3 weeks

I’ve got a formula in a template that basically says to use [Default Signature] if the actual signature box is blank. The app formula for [Default Signature] is “/abc627ff.Transferee.Sign.151432.png”

This was working fine on 5th Sept 2022, but for the last week the PDF report shows

Screenshot from 2022-09-29 11-45-33.png

Clicking on this link just gives a “File Not Found” error. The file is still there and has not changed name, location or any security settings. File is also actually shared on google drive for anyone with the URL. I tried adding another virtual column to reference this as an image instead of a signature, which doesn’t show up either. Finally tried to use the Google drive URL instead

https://drive.google.com/file/d/12BrxAcV.../view?usp=sharing

with same issue. Also tried turning off Require Image and File URL Signing. Anyone any idea what changed or what I’m doing wrong?

if the [Default Signature ]column type is Image, please insert the following expression in the column’s app formula

https://drive.google.com/uc?export=view&id=1abcd2345

Where 1abcd2345 is the file ID of the image file in Google drive.

In the above URL copied by you, you will get the image file ID after /d/ and before /View, that is 12BrxAcV…

Please append this entire file ID in the URL string below

"https://drive.google.com/uc?export=view&id=12BrxAcV… "

and paste this URL in app formula of [Default Signature ]

.

2 Likes

I think this is a problem we have seen before with other image column types.
This might be a bug related to how the workflow is distributed on server.

About the fact that you were not able to see the image even with the GDrive URL, that’s something I can’t test or help

2 Likes

@Suvrutt_Gurjar This sort of fixes it. So what I have now is two columns

[Default Signature] is a signature type virtual column with your formula in

[Default Image] is an image type virtual column with your formula in

Unlike before, these both render ok in the app. Albeit [Default Image] has a dark/clear background. But they both show up basically the same as the error image I posted in the inital problem description. Weirdly though if you now click on the link this now opens up a new browser tab and shows the correct image.

So we have an image in the app and a URL that both work. But the template refuses to display the image. Any other suggestions?

@1minManager ,

Thank you for the updates. Could you mention the expression you are using in the template for displaying the default signature? And any specific reason you are having two columns now?

1 Like

I eliminated the template formula altogether to simplfy testing.

“1.1” is there just so I know that I’m seeing the latest change to the template.

Just in case an Image column type worked but Signature didn’t, or vice versa

This is the result. Not sure if https://drive.google.com/ missing is relevant

@1minManager

Yes, you are right. I am also getting the same erroneous result as yours in the pdf report, even though it show correctly in app. Let me look for any other option.

If you can upload the default image through the app, then it should display. You could temporarily add a row to the table to upload the image through the app and then copy that image path into a VC of image type. AppSheet typically assigns images a path like "“Products_Images/7D4926A7.Image.064925.png” you could copy this path into a VC of image type and use that VC name in the default image in template. My testing showed and image so uploaded displays properly in the report. You could delete that temporary row thereafter.

1 Like

Thats sort of what I did do before. [Default Signature] was a virtual column with a formula of

“Skips_Images/abc627ff.Transferee.Sign.151432.png”

@Steve can you log this as a bug?

1 Like

This will need some investigation by Support. Please contact them.

1 Like

I’ve stopped bothering. They do nothing for a week, then ask you to build an entirely new app to demonstrate the bug, then email two weeks later to say their closing the ticket.

Gone are the old days when someone actually logged into your app and tried to resolve the issue. Must be the Google way…

2 Likes