Search results for

“testflight the requested app is not avaliable”

416,704 results found

Post

Replies

Boosts

Views

Activity

Left-flick and right-flick gestures with VoiceOver and UIAccessibilityReadingContent
Hi, I have an app that displays lines of text, that I want to make accessible with VoiceOver. It's based on a UITextView. I have implemented the UIAccessibilityReadingContent protocol, following the instructions in https://developer.apple.com/videos/play/wwdc2019/248 and now users can see the screen line by line, by moving their fingers on the screen. That works fine. However, users would also like to be able to use left-flick and right-flick to move to the previous or next line on the screen, and I haven't been able to make this work. I can see that left-flick triggers accessibilityPreviousTextNavigationElement and right-flick triggers accessibilityNextTextNavigationElement, but I don't understand what these variables should be.
1
0
642
5d
DJI DNG
DJI's DNG files display abnormally in the Apple Photos app on iOS devices, with dark areas showing as very black, but the same files appear normal in Photoshop. I'm curious about what causes this issue.
0
0
22
5d
Technical Blocker: Family Controls Entitlement for DeviceActivityMonitorExtension (Parent app already approved)
Hello, I am facing a critical technical blocker regarding the Family Controls (Screen Time API) entitlement for my app extensions. Current Situation: My parent app (com.hayashikento.FocusPact) is already approved for the Family Controls (Distribution) entitlement. However, the associated DeviceActivityMonitorExtension (com.hayashikento.FocusPact.FocusPActMonitor) and ReportExtension (com.hayashikento.FocusPact.ReportExtension) are still pending entitlement approval. Technical Issue: Because the extensions lack the Distribution entitlement, ManagedSettings and DeviceActivity triggers (like intervalWillEndWarning) are ignored by the system when testing via TestFlight or in a non-development environment. As a result, I am unable to verify the core automatic re-blocking logic and usage reporting features in a real-world scenario. This has completely halted the final QA and TestFlight phase of my project. Requests: Could an Apple engineer verify if these extension IDs c
0
0
28
5d
Reply to Understanding '.waiting' state in NWConnection.State for UDP
NWConnection is quite generic, so you shouldn’t be surprised that not all of its options make sense for all connection types [1]. However, in this case the .waiting state does make sense for UDP. Consider a connection created like this: let connection = NWConnection(to: .hostPort(host: example.com, port: 80), using: .udp) If you run this on a device with Airplane Mode enabled, the connection will enter the .waiting state. That’s because it’s waiting for DNS to come online so that it can resolve example.com to find out what addresses it should attempt to ‘connect’ to. But that’s just an example. I suspect that are a number of other cases where you’ll see this. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com [1] The new NetworkConnection API improves this situation, using the Swift type system to vary the operations supported on the connection based on the underlying protocol. However, there are limits to how much you can improve this
5d
Rejected under Guideline 1.1.1 (Objectionable Content) — car notification app, looking for advice
Hi everyone, I recently got rejected under Guideline 1.1.1 - Safety - Objectionable Content and I'm struggling to understand how my app falls under this category. Looking for advice from anyone who's dealt with similar rejections. What the app does: AutoSignal is a vehicle notification app designed for the Bulgarian market. It solves a very common real-world problem - needing to contact a car owner when their vehicle is double-parked, blocking you in, has its lights left on, or has been hit/damaged while parked. The core flow is: A user scans a license plate using their phone camera If the car owner is registered in the app, they receive an anonymous push notification (e.g., Your car with plate XX 1234 XX is blocking someone or Your lights are on) The car owner can then take action Users can also report vehicle damage cases with temporary witness notes that auto-expire after 7 days. Why I believe it doesn't violate 1.1.1: The app does not expose any person
1
0
43
5d
Reply to Sporadic crash in xzm_main_malloc_zone_init_range_groups when spawning large binaries (macOS 26.3.1)
The 3 in that error is KERN_NO_SPACE, which is a pretty clear indication that the system memory allocator asked for address space and the kernel refused to give it. However, given all the constraints you’ve described, it’s not at all clear why that would be. Weirdly, the code that traps this way is not on the main branch of the Darwin open source, but I found a copy in the rel/libmalloc-792 branch [1]. Now, I don’t have time today to study that code in depth, but I figured you’d find it interesting (-: AFAICT it tries to allocate address space by using mach_vm_map to map MEMORY_OBJECT_NULL, specifying a start that’s after 16 GiB, such that it fits within 64 GiB, with a randomly applied offset. That random bit probably explains why this shows up so infrequently. It’s hard to say why this is failing. You might be able to learn more by running vmmap against the dying process. It’d also be interested to know what address was passed to mach_vm_map (with reference to the source, that’s the ptr_add
5d
Reply to Need MetricKit Implementation details for MacOS background Application, mainly for
MetricKit definitely works on macOS. I’m not sure about how it interacts with Network Extension processes. Let’s start with some basics: Is your NE provider packaged as an app extension or a system extension? If it’s an sysex, are you distributing it directly? Or on the Mac App Store. TN3134 Network Extension provider deployment talks more about NE provider packaging and deployment options. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com
6d
AccessoryTransport Extensions not launching on iOS 26.5 beta — missing entitlements not available in provisioning
Environment Xcode 26.5 beta iOS 26.5 beta Using AccessorySetupKit + AccessoryTransportExtension framework Three extensions: AccessoryTransportAppExtension, AccessoryTransportSecurityExtension, AccessoryDataProviderExtension Background Everything worked correctly on iOS 26.4 beta. All three extensions shared the entitlement com.apple.developer.accessory-transport-extension, and the system launched them as expected. After upgrading to iOS 26.5 beta (both Xcode and device), the app compiles and runs, the accessory pairs and connects successfully (state = authorized, BLE connected, notification forwarding = allow), but none of the extensions are launched by the system. Investigation Captured system Console logs from the device and found these errors from deviceaccessd: error deviceaccessd ### Extension 'com.huami.NotificationForwardingDemo.AccessoryDataProviderExtension' is missing entitlement: com.apple.developer.accessory-data-provider for com.apple.accessory-data-provider error deviceaccessd ### Exten
1
0
59
6d
Enrollment Pending 5 Days — Paid €99, No Activation, No Support Response, 3 Open Cases Ignored
I purchased the Apple Developer Program on March 26, 2026. Payment went through immediately. I have the invoice (UA31019584), the order confirmation (W1318171870), and €99 charged to my card. Apple had no problem taking my money within seconds. Five days later: Account status: Pending Portal still says Purchase your membership and asks me to pay again App Store Connect: inaccessible TestFlight: inaccessible I contacted Apple Developer Support on day one — both by email and callback request. I now have three open cases and have received exactly zero responses: Case ID: 102856462218 — Program Purchase and Renewal Case ID: 102853916886 — Program Purchase and Renewal Case ID: 102853919455 — Program Enrolment Not a single acknowledgment. Not even an automated we're looking into it. Nothing. My app is built and ready. I have testers waiting. I cannot distribute anything — not even through TestFlight — because Apple took my pay
0
0
38
6d
Unexpected appAccountToken mutation in JWSRenewalInfo during in-app crossgrade
Hello Apple Developer Support / StoreKit Team, We recently observed a behavior regarding the appAccountToken in App Store Server Notifications v2 that seems to completely contradict the official documentation. According to the Set App Account Token documentation: The same appAccountToken continues to apply to renewal transactions if the customer upgrades, downgrades, or cross-grades the subscription. However, we encountered a scenario where an active in-app crossgrade resulted in an updated/overwritten appAccountToken inside the subsequent JWSRenewalInfoDecodedPayload, despite our backend never calling the Set App Account Token REST API. Our Observation: A user subscribes to our 1-month plan (Product A). Apple generates an originalTransactionId bound to their initial appAccountToken (Token A). Later, a crossgrade to a 1-year plan (Product B) is initiated from within the app while the user is logged into a different account in our system (Token B), but using the sam
0
0
38
6d
Github repository issues, no branches showing
I added a workflow and it seemed to work fine so lets add them all ! I added a second workflow and it seems to see the repository but not the branches in the repository. I have googled and even asked AI. Checked and it's installed with all repo access on Github Removing the repo .. adding it back Deleting the workflow and adding it back Adding the workflow from the browser Adding the workflow from XCode Nothing seems to work, but the first one I created works. Is there paid support for Xcode Cloud ? I s there a version control that works better with Xcode Cloud? Any suggestions are appreciated.
0
0
32
6d
Reply to Slow launch of app on iOS Simulator 26.4
➜ ~ /Applications/Xcode.app/Contents/Developer/usr/bin/simctl runtime dyld_shared_cache update --all Updating dyld shared cache if needed for runtime: iOS 26.3 (26.3.1 - 23D8133) - com.apple.CoreSimulator.SimRuntime.iOS-26-3. dyld shared cache is usable at path: '/Library/Developer/CoreSimulator/Caches/dyld/25D2128/com.apple.CoreSimulator.SimRuntime.iOS-26-3.23D8133/'. Updating dyld shared cache if needed for runtime: iOS 26.4 (26.4 - 23E244) - com.apple.CoreSimulator.SimRuntime.iOS-26-4. dyld shared cache is usable at path: '/Library/Developer/CoreSimulator/Caches/dyld/25D2128/com.apple.CoreSimulator.SimRuntime.iOS-26-4.23E244/'. But no changes to the startup time. Regarding configuration:
6d
Left-flick and right-flick gestures with VoiceOver and UIAccessibilityReadingContent
Hi, I have an app that displays lines of text, that I want to make accessible with VoiceOver. It's based on a UITextView. I have implemented the UIAccessibilityReadingContent protocol, following the instructions in https://developer.apple.com/videos/play/wwdc2019/248 and now users can see the screen line by line, by moving their fingers on the screen. That works fine. However, users would also like to be able to use left-flick and right-flick to move to the previous or next line on the screen, and I haven't been able to make this work. I can see that left-flick triggers accessibilityPreviousTextNavigationElement and right-flick triggers accessibilityNextTextNavigationElement, but I don't understand what these variables should be.
Replies
1
Boosts
0
Views
642
Activity
5d
DJI DNG
DJI's DNG files display abnormally in the Apple Photos app on iOS devices, with dark areas showing as very black, but the same files appear normal in Photoshop. I'm curious about what causes this issue.
Replies
0
Boosts
0
Views
22
Activity
5d
Technical Blocker: Family Controls Entitlement for DeviceActivityMonitorExtension (Parent app already approved)
Hello, I am facing a critical technical blocker regarding the Family Controls (Screen Time API) entitlement for my app extensions. Current Situation: My parent app (com.hayashikento.FocusPact) is already approved for the Family Controls (Distribution) entitlement. However, the associated DeviceActivityMonitorExtension (com.hayashikento.FocusPact.FocusPActMonitor) and ReportExtension (com.hayashikento.FocusPact.ReportExtension) are still pending entitlement approval. Technical Issue: Because the extensions lack the Distribution entitlement, ManagedSettings and DeviceActivity triggers (like intervalWillEndWarning) are ignored by the system when testing via TestFlight or in a non-development environment. As a result, I am unable to verify the core automatic re-blocking logic and usage reporting features in a real-world scenario. This has completely halted the final QA and TestFlight phase of my project. Requests: Could an Apple engineer verify if these extension IDs c
Replies
0
Boosts
0
Views
28
Activity
5d
Reply to Certificates valid if account is changed?
How are you distributing your programs? Directly, using Developer ID signing? Or via the Mac App Store? Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com
Replies
Boosts
Views
Activity
5d
Reply to Understanding '.waiting' state in NWConnection.State for UDP
NWConnection is quite generic, so you shouldn’t be surprised that not all of its options make sense for all connection types [1]. However, in this case the .waiting state does make sense for UDP. Consider a connection created like this: let connection = NWConnection(to: .hostPort(host: example.com, port: 80), using: .udp) If you run this on a device with Airplane Mode enabled, the connection will enter the .waiting state. That’s because it’s waiting for DNS to come online so that it can resolve example.com to find out what addresses it should attempt to ‘connect’ to. But that’s just an example. I suspect that are a number of other cases where you’ll see this. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com [1] The new NetworkConnection API improves this situation, using the Swift type system to vary the operations supported on the connection based on the underlying protocol. However, there are limits to how much you can improve this
Replies
Boosts
Views
Activity
5d
Rejected under Guideline 1.1.1 (Objectionable Content) — car notification app, looking for advice
Hi everyone, I recently got rejected under Guideline 1.1.1 - Safety - Objectionable Content and I'm struggling to understand how my app falls under this category. Looking for advice from anyone who's dealt with similar rejections. What the app does: AutoSignal is a vehicle notification app designed for the Bulgarian market. It solves a very common real-world problem - needing to contact a car owner when their vehicle is double-parked, blocking you in, has its lights left on, or has been hit/damaged while parked. The core flow is: A user scans a license plate using their phone camera If the car owner is registered in the app, they receive an anonymous push notification (e.g., Your car with plate XX 1234 XX is blocking someone or Your lights are on) The car owner can then take action Users can also report vehicle damage cases with temporary witness notes that auto-expire after 7 days. Why I believe it doesn't violate 1.1.1: The app does not expose any person
Replies
1
Boosts
0
Views
43
Activity
5d
Reply to Sporadic crash in xzm_main_malloc_zone_init_range_groups when spawning large binaries (macOS 26.3.1)
The 3 in that error is KERN_NO_SPACE, which is a pretty clear indication that the system memory allocator asked for address space and the kernel refused to give it. However, given all the constraints you’ve described, it’s not at all clear why that would be. Weirdly, the code that traps this way is not on the main branch of the Darwin open source, but I found a copy in the rel/libmalloc-792 branch [1]. Now, I don’t have time today to study that code in depth, but I figured you’d find it interesting (-: AFAICT it tries to allocate address space by using mach_vm_map to map MEMORY_OBJECT_NULL, specifying a start that’s after 16 GiB, such that it fits within 64 GiB, with a randomly applied offset. That random bit probably explains why this shows up so infrequently. It’s hard to say why this is failing. You might be able to learn more by running vmmap against the dying process. It’d also be interested to know what address was passed to mach_vm_map (with reference to the source, that’s the ptr_add
Replies
Boosts
Views
Activity
5d
Reply to ‌Xcode26-built apps cannot run on iPhone 6 or earlier devices‌
Not just Xcode 26 — re-releasing with an older version of Xcode has the same issue. For users on iOS 12 and below, the app can no longer launch.
Replies
Boosts
Views
Activity
5d
Reply to Need MetricKit Implementation details for MacOS background Application, mainly for
MetricKit definitely works on macOS. I’m not sure about how it interacts with Network Extension processes. Let’s start with some basics: Is your NE provider packaged as an app extension or a system extension? If it’s an sysex, are you distributing it directly? Or on the Mac App Store. TN3134 Network Extension provider deployment talks more about NE provider packaging and deployment options. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com
Replies
Boosts
Views
Activity
6d
AccessoryTransport Extensions not launching on iOS 26.5 beta — missing entitlements not available in provisioning
Environment Xcode 26.5 beta iOS 26.5 beta Using AccessorySetupKit + AccessoryTransportExtension framework Three extensions: AccessoryTransportAppExtension, AccessoryTransportSecurityExtension, AccessoryDataProviderExtension Background Everything worked correctly on iOS 26.4 beta. All three extensions shared the entitlement com.apple.developer.accessory-transport-extension, and the system launched them as expected. After upgrading to iOS 26.5 beta (both Xcode and device), the app compiles and runs, the accessory pairs and connects successfully (state = authorized, BLE connected, notification forwarding = allow), but none of the extensions are launched by the system. Investigation Captured system Console logs from the device and found these errors from deviceaccessd: error deviceaccessd ### Extension 'com.huami.NotificationForwardingDemo.AccessoryDataProviderExtension' is missing entitlement: com.apple.developer.accessory-data-provider for com.apple.accessory-data-provider error deviceaccessd ### Exten
Replies
1
Boosts
0
Views
59
Activity
6d
Enrollment Pending 5 Days — Paid €99, No Activation, No Support Response, 3 Open Cases Ignored
I purchased the Apple Developer Program on March 26, 2026. Payment went through immediately. I have the invoice (UA31019584), the order confirmation (W1318171870), and €99 charged to my card. Apple had no problem taking my money within seconds. Five days later: Account status: Pending Portal still says Purchase your membership and asks me to pay again App Store Connect: inaccessible TestFlight: inaccessible I contacted Apple Developer Support on day one — both by email and callback request. I now have three open cases and have received exactly zero responses: Case ID: 102856462218 — Program Purchase and Renewal Case ID: 102853916886 — Program Purchase and Renewal Case ID: 102853919455 — Program Enrolment Not a single acknowledgment. Not even an automated we're looking into it. Nothing. My app is built and ready. I have testers waiting. I cannot distribute anything — not even through TestFlight — because Apple took my pay
Replies
0
Boosts
0
Views
38
Activity
6d
Unexpected appAccountToken mutation in JWSRenewalInfo during in-app crossgrade
Hello Apple Developer Support / StoreKit Team, We recently observed a behavior regarding the appAccountToken in App Store Server Notifications v2 that seems to completely contradict the official documentation. According to the Set App Account Token documentation: The same appAccountToken continues to apply to renewal transactions if the customer upgrades, downgrades, or cross-grades the subscription. However, we encountered a scenario where an active in-app crossgrade resulted in an updated/overwritten appAccountToken inside the subsequent JWSRenewalInfoDecodedPayload, despite our backend never calling the Set App Account Token REST API. Our Observation: A user subscribes to our 1-month plan (Product A). Apple generates an originalTransactionId bound to their initial appAccountToken (Token A). Later, a crossgrade to a 1-year plan (Product B) is initiated from within the app while the user is logged into a different account in our system (Token B), but using the sam
Replies
0
Boosts
0
Views
38
Activity
6d
Reply to App Store DSA regulation compliance is "in review" state for a month
Have you been able to move forward with this? I'm in the same situation and no response from the support.
Replies
Boosts
Views
Activity
6d
Github repository issues, no branches showing
I added a workflow and it seemed to work fine so lets add them all ! I added a second workflow and it seems to see the repository but not the branches in the repository. I have googled and even asked AI. Checked and it's installed with all repo access on Github Removing the repo .. adding it back Deleting the workflow and adding it back Adding the workflow from the browser Adding the workflow from XCode Nothing seems to work, but the first one I created works. Is there paid support for Xcode Cloud ? I s there a version control that works better with Xcode Cloud? Any suggestions are appreciated.
Replies
0
Boosts
0
Views
32
Activity
6d
Reply to Slow launch of app on iOS Simulator 26.4
➜ ~ /Applications/Xcode.app/Contents/Developer/usr/bin/simctl runtime dyld_shared_cache update --all Updating dyld shared cache if needed for runtime: iOS 26.3 (26.3.1 - 23D8133) - com.apple.CoreSimulator.SimRuntime.iOS-26-3. dyld shared cache is usable at path: '/Library/Developer/CoreSimulator/Caches/dyld/25D2128/com.apple.CoreSimulator.SimRuntime.iOS-26-3.23D8133/'. Updating dyld shared cache if needed for runtime: iOS 26.4 (26.4 - 23E244) - com.apple.CoreSimulator.SimRuntime.iOS-26-4. dyld shared cache is usable at path: '/Library/Developer/CoreSimulator/Caches/dyld/25D2128/com.apple.CoreSimulator.SimRuntime.iOS-26-4.23E244/'. But no changes to the startup time. Regarding configuration:
Replies
Boosts
Views
Activity
6d