“We are unable to process your request”

I'm developing a watchOS nap app that detects when the user falls asleep by monitoring heart rate changes. == Technical Implementation == HKWorkoutSession (.mindAndBody) for background execution HKAnchoredObjectQuery for real-time heart rate data CoreMotion for movement detection == Battery Considerations == Heart rate monitoring ONLY active when user explicitly starts a session Monitoring continues until user is awakened OR 60-minute limit is reached If no sleep detected within 60 minutes, session auto-ends (user may have abandoned or forgotten to stop) App displays clear UI indicating monitoring is active Typical session: 15-30 minutes, keeping battery usage minimal == The Problem == HKWorkoutSession affects Activity Rings during the session. Users receive Exercise goal reached notifications while resting — confusing. == What I've Tried == Not using HKLiveWorkoutBuilder → Activity Rings still affected Using builder but not calling finishWorkout() (per https://developer.apple.com/forums/thread/780220) → Acti

Hello everyone, We've encountered a blocking issue while integrating Apple Pay on the Web within a Salesforce Commerce Cloud (SFCC) environment. The session fails immediately after a successful user authentication. Problem Summary: After a user authenticates a payment with Touch ID or Face ID, the Apple Pay sheet showing error Payment not completed message. The core of the issue is that the onpaymentauthorized event handler is never invoked in our client-side JavaScript. As a result, the corresponding server-side SFCC paymentAuthorized hooks are never triggered, and we cannot obtain a payment token to complete the transaction. Also, No console logs are observed. Observed Flow of Events: The ApplePaySession proceeds correctly through the initial callbacks. We have verified through server-side logs that the corresponding SFCC platform hooks (getRequest, prepareBasket, shippingContactSelected, shippingMethodSelected) fire and complete successfully. The payment sheet correctly updates with shipping costs and the

Hello, I’m posting here because I’m experiencing a very unusual issue with the App Store review process and haven’t been able to resolve it through normal support channels. Our app has been waiting in App Review for over 6 weeks, which is far beyond the normal review timeframe. During this period, I contacted Apple Developer Support multiple times and even submitted an expedited review request, but the situation has not progressed. Some of my inquiries have unfortunately received no response, and the app remains stuck in review without any explanation. This delay is now causing serious operational and financial impact for our small development business. We had updates and marketing plans scheduled around this release, but the prolonged review status is preventing us from moving forward. I fully understand that review times can vary, but a 6+ week delay without any status update or communication seems highly abnormal. If any Apple staff or experienced developers have encountered a similar sit

Hello, I’m dealing with an update that has been stuck in “Waiting for Review” for weeks with no progress and no meaningful response from Apple. App details: App Name: Dólar Argentina Apple ID: 6758462259 Bundle ID: com.rgioia.dolarargentina Version: 1.3.0 (update) Timeline: First submission: February 19 → stuck in Waiting for Review I canceled and resubmitted: February 28 Since then → still stuck with zero movement This is almost a month with no review activity. What I already did: Requested expedited review → approved Contacted Apple Developer Support multiple times Followed up several times The only response I got was that the expedited review was accepted, but nothing happened after that. Impact: The app is already live, this is just an update I cannot release fixes or improvements Same version was approved on Google Play in ~20 minutes No rejection, no feedback, no communication At this point, this is not just a delay — it’s a complete lack of review and support. Questions: Is anyone else experie