@GraphicsAndGamesEngineer Excellent, this is exactly what I have been looking for ;-) Are USD files playing animations always automatically and straight away? Nice that by the glTF export from Blender the animations would be preserved… Can I trigger these animations later programmatically after having imported them (that is, the USD file) into a SceneKit scene? Thanks ;-)

Hello, Boris, In your dataSource, did you mark your struct as…? struct dataSource: Codable, Equatable, Identifiable, Hashable { […] } Kind regards ;-)

Please file a Feedback with a feature request for this — and please post your FB[number] here in this thread afterwards. We will do the same. Once it accumulates enough, Apple will eventually do it ;-) Probably, they are already working on it and just not ready yet… Kind regards ;-)

Here we go again: https://developer.apple.com/forums/thread/664613 PS: Kind regards, please file your own FB on this issue!

Hello, again, Yes, there ARE spooky things going on in Apple's backend ;-) These Debug Symbols are now available for watchOS 7.1 (18R5561e) and working properly in Xcode Version 12.2 beta (12B5018i), e. g. on Watch Series 5. THANK YOU VERY MUCH INDEED! See you

Hello, my friends, Welcome to the club, please confer to: https://developer.apple.com/forums/thread/656601?login=true&page=1#638455022 No, it is not you, forget about this. Apple needs to do their homework, that is all. PLEASE MAKE SHURE TO ONlY USE THE LATEST AVAILABLE XCODE (BETA) VERSION At this moment, Xcode Version 12.2 beta (12B5018i) See you ;-)

Here we go again… As always, Debug Symbols are missing for watchOS 7.1 (18R5561e) Try to spoof the missing directory in you Library. See you ;-) PS: Yes, I am fed up, thank you.

Hello, Gualtier, Could you please confirm whether this would also be working with "normal" AirPods? As mentioned in this thread, it is working properly by now for AirPods Pro: https://developer.apple.com/forums/thread/650051 Since my 2nd generation AirPods and AirPods Pro are having the same firmware versions, is there any hardware missing which will prevent them from working with this API? Thank you very much.

Confirmation, you got it right! Working properly under… macOS Big Sur Version 11.0 Beta (20A5374g), Xcode Version 12.2 beta (12B5018i) for Watch Series 5: 'Library > Developer > Xcode > watchOS DeviceSupport > Watch5,2 7.1 (18R5552f)' Thank you Cupertino, you made my day ;-)

Hello, Cupertino, I AM VERY UNHAPPY ABOUT THIS! Sorry, guys, again? Please confer to my FB8662319. Workaround for the time being: In your Library, make a copy of the last Debug Symbols directory (if you are lucky and have got one), rename it to the missing Debug Symbols version (e. g. Library > Developer > Xcode > watchOS DeviceSupport > Watch5,2 7.0 (18R5382a), depending on your Watch model). Good Luck

Hello, myself, Just in case, I double information concerning this issue here: The watchOS 7.0 Beta (18R5350e) Debug Symbols just came in several minutes ago! Everything compiling and working now on-device (!) as expected. Kind regards

YES!!! Whoever this was, I owe you a buck of beer. Thank you very much indeed ;-) The watchOS 7.0 Beta (18R5350e) Debug Symbols just came in several minutes ago! Everything compiling and working now on-device (!) as expected. Kind regards

Hi, since Xcode 12 Beta 4 is already out, normally, I would recommend to only use this latest version. But since there are difficulties with Debug Symbols for watchOS 7.0 Beta not being installed, you are lucky that you even have Xcode console information working in debug development at all. Hope for the best and the next watchOS 7.0 Beta release which should be out in the very next future. Oh, of course, you could delete the DerivedData directory in the Library (which will be recreated) and delete your development targets in Xcode under Product > Manage Schemes — and auto-create new ones there. Good luck. Kind regards.

FB8275455 Welcome to the club! My saying since watchOS 6.2.8 Beta… THIS IS DRIVING ME NUTS!!! Hoping for the next Beta release. Forget about trying anything, your credentials and developer account are perfectly intact. This issue is well known and has happened already years before… Apple, PLEASE fix this rubbish now and forever. Kind regards.

Hello, If Apple were already good at naming the Developer version, why should they change anything for the public one ;-) https://developer.apple.com/forums/thread/650784 Kind regards ;-)