Search results for

xcode github

94,044 results found

Post

Replies

Boosts

Views

Activity

Reply to Feedbacks for DeclaredAgeRange - missing platform support
Regarding feedback FB20954846 for App Clip support, I got a message from Apple saying it is fixed. I can now compile, and code sign for an App Clip using the DeclaredAgeRange API. Great. Now that I can get past the compiler failure I'm running up against a new issue. When installed via TestFlight, an App Clip throws that the age range is unavailable. In the console app it looks like the App Clip is still prohibited from calling the system functionality: default PerformanceOrganizer AppClip 18:36:39.200071-0600 (501) Failed to fetch persona: got error from remote proxy: Error Domain=NSCocoaErrorDomain Code=4099 The connection to service named com.apple.mobile.usermanagerd.xpc was invalidated: Connection init failed at lookup with error 159 - Sandbox restriction. UserInfo={NSDebugDescription=The connection to service named com.apple.mobile.usermanagerd.xpc was invalidated: Connection init failed at lookup with error 159 - Sandbox restriction.} error PerformanceOrganizer AppClip 18:36:39.200108-0600 (501) person
2w
Feedbacks for DeclaredAgeRange - missing platform support
I've been writing about the DeclaredAgeRange a bit on LinkedIn and now it is time to take to the developer forums. In my efforts to prepare my apps for new local requirements, I've run across some rough edges. The DeclaredAgeRange API is missing on several platforms, and extension types. First and foremost, watchOS. An Apple Watch is a clear single user platform and for standalone apps, the DeclaredAgeRange being absent is felt by developers. FB20954931 - DeclaredAgeRange: Framework not available on watchOS making compliance a challenge for watchOS standalone apps In the same vein of thinking, while users on Apple Vision Pro are far fewer numbers than Apple Watch, it is also a miss. The tricky part would be testing on the simulator. So far I haven't gotten the simulator and sandbox testing to work and give real values across any platform. I don't think an Apple Store will let me try my app out via TestFlight on their devices and they're still too expensive to reasonably buy for most developers. Too bad Feedba
1
0
346
2w
Xcode Cloud Builds Failing with 7-8 Errors - Builds Stuck in "Processing" on App Store Connect
Hey there. I'm experiencing a critical issue with Xcode Cloud builds for my macOS application (bundle ID: com.mymind.mymind-mac) where builds fail in Xcode Cloud with 7-8 errors, yet all logs indicate successful completion. Additionally, when manually uploading builds, they become stuck in Processing status indefinitely on App Store Connect. Issue Details: Problem: Xcode Cloud reports 7-8 build errors but logs show no fatal errors Secondary Issue: Builds uploaded to App Store Connect remain in Processing status indefinitely Platform: macOS application with Safari Web Extension Xcode Version: 26.1.1 (26B100) - Xcode 26.1 Build Environment: Xcode Cloud What Works: Package dependency resolution completes successfully Archive creation succeeds (** ARCHIVE SUCCEEDED **) Export succeeds (** EXPORT SUCCEEDED **) Provisioning profiles are created correctly Code signing completes without errors Manual upload to App Store Connect completes What Fails: Xcode
3
0
239
2w
Reply to "Signing certificate" and post-installation assignment fail due to IOPCIPrimaryMatch
I'm not sure why Xcode Signing Certificate status is Failed with the above configuration. It doesn't seem to me that DriverKit and the provisioning file expect & as the expected value. Based on the above, isn't it Xcode that expects &? I'm suspicious of Xcode's behavior. I was able to get a look at your account configuration this morning, and I think I can explain what's going on. For reference, I looked at the bundle with this structure: com.0.DextPCIe **Short answer: ** Change your Entitlement.plist configuration to Development Only entitlement configuration: com.apple.developer.driverkit.transport.pci IOPCIPrimaryMatch 0xFFFFFFFF&0x00000000 ...and I think you'll find that your build will suddenly work fine. Note that it's perfectly fine to use the configuration above for normal testing and development. The entitlement above does match all devices, but your IOKitPersonalities dictionary controls what you ACTUALLY match against, so having an broad entitlement doesn'
Topic: Code Signing SubTopic: Entitlements Tags:
2w
Guideline 2.3.1 - Performance The app contains hidden features.
Hello everyone, my game update got rejected with the following violations : Guideline 2.3.1 - Performance The app contains hidden features. Specifically, this app contains a switch which causes it to behave differently during review via alternative web content presentation. It would be appropriate to remove this feature entirely before resubmitting for review. Guideline 4.2 - Design - Minimum Functionality Your app provides a limited user experience as it is not sufficiently different from a web browsing experience. As such, the experience it provides is similar to the general experience of using a web browser. Including features such as push notifications, Core Location, or sharing do not provide a robust enough experience to be appropriate for the App Store. My game is a crossword mobile game made with Unity, and I am using the following 3rd party Sdks: -Playfab server : used to fetch configs, leaderboards and pvp matches. -Applovin : diplaying Ads -Adjust : for marketing measurement -Firebase : analytics/c
1
0
167
2w
Xcode 26 Coding Assistant & Anthropic
I've been trying to use Antrhopic with Xcode 26 RC and continue to run into this error: No Data/Bytes for request: https://api.anthropic.com/v1/messages Once I get it, all prompts fail even a simple Hello that worked a moment ago returns the error message. Restarting Xcode and it returns to normal till I hit that error again. Any ideas on what's going on?
1
0
169
2w
Reply to Love the coding assistant in Xcode
I too love the coding assistant. That is, until I get the evil beachball of death when scrolling the assistant panel down. This happens for me with both ChatGPT and Claude.AI, about 10 or 11 times a day. The only recourse I have is to Force Quit Xcode (26.1) and restart. It is particularly annoying when the cars happens in the middle of a fix or modification.
2w
Xcode debugger stops at dyld after upgrading to Xcode 26
After upgrading to Xcode 26, started getting an issue where Xcode debugger is stopping at dyld`lldb_image_notifier Does not happen on device. Tried cleaning derived data folder, clean build but no success. what could be the cause? this is from the stack. #0 0x0000000207e0ffa1 in lldb_image_notifier () #1 0x0000000207e11c49 in dyld4::ExternallyViewableState::triggerNotifications () #2 0x0000000207e13a2f in invocation function for block in dyld4::ExternallyViewableState::notifyMonitorOfImageListChangesSim(bool, unsigned int, mach_header const**, char const**) () #3 0x0000000207e10c3b in dyld4::ExternallyViewableState::notifyMonitorOfImageListChangesSim () #4 0x00000001102b9195 in dyld4::ExternallyViewableState::triggerNotifications () #5 0x00000001102b9465 in dyld4::ExternallyViewableState::addImages () #6 0x000000011029dcec in dyld4::RuntimeState::notifyDebuggerLoad () #7 0x00000001102b8065 in dyld4::APIs::dlopen_from(char const*, int, void*)::$_0::operator()() const::'lambda'()::operator()()
1
0
109
2w
UISplitViewController.showDetailViewController() not working in iPhone version.
Since updating to Tahoe and Xcode 26 I have found that the UISplitViewController.showDetailViewController() is not working in the iPhone version of my app (it is a universal app). I'm just trying to show a detail view after a tap on a UITableView item. The iPad versions are all working correctly. Has anyone else experienced this or have any advice about what may have changed? Thanks in advance.
1
0
153
2w
Reply to Canvas fails with "Runtime Linking Failure" in Swift Package
Hi, Sorry to hear you are having problems getting previews working. The best next step will be to file a feedback with diagnostics so we can take a look. We will need the diagnostics Xcode Previews generates in order to make sure we understand the error the previews system is encountering. Install the logging profile using instructions available here: https://developer.apple.com/bug-reporting/profiles-and-logs/?name=swift On your mac running Xcode, and on your physical preview device (if you are using one). Install the logging profile using the following instructions on your mac running Xcode; and if you are using one, your physical preview device (iOS or visionOS): https://developer.apple.com/bug-reporting/profiles-and-logs/?name=swift Then when you reproduce the problem in Xcode: Either (a) an error banner will appear, click the Diagnostics button in that banner; or (b) if you're not seeing an error but you still want to provide diagnostics you can get the same diagnostic
2w
Using Transporter to upload app build to App Store Connect on Windows and Linux
Hi all, I'm looking for a way to upload app builds to App Store Connect on Windows and Linux (I know on MacOS we can use Xcode to do that). I found that the Transporter command line tool could be used for this task here - https://help.apple.com/app-store-connect/#/devb1c185036. Then I did some research on the Transporter, and found that to download it you need to be approved by Apple for qualification in here - https://itunespartner.apple.com/en/movies/faq/Transporter_Getting%20Set%20Up. Other than this I can't find much info on exactly how to get access to the tool. Surprisingly not much resources about this on the Internet, and all the apple doc seems very vague on this. So my question is: Can the Transporter tool really be used to upload builds to App Store on Windows and Linux? If yes, what is the exact steps to get access to it? Has anyone been able to go through the process and use the tool?
1
0
2.8k
2w