From mobile apps to microservices, from small startups to big enterprises, Gradle helps teams build, automate and deliver better software, faster.

Gradle Community

This (using `Set&lt;FileSystemLocation&gt;` instead of `FileSystemLocation`), however works:
```fun TaskProvider&lt;Sync&gt;.asFileSystemLocationSet(): Provider&lt;Set&lt;FileSystemLocation&gt;&gt; {
    return map {
        it.outputs.files.asFileTree.elements.get()
    }
}```
I think this is because Gradle understands that the `Set&lt;..&gt;` is live, and pulling a single `FileSystemLocation` out of it breaks that behavior

However - I don’t want to define my task input as `Set&lt;FileSystemLocation&gt;` when it’s only 1 file - I want to define it as `FileSystemLocation`

Perhaps the following would work:
```fun TaskProvider&lt;Sync&gt;.asFileSystemLocationSingleFile(): Provider&lt;FileSystemLocation&gt; {
    return flatMap { sync -&gt;
        sync.outputs.files.asFileTree.elements.map { it.first() }
    }
}```

The `asFileTree` step looks redundant:
```fun TaskProvider&lt;Sync&gt;.asFileSystemLocationSingleFile(): Provider&lt;FileSystemLocation&gt; {
    return flatMap { sync -&gt;
        sync.outputs.files.elements.map { it.first() }
    }
}```

I’ve had so many issues with flatmap tbh bc it switches the provider and seems to break the chain of dependent tasks, but I’ll try it

```fun TaskProvider&lt;Sync&gt;.asFileSystemLocationSingleFile(): Provider&lt;FileSystemLocation&gt; {
    return flatMap { sync -&gt;
        sync.outputs.files.asFileTree.elements.map { it.first() }
    }
}```
worked! Needed to use `.asFileTree` to get the actual file output instead of the directory