When I flash or reformat a usb drive via gui based software tools such as Balena Etcher the new file system info is not shown on gnome or any gui applications also lsblk refuses to show new data regarding usb’s info even upon lsblk /dev/sda. However when I use sudo blkid /dev/sda it shows the correct info related to the new filesystem info. This issue persists on debian 13 & Fedora however it does not happen on ubuntu 22.04 in fact this issue was non existent up until late 2023. Since the issue arised I have been forced to flashing via disk destroyer and using eject via terminal. I am addressing this issue not because it will effect everyone but because many new users immigrating to Linux may not understand some of the seemly arbitrary nuances.
It has always been standard practice when using linux to dismount devices before altering them and remounting the devices after the change is complete. Does the system properly recognize the altered state when it is newly connected after a disconnect?
Udevadm acts upon new info when udev detects a newly connected device and configures it. Already connected devices do not trigger that action automatically even when changes are made.
Your issue appears to be directly related to Balena Etcher and how you may be using it, not a fedora issue at all.
As far as lsblk and blkid are concerned they operate differently.
lsblk uses the cached partition table info for its reports since that must be available for the system use at all times for mounted file systems.
blkid reads the data directly from the device.
Think about what may happen to a file system if its size, location, or type were altered when already mounted and the system tried writing to it. Having the incorrect cached info could destroy the file system.
This is why a connected device is read once at connect time and that data cached for future use. It seems Balena Etcher may be modifying the device after it is already attached and leaves it with the stale info in the cache. (User error in not dismounting the file system before altering it)
That problem is NOT a fedora issue, but instead is an issue with the app (which really should not be making alterations to a mounted device) or even worse an issue with the users procedures by allowing an app to make alterations on a mounted device to change file systems or partition tables.
When I am flashing a usb drive I recognize that the system automatically mounts the existing file system on that drive as soon as it is detected. I manually dismount it then flash the new image onto the device. To test the new image I then disconnect it and reconnect it before checking the content. This is standard practice for all linux users and by doing this you ensure only the current condition is in the system cache.