Post

Replies

Boosts

Views

Activity

Reply to Not able to use UITabBarControllerDelegate.tabBarController(:didSelectTab:previousTab:)
You just need to change one or both of those parameter names in your code. The argument labels (didSelectTab and previousTab) are part of the method signature and need to match the protocol declaration, but the parameter names can be whatever you want. I’d recommend this: func tabBarController( _ tabBarController: UITabBarController, didSelectTab selectedTab: UITab, // better parameter name previousTab: UITab? // no custom parameter name needed ) (Or you can omit tabBarController and selectedTab entirely if you don’t actually use them in your code.) Also consider entering a Feedback to report that the method declaration in the SDK is poorly formed. Presumably your error came after letting Xcode auto-generate the method for you based on its declaration. So it would be better if the SDK declaration were formed like my proposal above.
Topic: UI Frameworks SubTopic: UIKit Tags:
Jul ’24
Reply to Incorrect JSON Format with JSONEncoder
AccountCreationData(name: "name", email: "email", phone: "phone", password: "password") 110 bytes Something is off. Testing here, if I encode your struct with those exact values, the result is 69 bytes, not 110 bytes. Can you print out a string representation of the encoded JSON? And separately, do you need to set a Content-Type: application/json header so your server knows that the body format is JSON?
Topic: App & System Services SubTopic: General Tags:
Jul ’24
Reply to iOS 18 open settings URLs
Apple probably doesn't consider this a bug but I filed FB14378568 anyway. Did you frame it as a bug report, or as a feature suggestion? It’s definitely not a bug, since of course an “undocumented API” is no API at all. But lots of developers probably would concur with a suggestion to add proper APIs for these examples and others. You could call for others to submit their own suggestion feedback and reference your FB number.
Jul ’24
Reply to Will FlatBuffers API be made available?
btw, why make such a big deal about FlatBuffers in the session video if its strictly an internal implementation detail? I suspect the motivation is found in the transcript here: If you are using the Swift API, this optimization comes for free. While if you use the REST API, it is optional, and you can activate it by specifying an accept header. And here: If you are using the REST API, please consider taking advantage of the new FlatBuffer response. So they are telling REST API users to go grab FlatBuffers from GitHub for whatever platform they are using, while the WeatherKit framework of course remains closed source and just so happens to use FlatBuffers too.
Topic: App & System Services SubTopic: General Tags:
Jun ’24
Reply to iPadOS 18 compatibility
I have one here (model A1701) and can confirm that the iPadOS 18 beta isn’t available. The Settings → General → Software Update → Beta Updates menu does now include the iPadOS 18 Developer Beta option, but it has no effect.
Topic: Community SubTopic: Apple Developers Tags:
Jun ’24