Updated Apple Developer Program License Agreement now available
<p>The Apple Developer Program License Agreement has been revised to support updated policies and to provide clarification. Please review the changes below and <a href="https://developer.apple.com/account">sign in to your account</a> to accept the updated terms.</p><ul> <li>Section 3.3.1(B): Updated requirements related to interpreted code</li> <li>Definitions, Section 3.3.3(F): Specified requirements for use of the Location Push Service Extension</li> <li>Section 3.3.8(A), Attachment 4: Added links to terms for Xcode Cloud and CloudKit related to Regulation (EU) 2023/2854 (EU Data Act)</li> <li>Section 3.3.9(D): Updated terms regarding the entity that distributes the Tap to Pay APIs</li> <li>Schedule 1, Exhibit C: Updated Section 1 definition for Promo Codes</li> <li>Schedule 2, Section 3
October 8, 2025
The Apple Developer Program License Agreement has been revised to support updated policies and to provide clarification. Please review the changes below and sign in to your account to accept the updated terms.
-
Section 3.3.1(B): Updated requirements related to interpreted code
-
Definitions, Section 3.3.3(F): Specified requirements for use of the Location Push Service Extension
-
Section 3.3.8(A), Attachment 4: Added links to terms for Xcode Cloud and CloudKit related to Regulation (EU) 2023/2854 (EU Data Act)
-
Section 3.3.9(D): Updated terms regarding the entity that distributes the Tap to Pay APIs
-
Schedule 1, Exhibit C: Updated Section 1 definition for Promo Codes
-
Schedule 2, Section 3.13: Updated references to Offer Codes
-
Schedule 2, Section 3.13(b): Updated availability terms for Offer Codes
Translations of the updated agreement will be available on the Apple Developer website within one month.
Sign in to highlight and annotate this article
Conversation starters
Daily AI Digest
Get the top 5 AI stories delivered to your inbox every morning.
More about
availableupdateservice
![trunk/d52b2f548aa3cfcfcd499fcba764fccf29628de6: [inductor] Enable precompiled headers in fbcode (#178870) (#178870)](https://avatars.githubusercontent.com/u/3659962?s=60&v=4)
trunk/d52b2f548aa3cfcfcd499fcba764fccf29628de6: [inductor] Enable precompiled headers in fbcode (#178870) (#178870)
<p>Summary:</p> <p>Enable cpp_cache_precompile_headers for fbcode</p> <p>Authored with Claude.</p> <p>Test Plan: CI</p> <p>Reviewed By: IvanKobzarev</p> <p>Differential Revision: D98767213</p> <p>Pull Request resolved: <a class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="4179300248" data-permission-text="Title is private" data-url="https://github.com/pytorch/pytorch/issues/178870" data-hovercard-type="pull_request" data-hovercard-url="/pytorch/pytorch/pull/178870/hovercard" href="https://github.com/pytorch/pytorch/pull/178870">#178870</a><br> Approved by: <a href="https://github.com/IvanKobzarev">https://github.com/IvanKobzarev</a></p>
Knowledge Map
Connected Articles — Knowledge Graph
This article is connected to other articles through shared AI topics and tags.
More in Releases
ciflow/torchtitan/178947: Update on "add API to check if a tensor is symm-mem-tensor"
<p>In Helion autotuner, we need clone a input symm memory tensor properly if the kernel inplace update it. That requires us to know if a tensor is a symm memory tensor. Right now I call rendezvous for the tensor. If no exception is thrown, then it's a symm memory tensor. But it's not ideal</p> <ol> <li>there will be a lot of warnings complaining calling rendezvous on non-symm memory tensor</li> <li>I'll need to pass in the process group name to this API. But fundamentally check if a tensor is a symmetric memory tensor does not require the process group name.</li> </ol> <p>[ghstack-poisoned]</p>
Discussion
Sign in to join the discussion
No comments yet — be the first to share your thoughts!