missing package product

Thanks for the replay @DTS Engineer. You are right on my requirement, currently I am looking for iOS but I would be happy with a solution that works across apple platforms as well. If so, to what end? To answer your query on why I want to detect debug build I won't be able to share my exact use-case but I will share a parallel use-case that currently Apple uses: Currently Apple allows developers to send push notifications to iOS with APNS. From what I understand, APNS exposes sandbox and production environments which are controlled with aps-environment entitlement. Since, Apple controls the tooling side of iOS development, they can inject entitlement based on the provisioning profile. I want to achieve something similar to this where the REST API domain used by my framework is decided based on either provisioning profile or build type. A lot of the time it’s not the build configuration that matters, it’s the way that the app was signed. Or the way that’s it’s run (from Xcode or like a user would).

[quote='807744021, HarimaSun, /thread/807744, /profile/HarimaSun'] Does this mean ODR will be deprecated? [/quote] Yes. We said that explicitly in WWDC 2025 Session 325 Discover Apple-Hosted Background Assets. [quote='807744021, HarimaSun, /thread/807744, /profile/HarimaSun'] If so, when will it officially take effect? [/quote] AFAIK there’s no announced timeline. However, the message seems pretty clear to me: It wouldn’t be wise to use ODR in a new product. Note that the above-mentioned WWDC session also introduced Apple-host background assets, which covers much the same territory as ODR. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

Hi @changFei, You wrote: After the app transfer: If a user logs in via an existing pre-transfer version of the app (published under Team A before transfer), will the Apple Sign-In token’s sub (or private email) switch to new value tie to Team B, or unchanged? The user ID and private email address will remain unchanged—the value associated with Team A will continue to be provided. After the 60-day transfer period, Sign in with Apple will fail until they update the app (now associated only with Team B). Then, you wrote: Since our app-transfer is an internal transfer (no change in app ownership outside our organization), is there a way to retain the original sub value（or private email） for users after the transfer? Please follow the steps outlined in the post below and reply here with your Feedback ID so we can discuss a potential solution for your organization: Gathering required information for troubleshooting Sign in with Apple user migration https://developer.apple.com/forums/thread/762829 Lastly, you wrote:

Also I lose the ability to set the itemIdentifier property on subitems when creating the NSToolbarItemGroup with the class constructor. Presumably the subitem is still the sender when NSToolbarItem invokes its action? Being able to define itemIdentifier on subitem can sometimes be useful. I guess I can use tag instead but feels like a lot of busy work here. Err