Does anyone know if alternate app icons are actually supposed to work for Apple TV projects? We tried to set this up, and while it works in Debug, we run into validation errors when uploading the app to App Store Connect. Is this feature officially supported on tvOS, or is it iOS-only?
Search results for
Building for iOS Simulator, but the linked and embedded framework ‘XX.framework‘ was built for
186,306 results found
Selecting any option will automatically load the page
Post
Replies
Boosts
Views
Activity
Hello, I am one of the developers of Scaniverse and we are looking to push a significant update of the app by the Feb 20th. We have been in review for the past 2 days and are concerned that we won't have our app approved before our launch deadline. Our company is coordinating a launch across multiple applications with marketing to coincide with an event and it is very important that we be able to deliver this app. Is there anyway someone can look at this or someone I can reach out to expedite this? We uploaded a prior build several weeks ago and approval was much quicker, so this caught us off guard.
Topic:
App Store Distribution & Marketing
SubTopic:
App Review
Albert, thanks for the reply. Remote hosted Live Activities I believe is a iOS 26.x system feature → No developer adoption. My steps: Preparation: Make sure iPhone and Mac (and/or Watch) are signed in with the same AppleID New iOS Project New Widget target, using standard template (In the new target UI also check that you want the live activity) Build and run to a physical iPhone Notice Live Activity exists on iPhone, Mac and Apple Watch [Example: From macOS, iOS Live Activity appears] In this case, I haven't built for any other platforms at all. I believe this is a feature, but I'm attempting to understand what I need to do to make it stop showing up in places that don't make sense for this app. Just made a simple project using the Xcode templates provided, then start the live activity on app launch. https://github.com/ioloro/LiveActivityWillTravel Thanks, John Marc
Topic:
App & System Services
SubTopic:
Widgets & Live Activities
Tags:
Problem After launching the host app by tapping the widget (widgetURL), calls to: WidgetCenter.shared.reloadAllTimelines() WidgetCenter.shared.reloadTimelines(ofKind: ...) are ignored/deferred for an initial period right after the app opens. During this window, the widget does not reload its timeline and remains unupdated, no matter how many times I call the reload methods. After some time passes (typically ~30 seconds, sometimes shorter/longer), reload calls start working again. There is also no developer-visible signal (no callback/error/acknowledgement) that the reload was ignored, so the app can’t detect the failure and can’t reliably recover the flow. Question: Is this expected behavior (throttling/cooldown) after opening the app from a widget ? If so, is there any recommended workaround to update the widget reliably and quickly (or at least detect that the reload was not accepted)? Any guidance would help.
Your enrollment could not be completed. Your enrollment in the Apple Developer Program could not be completed at this time. I know a lot here are also experiencing this slow and seemingly ignorance from the Apple team to solve this problem or of related issue. As a new guy to the Apple ecosystem and in development world, i thought it'll be a breeze but oh my pickle! I thought I'd lose my mind! Tried through the website, on my mac and phone but nothing seems working. Paying online using my card is fine, but when it comes to paying the enrollment I don't get why I am having an (1) authorization issue , other case using another method prohibits me due to (2) no availability in my region, or that a (3)disabled Enroll Now list item via Developer App on iOS devices. Support though mail is nonexistent and when in a call, albeit the support staff is polite, the responses I got are pretty vague and with no certainty ---- making me paranoid. Don't they see the time costing developers waiting for this simple st
Topic:
Developer Tools & Services
SubTopic:
Apple Developer Program
Hello, Same for me, I've published my app for review on the 4th of February 2026. It has been on Waiting for review since that day. We are on the 18th of February 2026 and my app still didn't get verified. I've been trying to contact support two times and I also did ask for an accelerated review but didn't get any response. That's really sad knowing I had a big advantage of timing by having the idea and building it early, and I am now seeing new competitors building the same app...
Topic:
App Store Distribution & Marketing
SubTopic:
App Review
Hello, My app Kevser (iOS 2.0.0) has been in Waiting for Review since February 11, 2026, with no status change. It is a lifestyle and community app already live on Google Play with active users. The iOS version is fully functional and ready for release. The timing is important because our app serves a seasonal audience in Turkey, and the key season starts tomorrow. Every day of delay matters significantly for our launch window. I have opened 5 support cases so far (including Case ID: 102821061223). Only one was responded to, and the reply simply said to be patient and wait for my turn in the queue. I also have a few minor revisions I would like to make, but I am afraid to submit a new build because it would reset my position in the queue and push me to the back of the line. The length of this wait is preventing me from making any improvements. Has anyone experienced a similar situation recently? Any advice would be appreciated.
Hello everyone, I’m looking for more detailed information regarding UVC (USB Video Class) over MFi within the Apple ecosystem and would appreciate some clarification. I’m interested in developing (or interfacing with) an accessory that transmits video over USB using the UVC standard, and I’d like to better understand how this works within the MFi (Made for iPhone) program. Here are my main questions: 1. Do iOS devices provide native support for UVC over USB-C or Lightning within the MFi framework? 2. Are there any specific firmware or authentication requirements when the accessory is MFi-certified? 3. Does UVC support depend solely on the hardware interface (USB-C vs Lightning), or are there additional software-level requirements? 4. Is there any official documentation outlining the recommended flow for implementing UVC-based video capture accessories on iOS? From what I understand, USB-C iPads appear to offer more direct support for standard UVC devices, but it’s not entirely clear
Hmmm, that’s not good. While I don’t want to engage in ‘blame the victim’ here, there is something you can do to reduce the risk of problems like this occurring in the future, namely, testing with beta seeds as they’re released. The beta seed programme exists to help us find and fixing regressions like this. Anyway, let’s see if we can find you a workaround. If you add this to your app’s entitlement, does it prevent the failure: A key of com.apple.security.temporary-exception.mach-lookup.global-name With the value being an array With a single string element Whose value is com.apple.storagekitd If that works, we can then talk about the App Review implications |-: Note Temporary exception entitlements have an interesting history. I have a couple of links in App Sandbox Resources that explain more about them. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com
Topic:
App & System Services
SubTopic:
Core OS
Tags:
I am developing a mobile application using Flutter and plan to implement in-app subscriptions for both iOS platforms. I would like to request guidance on the following: Technical Implementation: Recommended best practices for implementing auto-renewable subscriptions in Flutter apps StoreKit 2 integration requirements and compatibility considerations Server-to-server notification setup and endpoint requirements Testing Procedures: Sandbox environment configuration and testing workflow TestFlight testing requirements for subscription features Recommended testing scenarios before production release Required Documentation and Accounts: Complete list of required agreements (Paid Applications Agreement, etc.) Banking and tax information requirements Privacy policy and terms of service specifications for subscription apps App Review guidelines specific to subscription-based apps Subscription Management: Grace period implementation requirements Handling subscription cancellations and refunds Promotional off
You can find your answer on the submission form. You select your runtime environment using a popup, and below that popup is this text: Xcode app playgrounds are run in Simulator. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com
Topic:
Community
SubTopic:
Swift Student Challenge
Tags:
First up, I want to be clear about terminology. You don’t sign code with a certificate, you sign it with a digital identity, that is, the combination of a certificate and its associated private key. There’s no need to protect the certificate; it’s the private key that matters. I talk more about this in TN3161 Inside Code Signing: Certificates. Second, the Secure Enclave (SE) doesn’t store private keys. Rather, you protect a private key with the SE. The SE generates the private key and returns it wrapped in a way so that only that SE can use it. You then send key operations, like ‘sign this blob with this wrapped key’, to the SE, it internally unwraps the key, does the operation, and returns you the result. So the unwrapped key material never leaves the SE, but it’s not stored in the SE. Note This is how the SE works but it’s not true for other hardware-based keys. Notably, with a smart card the private key is actually stored on the smart card itself. Folks using the smart card don’t work with a wrapped key, t
Topic:
Code Signing
SubTopic:
Certificates, Identifiers & Profiles
Tags:
Hello everyone, Our app was recently rejected under Guideline 5.0 – Legal (U.S. Sanctions Compliance). Apple review reported that the binary contains the following domain: https://lib.eshia.ir However, after extensive investigation: • The app does NOT connect to this domain • The app does NOT provide services to sanctioned regions • The domain does NOT exist in our source code, API calls, or UI • Network logs confirm no outgoing requests to this host We suspect the reference is coming from a bundled third-party dependency dataset (possibly a public suffix / domain validation / fraud detection list embedded in a framework). We already: Extracted IPA Scanned all source files Ran strings on the main binary Checked networking layer But we still cannot identify which framework contains this entry. Questions: Has anyone faced a sanctions rejection due to a domain inside a compiled SDK dataset? Is Apple expecting removal of the exact string from the binary even if unused? How do you typica
Hello everyone, Our app was recently rejected under Guideline 5.0 – Legal (U.S. Sanctions Compliance). Apple review reported that the binary contains the following domain: https://lib.eshia.ir However, after extensive investigation: • The app does NOT connect to this domain • The app does NOT provide services to sanctioned regions • The domain does NOT exist in our source code, API calls, or UI • Network logs confirm no outgoing requests to this host We suspect the reference is coming from a bundled third-party dependency dataset (possibly a public suffix / domain validation / fraud detection list embedded in a framework). We already: Extracted IPA Scanned all source files Ran strings on the main binary Checked networking layer But we still cannot identify which framework contains this entry. Questions: Has anyone faced a sanctions rejection due to a domain inside a compiled SDK dataset? Is Apple expecting removal of the exact string from the binary even if unused? How do you typica
With agentic coding and AI rapidly improving at solving development problems, I’m starting to question what the next three to five years will look like for iOS developers and whether manual coding will gradually disappear. I’ve been building iOS apps full time since 2013 and while I appreciate AI for speeding up workflows like unit testing, I worry that over reliance could weaken our core skills, reduce our understanding of evolving APIs, and ultimately impact our long term value and demand in the industry, does anyone else feel the same?
Topic:
App Store Distribution & Marketing
SubTopic:
App Store Connect
Tags:
App Store
App Review
App Store Connect