@cecilia_hollins Just following up to see if you were able to package your solution. I’m confident it would be a valuable resource for visionOS developers. Thanks!
Post
Replies
Boosts
Views
Activity
I have this issue as well. Has anyone been able to figure this out?
I’m starting to suspect the issue is related to Apple IDs associated with developer accounts, as that’s the only common factor I’ve identified so far.
Apple folks: FB15345379
I see the same issue for a handful of users.
This has bitten me as well. I used .ascii to detect if a SSH key uses a passphrase or not. Thanks, I guess?
Here's an excerpt of the crash:
Unhandled coercion:
(existential_type
(protocol_composition_type
(bound_generic_class_type decl="Swift.(file).PartialKeyPath"
(struct_type decl="PartialKeyPath.(file).RemoteComputer@/Users/me/Downloads/PartialKeyPath/PartialKeyPath/ContentView.swift:74:8"))
(protocol_type decl="Swift.(file).Sendable")))
(bound_generic_class_type decl="Swift.(file).PartialKeyPath"
(struct_type decl="PartialKeyPath.(file).RemoteComputer@/Users/me/Downloads/PartialKeyPath/PartialKeyPath/ContentView.swift:74:8"))
Please submit a bug report (https://swift.org/contributing/#reporting-bugs) and include the crash backtrace.
...
1. Apple Swift version 6.0 (swiftlang-6.0.0.7.6 clang-1600.0.24.1)
2. Compiling with effective version 5.10
3. While evaluating request TypeCheckSourceFileRequest(source_file "/Users/me/Downloads/PartialKeyPath/PartialKeyPath/ContentView.swift")
4. While evaluating request TypeCheckFunctionBodyRequest(PartialKeyPath.(file).CSItemOrder.init(comparator:)@/Users/me/Downloads/PartialKeyPath/PartialKeyPath/ContentView.swift:61:5)
5. While type-checking statement at [/Users/me/Downloads/PartialKeyPath/PartialKeyPath/ContentView.swift:61:64 - line:70:5] RangeText="{
switch comparator.keyPath {
case \RemoteComputer.readableName: self.init(type: .readableName, order: comparator.order)
case \RemoteComputer.lastConnectionDate: self.init(type: .lastConnectionDate, order: comparator.order)
case \RemoteComputer.numberOfConnections: self.init(type: .numberOfConnections, order: comparator.order)
default:
print("Unsupported keyPath: \(comparator.keyPath)")
throw ItemOrderError.unsupportedKeyPath
}
"
6. While type-checking statement at [/Users/me/Downloads/PartialKeyPath/PartialKeyPath/ContentView.swift:62:9 - line:69:9] RangeText="switch comparator.keyPath {
case \RemoteComputer.readableName: self.init(type: .readableName, order: comparator.order)
case \RemoteComputer.lastConnectionDate: self.init(type: .lastConnectionDate, order: comparator.order)
case \RemoteComputer.numberOfConnections: self.init(type: .numberOfConnections, order: comparator.order)
default:
print("Unsupported keyPath: \(comparator.keyPath)")
throw ItemOrderError.unsupportedKeyPath
"
7. While type-checking expression at [/Users/me/Downloads/PartialKeyPath/PartialKeyPath/ContentView.swift:62:16 - line:62:27] RangeText="comparator."
8. While type-checking-target starting at /Users/me/Downloads/PartialKeyPath/PartialKeyPath/ContentView.swift:62:27
FB14697971
Apple folks: FB13792217
Were you ever able to find a workaround for this issue?
Actually, I think I found the issue.
After some further investigation, it seems the issue occurs when UIPointerStyle.hidden() is used:
func pointerInteraction(_ interaction: UIPointerInteraction, styleFor region: UIPointerRegion) -> UIPointerStyle? {
return UIPointerStyle.hidden()
}
Using UIPointerStyle.system() instead prevents the cursor from jumping.
Apple folks: FB13709727
Apple folks: FB13708422
It would really be nice to disable eye tracking for the hover gesture so it can behave like it does on iPadOS.
No, sorry.
Making ControlActiveState available on visionOS would solve this issue. It's only available on macOS at this time.
FB13675635
Is this ever going to get fixed? Some users are unable to make any in-app purchases on the Mac App Store! It's not just our app - we asked users running into this issue to try purchasing IAP from other apps and that fails as well.
If anyone has a workaround I'd love to know about it!
This has been fixed in the latest iPadOS 17.4 beta, BTW.