Hi @zachgibson, this is currently by design. We do not eagerly write the initial value to the external system (in any strategy, including appStorage). The reason a file with empty bytes is being written is because we need a file on disk to observe changes to it via dispatch source.

Can you describe what problem this is causing for you so that we can evaluate?

But since this isn't an issue with the library I am going to convert it to a discussion. Let's continue the conversation over there!

I see @mbrandonw, this makes sense. I guess I'm just using it in an unexpected way.

My use-case is a Metal shader "REPL-like" app. When saving your shader externally Sharing picks that up and we re-compile/draw the new shader. So, when someone creates a new shader in the app I default the string to a sample shader program that has all the necessary boilerplate. This is where I am needing the file to have the contents initially.

I'm down to handle this in my own way but I haven't thought of a reliable mechanism to know when to update the state to cause it to be written to the file.

For now I'm creating the file and seeding the contents myself at creation time. @mbrandonw any considerations here or is this totally fine?