Good evening everyone,
If I rename a resource outside of Hype (for example, the renamed resource B), the name of the resource does not update either in the "Assets panel" (I mean the name above the actual file, the one with the arrow pointing down next to it) or in the "Main Timeline panel".
Is there a way to have the renamed asset names automatically updated in the "Assets" and "Main Timeline" panels?
Thanks for your attention and for any help 
Sorry, there's not really a way to do this, but it is on our list to fix (and at least allow manual resource renaming).
It's been almost three years since the report, and to this day I still find myself having to reconnect all the images of the hype documents manually, when the program reports that the link is no longer available and asks to reconnect the resource.
This happens when I work on the same file on two computers, and inexplicably, when switching from one computer to another, the resources are no longer automatically recognized.
This is very frustrating because it wastes a lot of time, working with presentations of many slides that have several images, often hundreds, imported.
It would be really essential for Hype to have a system like Adobe Indesign and other Adobe programs, which report when a linked resource has been modified externally, and that once the link to the resource is re-established, the program searches for other suspended links in the reference folder and updates them automatically.
Thanks for the feedback. There's definitely a few things we can do to make this a little more resilient and have a better UI around re-linking.
Ultimately this comes about because of Apple's mac security enforcements (specifically for the App Store, and we've thus tried to keep the non-App Store version the same). Apps cannot freely look around the filesystem to do things like reading/linking files. Instead via implicit permissions apps can maintain a "bookmark" to files that they've been given access to. This does not work across machines. There's many other situations also where this can fail. Unfortunately, Apple started requiring this on macOS 10.7 and has not really updated or tried to improve this for apps since macOS 10.8...
