rive-ios
rive-ios copied to clipboard
XCode 14 Beta 5 Preview error
Can't see preview anymore, here is the error in text form:- ` HumanReadableSwiftError
SettingsError: noExecutablePath(<IDESwiftPackageStaticLibraryProductBuildable:ObjectIdentifier(0x0000600008165530):'RiveRuntime'>)
`
Seeing this as well.
I'm facing the same issue with Version 14.0 (14A309) Did anyone find a fix or a workaround for this?
Same problem. Has anyone found a solution? Xcode 14.0 (14A309)
Same on my end, even with views which are not using Rive at all
Did anyone find a fix to this?

I found a solution!
Go to your project's main file with a blue App Store logo. Go to Targets > your app > General (at the top) > scroll down to Frameworks, libraries, and embedded content > remove RiveRuntime.
I don't know why that would work but it did work for me and now my rive animations are still there plus the previews work.

The above is a great workaround!
Same issue here. The founder just replied to my tweet and suggested that we install it as an .xcframework instead of via Swift Package Manager. Apparently there is an issue with all binary frameworks with Swift Package Manager right now. Anyone know how to do this?
We did some testing around this - and believe it to be an XCode ^14.0.0 bug around SPM packages (able to repro with other non-Rive packages standalone in a new app). As @andrewbeshay25 found interestingly, if you remove it, you should be able to use RiveRuntime in previews, but it may not build if you run on a simulator. However if you keep RiveRuntime as a SPM package added (still our most recommended way to add the package), you should be able to run this on an emulator. We also did some testing and the new XCode beta (14.1) seems to have addressed this issue so you may try experimenting there to see if this resolves the issue!
closing this out as this has been resolved with later versions of XCode