Closed jakov-clay closed 1 year ago
@SergeySeroshtan hey do you maybe have time to check this issue?
Will take a look
@SergeySeroshtan were you able to reproduce issue? any ETA for this? My watch app is blocked by this so any info or help is helpful. Thanks!
Currently have issue with building low level libraries with updated environment. Going to resolve this ASAP. ETA until Oct 24.
Hi @jakov-clay what package manager do you use?
Met the same issue as - https://developer.apple.com/forums/thread/700583
Hi @jakov-clay what package manager do you use?
Cocoa Pods
Met the same issue as - https://developer.apple.com/forums/thread/700583
My issue occurs only in Xcode 14, everything seems to work normally in Xcode 13
If I build for Any watchOS device I get a bit different error.
I'm unsure why this happens. I can test on real watch device, if I can help let me know.
Going to accomplish this issue until tomorrow.
@SergeySeroshtan how it's going? Any progress, problems, updates?
Hi @jakov-clay, I've got problems with Carthage package manager, that won't be able to fix quickly. To unblock your's progress, I've released a new version for Cocoapods - 8.2.0 with arm64 arch for watchOS, please check it.
@SergeySeroshtan I'm confirming that SDK works with latest Xcode on real devices! Thank you very much! I have some problems with my framework but Virgil is running normally.
I'm having issues when building for watchOS in Xcode 14 for real devices (simulator is fine). I get bunch of issues when linking VirgilCryptoFoundation for arm64 arch. In Xcode 13 works fine, probably related to bunch of changes Xcode 14 introduced for watchOS, now there is only 1 target instead of 2 when creating watchOS app, and new architecture.
My Podfile:
Tested also with SPM, same result.
Maybe rebuilding libraries with Xcode 14 tools would help solve this issue?