Posts

Post not yet marked as solved
2 Replies
Here's the answer I received from Apple DTS. As for attribution, there is a REST API call for attribution, though looking at the documentation, I see it is not listed. I've already filed a request to have that added (r. 102144735). I encourage you to file your own feedback about this; feel free to reference the bug I filed when you do so. https://feedbackassistant.apple.com. The call is  https://weatherkit.apple.com/attribution/{locale} which returns JSON, with the attribution images and localized name for WeatherKit in that locale. For example https://weatherkit.apple.com/attribution/en-US returns  {     "logoDark@3x": "/assets/branding/en/Apple_Weather_wht_en_3X_090122.png",     "logoLight@1x": "/assets/branding/en/Apple_Weather_blk_en_1X_090122.png",     "logoDark@2x": "/assets/branding/en/Apple_Weather_wht_en_2X_090122.png",     "logoDark@1x": "/assets/branding/en/Apple_Weather_wht_en_1X_090122.png",     "logoLight@2x": "/assets/branding/en/Apple_Weather_blk_en_2X_090122.png",     "logoLight@3x": "/assets/branding/en/Apple_Weather_blk_en_3X_090122.png",     "logoSquare@2x": "/assets/branding/square-mark@2x.png",     "serviceName": "\uf8ff Weather",     "logoSquare@1x": "/assets/branding/square-mark.png",     "logoSquare@3x": "/assets/branding/square-mark@3x.png" }
Post not yet marked as solved
1 Replies
File > New > Editor Below
Post marked as solved
17 Replies
I don't claim to know what all the XML means but the change happens in my watch app schemes when I switch the selected device between the simulator and a real watch. When I select the simulator, BuildableProductRunnable is in effect but when I select a real watch, RemoteRunnable is in effect. It's almost as if the scheme has to change to allow remote debugging when using a real watch. So the state of the scheme files depends on the device selected when you last built in Xcode.
Post not yet marked as solved
3 Replies
I'm trying to figure out a good way to provide sessions between my app and my appserver since Sign In with Apple won't provide them the way every other services (Google, Facebook , Twitter, AWS Cognito, etc) do. At first I thought I might need my own OAuth 2.0 server but the simplest thing I can think of to do is have my app server create and return new JWTs to my app. When the user signs in with Apple, I send the identity token to my app server, verify the identity token with Apple, then create JWTs (identity/access and refresh) and return them along with the expiration back to my app.