Post not yet marked as solved
And I liked this one: ”You’ve exceeded the posting limits. Please try again in a few minutes.“
This new feature might hurt you a bit, KMT ;-)
Post not yet marked as solved
And I would love to see better entry options on the Developer Forums' start page. watchOS is no interesting topic to be dealt with? Oh dear…
Post not yet marked as solved
Is this new Apple Developer Forum hand-curated by now? Twenty minutes for the approval of an answer? You are getting qicker on this, do you?
See you ;-)
Post not yet marked as solved
Hi, KMT,
Still keeping your nice record ;-)
They did a decent job on mobile devices. It looks so much better on iPad and even iPhones.
We both know that we are hanging around here for more than five years, but never mind ;-)
“Pacific Rim” region, nice…
See you ;-)
Post not yet marked as solved
My dear friend KMT, incredible that you are still around after all these years ;-) Still remember the last Developer Forum change back then turning it into something almost unusable, pushing good people to giving and searching advise on StackOverflow and elsewhere… I just hope that they did it right this time, maybe it will even work well on mobile devices…
Post not yet marked as solved
Thanks for asking. Alive and kicking. Actually, I am very keen on publishing my very first app on the App Store this year. Really? Yes, I have just been trying to get better since 2008, starting with Apple sample code “Hello World” back then… No joke. 2020 is a very good year for this now, having made the switch to Swift from Objective-c two years ago, now to SwiftUI that I love a lot. By now, Apple has invented pretty much any technology and API that I would need for my project. Excellent. Yes, I know, somewhat late to the party, but still enjoying being around here A LOT ;-) I owe “you guys of the very first hour” a lot, without people like you (and Apple engineers like Eskimo1) I would not have made it so far ;-)
Post not yet marked as solved
@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 ;-)
Post not yet marked as solved
Hello, Boris,
In your dataSource, did you mark your struct as…?
struct dataSource: Codable, Equatable, Identifiable, Hashable {
[…]
}
Kind regards ;-)
Post not yet marked as solved
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.
Post not yet marked as solved
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 ;-)
