Thanks for the insight — you’re right about AsyncImage. I’m using a custom NetworkImage wrapper that adds fallback logic, placeholders, and manual refresh via UUIDs. It’s still backed by AsyncImage, but gives me more control for handling expiring SAS URLs. Might move to a full URLSession + @StateObject setup later for better caching and control. Appreciate you calling that out!

Thanks for the insight — you’re right about AsyncImage. I’m now using a custom NetworkImage wrapper that adds fallback logic, placeholders, and manual refresh via UUIDs. It’s still backed by AsyncImage, but gives me more control for handling expiring SAS URLs. Might move to a full URLSession + @StateObject setup later for better caching and control. Appreciate you calling that out!

Thanks for the insight — you’re right about AsyncImage. I’m now using a custom NetworkImage wrapper that adds fallback logic, placeholders, and manual refresh via UUIDs. It’s still backed by AsyncImage, but gives me more control for handling expiring SAS URLs. Might move to a full URLSession + @StateObject setup later for better caching and control. Appreciate you calling that out! 🙏

Thanks for the insight — you’re right about AsyncImage. I’m now using a custom NetworkImage wrapper that adds fallback logic, placeholders, and manual refresh via UUIDs. It’s still backed by AsyncImage, but gives me more control for handling expiring SAS URLs. Might move to a full URLSession + @StateObject setup later for better caching and control. Appreciate you calling that out! 🙏