Problems with MapboxMaps dependency

[evilhonda3030]

Hi, I am trying to integrate with Tuist on my project. I very love the product but I experience a weird issue.

https://gist.github.com/evilhonda3030/807fbba431c6fb1f5cec014fdb87bd06 - this a test Tuist config I used to reproduce the issue

The problem is a Mapbox dependency build fails with an error:

error: filename "Bundle+MapboxMaps.swift" used twice: '/Users/egormikhailov/Documents/Test/TestTestTuist/Tuist/Dependencies/SwiftPackageManager/.build/checkouts/mapbox-maps-ios/Derived/Sources/Bundle+MapboxMaps.swift' and '/Users/egormikhailov/Documents/Test/TestTestTuist/Tuist/Dependencies/SwiftPackageManager/.build/checkouts/mapbox-maps-ios/Sources/MapboxMaps/Foundation/Extensions/Bundle+MapboxMaps.swift'
note: filenames are used to distinguish private declarations with the same name

Could you help me to figure it out? Because I guess there is a problem with my Tuist configuration rather than Mapbox package

[danieleformichelli]

Configuration looks fine, could you please open an issue with a reproducible sample project and steps? 🙏

[evilhonda3030]

Okay, will do! Thanks

[evilhonda3030]

@danyf90 I got it. Tuist generates Bundle+{Dependency}.swift file that's why here is a conflict. Because MapBox team created the file with the same name by themselves. How can I solve it? Is there any option in order to disable generation of this files by tuist?

[evilhonda3030]

Hmmm, nope, both files created by Tuist. I guess I should just disable resourceSynthesizers as a first step

[evilhonda3030]

#3088 - i see this PR, however, I can't use this option in Config initializer...

[evilhonda3030]

Okay, in the 1st version I could disable 'disableBundleAccessors' but not now? What can I use instead?
https://github.com/wojciech-kulik/tuist/blob/c9aa1e2d546a2369e05a51ff9462b10c90d29f2e/Sources/ProjectDescription/Config.swift

[evilhonda3030]

Found this option in project initializer. But Tuist still generate bundle accessors for dependencies and it's leads to an compile error. I will open an issue

[pepicrft]

We've moved discussions to a community forum outside of GitHub. If this conversation is still relevant, feel free to reopen it there.