Let me try and explain what’s going on and suggest an alternative.
If you try and navigate to that link (https://tinyurl.com/y7sqhbgo) in a desktop browser it gives a 311 error. An unsafe redirect.
This is because
file: protocols are not typically (I don’t know of any exceptions these days, but there probably are some, and some may have deply buried override settings) enabled for browsers as this is a security risk. It is effectively a pointer to a local file system.
Basically, it is a good thing and if you value device security you should probably be hapy that is the case. For those who don’t like this … well they’re probably the people who can implement overrides with their browser of choice.
You can always check the original URL validity in Safari on iOS. If you enter anything with
file: you’ll get the following.
If you want to work with the iOS Files app, then
shareddocuments://, in Safari will give you the following.
But I’ve never seen anything to that URL scheme beyond launching the app.
If you wanted to do something specific with a file on iOS, then consider using something like the originating app where iCloud sandboxing rules apply (i.e. Drafts for files in the Drafts iCloud folder structure), or something more generic perhaps like Shortcuts for say Dropbox (though Drafts also has great power here). Create some sort of automation (e.g. a Drafts action), then build the URL to trigger it, shorten that URL, and place that in your Google doc.
If you’re working on the Mac, I would assume you could apply a similar approach using Keyboard Maestro’s URL trigger capabilities and a bit of scripting/macro writing.
Hope that covers everything.