Package name conflict

[wsantos24s]

The package name "ios_sdk" is way too generic, and we can't implement it as we already have a dependency with the same name.
Could you update the package name to include the name of your product and prevent conflicts ?

[username0x0a]

In that case, I'd rather recommend creating another repository (let's say Riskified/riskified-ios-sdk) & only keep specs files there, moving xcframework from the repository to the Releases as zip attachment 👌 that can be used in the Package.swift/.podspec as a binary reference (the URL is predictable, it's quite common) as well as downloaded directly (Facebook or Firebase provide zips with releases, too). The benefit would be waaay faster checkout (& less devs' storage occupied) as we wouldn't need to fetch all historical xcframeworks with the repository when Xcode checks out Swift packages.

[SudhirKaushik]

Hello.. any consideration on this issue?