Post not yet marked as solved
Preparing an iPad App for native MacOS experience using Mac Catalyst (and AppKit when needed) and using SwiftUI.
We observe that Horizontal Scroll is tricky using a Mouse! Most users have the habit of click+drag to scroll horizontally. This does not seem to be default behavior on ScrollView.
Strange: Same App when compiled on "Mac (Designed for iPad)" [aka Silicon only] scrolls horizontally with click drag. But not if compiled with Mac Catalyst.
Question: How can we enable general click-drag for horizontal scrolling using SwiftUI on Mac Catalyst? I wouldn't mind using specific AppKit framework if needed.
Thanks in advance.
Post not yet marked as solved
Xcode 14.0 introduced a work-around for a problem introduced in Swift 5.7 by setting the OTHER_SWIFT_FLAGS build option in Xcode to -Xfrontend -warn-redundant-requirements. (92092635)
The compiler crash and discussions are on the Swift GitHub Issues and pending resolution since.
The above workaround/flag is no longer available when upgrading to Xcode 14.3 (14.2 is fine) and projects using that flag simply fail.
Any hints?
Since updating to Xcode 13.3 (13E113), out WatchKit target fails to build in the ValidateEmbeddedBinary step with the error message: “error: The value of CFBundleShortVersionString in your WatchKit app’s Info.plist (X.Y.Z) does not match the value in your companion app’s Info.plist ((null)). These values are required to match.”
All info.plists look perfectly fine! This is only happening since 13.3.
The Release Note of 13.3 mentions this bug as fixed: https://developer.apple.com/documentation/xcode-release-notes/xcode-13_3-release-notes 🤷🏻♂️
Any one has come across this?!
Post not yet marked as solved
For an App in the PlaybackAndRecording Category, would entering a Group Activity Session change the Category and Mode since FaceTime is ongoing?
will we still have access to Microphone locally using, e.g. AVAudioEngine?
if yes, will the presence of FaceTime force VoiceChat mode and VPIO in our session?
Thanks in advance.
Post not yet marked as solved
When trying to access a kAudioOutputUnitProperty_OSWorkgroup the compiler errors by indicating:
'kAudioOutputUnitPropertyOSWorkgroup' is unavailable in Swift: Swift is not supported for use with audio realtime threads This makes total sense! But I'm just fetching a property here... . I am not_ in real-time thread! In the world of Mix-N-Match (between C, ObjC++ and Swift) we should be able to fetch a property like this when we're not in a critical block.
Or am I missing something here?!
Post not yet marked as solved
I am trying to use PKToolPicker (from PencilKit) without a PKCanvasView by adopting PKToolPickerObserver in my own class.
I am wondering how to deal with the FirstResponder required by PKToolPicker visibility set from a SwiftUI App when the view containing the PKToolPicker is a UIViewRepresentable embedded in a SwiftUI View that has control of gestures.
Thanks in advance,
Arshia
Post not yet marked as solved
Just saw the Audio Workgroup WWDC20 video. Thanks for bringing this up as it reduces uncertainty for most real-time audio Apps.
I am wondering about the availability of Workgroups. The speaker mentions Fall 2020. Is this already part of iOS 14? Is this only iOS 14+ feature or is there backward compatibility?
thanks in advance,
Arshia Cont
The following simplified code compiles but fails at runtime (crash!) "precondition failure: attribute failed to set an initial value: X" error.Doing some tests, it seems that SwiftUI ForEach does not like the "id:\.self" as would be the common way of using a simple Array on ForEach?I know that it is easy and convenient to comply the content of Array to identifiable but there are cases (such as using CaseIterable) where just using id:\.self would be the way to go:@State var Value: Float = 0.0
private var baseChoices: [Float] = [436, 437, 438, 439, 440, 441, 442, 443, 444] // declared at the beginning of view Struct
/// inside the body:
HStack {
Picker(selection: $Value,
label: Text("watchos.tuner.base").bold().modifier(PickerLabel()) ) {
ForEach(baseChoices, id: \.self) { val in
Text("\(Int(val))").minimumScaleFactor(0.5)
}
}
}Note that this works totally fine on WatchOS 6 and any non-beta but systematically leading to Crash on all available betas as of today.This seems to be the case with all uses of "id" on ForEach.
XCode 11.1 GM Seed (11A1027) does not seem have the right SDK for the WatchOS 6.1 beta (17S5054e) and the device with this WatchOS is marked as unavailable for development.Anyone?
Appe invited developers no less than 2 days ago to submit WatchOS 6 Apps: https://developer.apple.com/news/?id=09112019aThis includes the very promiss of Independent Watch Apps.As the deadline approaches, I can't seem to fin how to submit an independent Watch App. All documentations refer to the old companion Apps. Nothing signals (yet?) independent watch App availability on AppStoreConnect and we have no clue on how to prepare the submission (new App Identifier, New Product Page? New Certificates... ?)Anyone?
arshiacont.