“DTiPhoneSimulatorErrorDomain Code 2”

Since a few days ago, I noticed that every time you go to the top of the text in the Agentic Coding chat box, if you keep pressing the up arrow, the current message is replaced by the previous one. It's like someone decided to allow users to use the arrows to navigate to previous conversations in the same context, but this means that you are constantly jumping to previous messages by accident. The feature is error prone, confusing, and extremely annoying. If someone knows of an option in setting to disable it, please let me know. I'm constantly making mistakes, wasting tokens, editing the wrong message, and making the conversation confusing by sending the wrong message to the agent.

forum-post-v2-evidence.log MCRestrictionsPayload (allowListedAppBundleIDs) breaks Apple Watch app enumeration — nanotimekitcompaniond reports Missing .app from directory: /Watch/ Summary Installing a Configuration Profile with com.apple.applicationaccess payload containing allowListedAppBundleIDs causes native Apple Watch apps to disappear from the paired Watch — even when their bundle IDs are explicitly in the whitelist. Log analysis shows this is not a bundle ID matching problem: nanotimekitcompaniond on the iPhone fails to enumerate the .app/Watch/ subdirectories where native watchOS app stubs live. Follow-up to https://developer.apple.com/forums/thread/745585 — community-confirmed but received no official response. Environment iPhone 16 (iPhone17,3), iOS 26.4.2 (23E261), supervised Apple Watch paired via Bridge.app Profile installed locally via Apple Configurator (no MDM server required) Smoking gun Within ~5 seconds of profile install, two processes (nanotimekitcompaniond and NTKFaceSnapshotServ

So i submitted my app what seems like a dozen times now and they keep rejecting it due to Guidelines 5.1.1(i) - Privacy - Data Collection and 5.1.2(i) - Legal - Privacy - Data. The full section is: Issue Description The app appears to share the user’s personal data with a third-party AI service but the app does not clearly explain what data is sent, identify who the data is sent to, and ask the user’s permission before sharing the data. Apps may only use, transmit, or share personal data after they meet all of the following requirements: - Disclose what data will be sent - Specify who the data is sent to - Obtain the user’s permission before sending data - Identify in the privacy policy what data the app collects, how it collects that data, all uses of that data, and confirm any third party the app shares data with provides the same or equal protection Next Steps If the app sends user data to a third-party AI service, revise the app to explain what data is sent, identify who the data is sent to, and ask the u

I submitted my paperwork on May 5 to development support to verify my organization and my signing ability for my organization and I have not heard anything back to this day. I know that these things are supposed to only take two business days. So I’ve also emailed and have not heard back. Has anybody ever had these issues before? And is there a way to contact Apple that’s not requesting a phone call I work full-time and cannot receive phone calls while I’m at work so that’s not a feasible option for me. Hopefully somebody will see this from support and respond to my emails and or submission.

My tvOS app includes the purchase of subscriptions, and I am updating the code with Storekit 2.0. I have seen other apps that present the Confirm with Apple Device UI upon selection of a product, but for me I only ever see an alert confirming the purchase. I have tested this using Xcode storekit data and a sandbox account. I have also attempted using Storekit views and passing the UIWindowScene to the purchase(confirmIn: ) parameter, but neither made any difference. Is there some limitation that prevents that UI from showing in debug builds?

I have been attempting to contact development support regarding verification of my organization in my signing ability on behalf of my organization because my account has not been. My initial filing was on May 5 for my new reference number because my first one got declined the developer portal as that it should only take two business days, but it is definitely taking a lot longer than that to verify my business. has anybody had this sort of issue before and is there a phone number to actually contact because the email process also seems to be delayed at this point in time. I work full-time and cannot receive phone calls during the day so putting in a ticket for someone to call me is not feasible. Hopefully somebody from the sports team will see this post and reach out to me and give me a way to contact Apple development support so I can get this finalized.

I've added two new users to our App Store connect account but when they follow the link in the invitation email, they're taken to a blank white page in their browser. I've had them try with an incognito browser and cleared their browsing data but have had no luck. We stopped trying for a few weeks and today, I sent a new invitation and they experienced the same issue. Can't seem to nail down why this is happening.

I'm adding live activities to my app and I'm trying to use push notifications to fully remotely start them and end them. The pushToStartTokenUpdates sequence gives start tokens exactly as expected, and triggers even when the app is fully terminated when a new live activity starts. However, the pushTokenUpdates sequence is far less predictable and seems to never trigger when the app is fully terminated. Even when the app is just backgrounded, it's still finicky. I send the input-push-token: 1 as part of the aps payload too to begin the live activity, but that seems to have little to no effect. Is there any way to ensure that we can receive a push token specifically to update the live activity after it starts? It seems to me that if a live activity can be started via push even when the app is fully terminated, and live activities are meant to reflect active information, then the mechanism to update it via a new token should also be able to work when the app is terminated. Both sequences are subscribed to within

Our application currently supports Live Activities. We’re working on adding a new Widget and are weighing some architectural decisions regarding whether we should add it to the same extension target that our Live Activity lives in or create a new extension that would expose it and other widgets we plan to create in the future. In the Add Support for Live Activities documentation, it suggests adding Live Activity code to the existing widget extension to facilitate code reuse. Beyond code sharing, we’re trying to determine if there are downsides to isolating new Widget(s) into their own extension. Specifically, we are concerned about process isolation and how a failure/crash in one might impact the other. Assuming they did live in the same extension, we’re hoping to better understand some of the finer details as presented by the following questions: If a Widget (e.g., via the TimelineProvider) causes the extension process to crash, what is the guaranteed behavior for a currently runni

Hey everyone, hoping someone here has seen this one because Apple support has basically gone silent on me at this point. Quick rundown of the situation: I submitted my app for review for the first time about 2 weeks ago, with my in app subscriptions attached to that first binary. That worked exactly like it's supposed to, subs and binary went into review together. The binary got rejected and the subs got rejected with it. Since then, every single time I create a new app version, the option to submit my subscriptions alongside it just isn't there. There's no attach subscriptions prompt anywhere in the new version's submission flow. So the only way I can actually submit the subs is on their own, straight from the Subscriptions page. And every time I do that, they come back rejected for one reason only, that they need to be submitted with a new app version. Which I literally cannot do, because that UI option doesn't appear in my ASC anymore. It worked the first time, and ever since that very first rejec