For anyone coming across this in Xcode 13.3 (13E113): Apparently starting this version one must use the MARKETING_VERSION and CURRENT_PROJECT_VERSION build settings in the companion app target, and avoid using the Info.plist for that purpose. Doing this solved the problem on our side.
Thanks to Apple FB Engineers for swift response.
Post not yet marked as solved
Same problem here.
First build is fine.
Starting second build we get crash reports (see attachment) on XCBBuildService. After that, we get weird "Cycling Dependency" compiler errors (on dependencies that do not depend on each other). Cleaning the project makes it work but things re-start after the first build!
Problem only since 13.3. 13.2.1 is totally fine.
XCBBuildService-2022-03-18-180159.txt
For people coming to this thread from the Web: The accepted answer does not resolve the issue! The PRPreviewViewController is apparently Full Screen and one should just change the modalPresentationStyle to .overFullScreen to see the result fit on iPhones.
Post not yet marked as solved
When connecting to an "AirPlay 2", you loose audio Input as the corresponding AVAudioSession is incompatible with Recording/PlayAndRecord categories; at least in the AVAudioEngine context.
This is what we are experiencing at least when AirPlay 2 is getting connected. We have submitted Feedback FB8996889 to Apple on this issue after discussions during WWDC.
But some Apps seem to go around this by using low-level CoreAudio AUnits. Any feedback on this would be very welcome!
Post not yet marked as solved
Has anyone achieved weak linking with PencilKit? It seems like we have to switch back to ObjC on this... Just wondering before undertaking the migration of concerned class!
Post not yet marked as solved
Thanks! Have any idea if joining threads as such would be backward compatible let’s say iOS 12,13 underneath?
Post not yet marked as solved
Hi Chris,Did you figure out anything on this issue? We see the same problem! Universal Links work perfectly. Keychain is fine but for some strange reason the "Strong password" is not being proposed anymore since iOS 13 despite all the code updates etc by the book.
For info: This is now fixed in WatchOS 6.1 beta 4 - build 17S5076a (whose release note is empty BTW).
Post not yet marked as solved
I confirm that the problem persists! I suggest to everyone to file a Feedback.. I was told by our Dev Relations that it'll just push the issue to high priority. Mine is FB7340990
Post not yet marked as solved
From my experience, you can't do this yet as of XCode 11.1 GM and WatchOS 6 in SwiftUI!But we see in a WWDC'19 video that they are doing it on a sample project which I hope (as they say) will be published soon.
Thank you Nik!Did you create an independent App Identifier for this? And did you then create a dedicated "iOS App" on the AppStoreConnect?
We are all in the same boat I believe! Apple just released XCode GM Seed 2 a few hours ago. My guess is that things should start moving in a day or two! Let's wait and see... .BTW, in case you're using SwiftUI, how do you come around the `.onDisappear(perform:)` not working using NavigationLinks?!
Post not yet marked as solved
@zvba : You can't have a voiceprocessing audiounit with remoteIO. One major reason is that VPIO requires specific AVAudioSession Category/Modes which are not the ones you can use with remoteIO. I had the chance to talk with CoreAudio developpers on this at WWDC. This won't get any better with the new AVAudioEngine support for VPIO (which I think uses the good old APIs under the hood).A nice solution would be to have enough controls over VPIO to get what we want. All this, for an undetermined future... .
