We have received several cases that our app can not display uitableview cell in iOS26, but users said that they can select cells with single tab and the uitableview didselectcell delegate can response！ I have reported a feedback but no response. Does anyone have the same bugs with me？ You guys can see that the page is blank, I have a video a user sent to me can proved that he can select cell with gesture. We cannot reproduce the bug and don't konw how to fixed, we think this is the bug with iOS26, so here for some help. This bug block our distribution of new version(support iOS26) This is the feedback https://feedbackassistant.apple.com/feedback/20677046
Search results for
Request failed with http status code 503
190,641 results found
Selecting any option will automatically load the page
Post
Replies
Boosts
Views
Activity
Hi, after 2 years of not updating my app on appstore i wanted to submit an update for my iOS app which also containts a watch app target. When i try to submit it to upload it i get the following errors: Failed registering bundle identifier The app identifier (myappBundleID).watchkitapp cannot be registered to your development team because it is nit available. Change your bundle identifier to a unique string to try again. No Profiles for (myappBundleID).watchkitapp were found. Xcode culdn't find any iOS App Store provisining profiles matching (myappBundleID).watchkitapp Since i have my app already in store with that bundle identifier i don't know why it can not be registered to my team. Also i don't want to change the bundle identifier because then i can not publish it as update to store.
I have an Xcode project setup as follows: 3 static libraries 1 framework target, whose Mach-O type is set to Dynamic Library main app target (iOS app) The target dependencies are as follows: In framework's build phase [Link with libraries], I have the 3 libs statically linked. In the main app's build phase [Link with libraries], I have only the framework, which is dynamically linked. As per my understanding: The libs are statically linked to the framework. So, the framework binary would contain code from all the libs. The framework is dynamically linked to the main app (iOS app in this case). So, the main app's binary only has a reference to the framework's binary, which would be loaded in the memory at runtime. Assuming my understanding is correct, I'm stuck with the following problem: All 3 libs build successfully The framework builds successfully The main app target doesn't build. The compilation is successful, but the build fails with linker errors. Please let me know if I am doing somet
I’m not sure I fully understand your latest message, but this is a concern: [quote='862073022, raunits, /thread/800094?answerId=862073022#862073022, /profile/raunits'] I added a Copy Files build phase to copy these libs to the .app bundle but still face the same error. [/quote] It sounds like you’re trying to use a standard dynamic library (.dylib) on iOS. That won’t work. Third-party dynamic libraries must be wrapped in in a framework (.framework). Placing content in a bundle is very clear about this. So, a structure like this will work on the Mac: MyApp.app/ Contents/ MacOS/ MyApp Frameworks/ MyFramework.framework/ Versions/ A/ MyFramework MyLib.dylib but the equivalent iOS structure isn’t supported: MyApp.app/ MyApp Frameworks/ MyFramework.framework/ MyFramework MyLib.dylib <<< not allowed Rather, you need to manually wrap the library as a framework: MyApp.app/ MyApp Frameworks/ MyFramework.framework/ MyFramework MyLib.framework/ MyLib IMPORTANT I’ve elided the Info.plist files from the above for
Topic:
Developer Tools & Services
SubTopic:
General
Tags:
Hello! My question is about 1) if we can use any and or all accessibility features within a sandboxed app and 2) what steps we need to take to do so. Using accessibility permissions, my app was working fine in Xcode. It used NSEvent.addGlobalMonitorForEvents and localMoniter, along with CGEvent.tapCreate. However, after downloading the same app from the App Store, the code was not working. I believe this was due to differences in how permissions for accessibility are managed in Xcode compared to production. Is it possible for my app to get access to all accessibility features, while being distributed on the App Store though? Do I need to add / request any special entitlements like com.apple.security.accessibility? Thanks so much for the help. I have done a lot of research on this online but found some conflicting information, so wanted to post here for a clear answer.
[quote='861637022, Macho Man Randy Savage, /thread/758375?answerId=861637022#861637022, /profile/Macho+Man+Randy+Savage'] I'd like to know what the recommendation is for a new Mac app. [/quote] App Groups: macOS vs iOS: Working Towards Harmony is quite clear about this: If you’re writing new code that uses app groups, use an iOS-style app group ID. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com
Topic:
Privacy & Security
SubTopic:
General
Tags:
[quote='861494022, dreisicht, /thread/802464?answerId=861494022#861494022, /profile/dreisicht'] Is there a way to get more information about why the Developer ID Certificate is invalid? [/quote] That’s a red herring. The fundamental issue here is that your code isn’t signed correctly and the notary service responds to that by issuing a generic error. [quote='861494022, dreisicht, /thread/802464?answerId=861494022#861494022, /profile/dreisicht'] I tried signing the files in ascending order, meaning so sign all files first, and the directory above it. [/quote] That’s not the right approach. Don’t just walk up the directory hierarchy signing each directory as you go. That won’t yield the results you need. Rather, identify each code item and then sign each item separately, from the inside out. Now, a code item might be a bundle and on disk that’s a directory, and signing that is cool. However, that’s not the same as signing each directory. So, you need to: Find each code item.
Topic:
Code Signing
SubTopic:
Certificates, Identifiers & Profiles
I'm trying to sign a .app package coming from Py2app. Unfortunately I keep running into the same two issues: The binary is not signed with a valid Developer ID certificate. and The signature does not include a secure timestamp. I tried everything, from recreating the signatures, with different arguments, different keys and certificates, but it keeps complaining with these two errors on a long list of files. For reference I added the python script I use for signing the files. code_singing.py
Topic:
Code Signing
SubTopic:
Certificates, Identifiers & Profiles
Xcode downloaded a crash report for my app that crashed when trying to insert a String into a Set. Apparently there was an assertion failure ELEMENT_TYPE_OF_SET_VIOLATES_HASHABLE_REQUIREMENTS. I assume that this assertion failure happened because the hash of the new element didn't match the hash of an equal already inserted element, but regardless, I don't understand how inserting a simple string could trigger this assertion. Here is essentially the code that leads to the crash. path is any file system directory, and basePath is a directory higher in the hierarchy, or path itself. var scanErrorPaths = Set() func main() { let path = /path/to/directory let basePath = /path let fileDescriptor = open(path, O_RDONLY) if fileDescriptor < 0 { if (try? URL(fileURLWithPath: path, isDirectory: false).checkResourceIsReachable()) == true { scanErrorPaths.insert(path.relativePath(from: basePath)!) return } } extension String { func relativePath(from basePath: String) -> String? { if basePath == { return se
Hello, I’m developing an app for both iOS and macOS using Mac Catalyst. On the iOS target, the DeclaredAgeRange framework works fine: I enabled the capability, set the entitlement, and can call the APIs successfully. However, when I build the Mac Catalyst target, I get compile-time errors because DeclaredAgeRange cannot be imported. Environment Xcode 26.0.1 Deployment Target (iOS): 13.0 Mac Catalyst target enabled (same bundle ID, same source code base as iOS version) iOS build works well with DeclaredAgeRange What I tried Added the Declared Age Range capability in Signing & Capabilities for iOS target → works fine. Tried setting Mac Catalyst Deployment Target to macOS 15.0+ and rebuilding → still failed to import. Because it didn’t help, I reverted and removed the separate macOS target setting. On Catalyst, the module simply isn’t available (import DeclaredAgeRange fails). From Apple’s documentation, my understanding is that DeclaredAgeRange should also be supported on Mac Cata
Topic:
App & System Services
SubTopic:
General
[quote='861851022, Mikesch8764, /thread/802830?answerId=861851022#861851022, /profile/Mikesch8764'] It looks like there is no such header available [/quote] Right. Like many of our new frameworks, DeclaredAgeRange is Swift only. If you have an Objective-C app, you’ll need to write Swift code to call the new framework and then call that Swift code from Objective-C. If this is the first time you’ve done that, you can crib ideas from the example I posted here. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com
Topic:
App & System Services
SubTopic:
General
I’m unable to notarize the executable and the .app — the status has been showing “In Progress” for over an hour. Upon checking the xcrun logs, it indicates that the submission ID was not received. I also noticed there’s an Apple Developer Service outage reported since October 8, 2025. Could you please let me know when this outage is expected to be resolved? It would be very helpful.
Hi everyone, I’ve just subscribed and configured my Apple Developer account. I tried to notarize the first binary I need to distribute via Homebrew, but I’m experiencing an issue where the process has been stuck in “In Progress” status for more than 21 hours, without completing or returning any errors. Here’s the relevant history: createdDate: 2025-10-15T21:53:41.343Z status: In Progress
Successfully received submission history. history ...... -------------------------------------------------- createdDate: 2025-10-19T18:34:47.472Z id: d3248896-7841-421e-9470-101df9d0da21 name: ... status: In Progress -------------------------------------------------- createdDate: 2025-10-19T18:12:45.325Z id: e5822fa0-5bcf-4610-81fc-9f541e8ad189 name: ... status: In Progress
You can expect that most uploads will be notarised quickly. Occasionally, some uploads are held for in-depth analysis and may take longer to complete. As you notarise your apps, the system will learn how to recognise them, and you should see fewer delays. Oh, and just FYI: [quote='862770022, glenbot, /thread/771909?answerId=862770022#862770022, /profile/glenbot'] But the first 6 or so i was using the app specific password. I switched to connect api per electron builder recommendations [/quote] The method you use to authenticate has no bearing on the above. I also recommend that you use an API key rather than an app-specific password, but that’s just because it’s easier to understand (-: Oh, and one last thing. I’m going to close out this thread because I don’t want it to become a MegaThread™ that attracts everyone who experiences notarisation delays. If you experience very long notarisation delays — say more than a week — please start a new thread with the details. Put it in the Code Signing > Not
Topic:
Code Signing
SubTopic:
Notarization
Tags: