Search results for

xcode github

91,899 results found

Post

Replies

Boosts

Views

Activity

Reply to What happened to CMD-Option-Click?
I don't know if I speak of the same thing. -Cmd-Option-click on a class name as NSWindow or UIWindow, or a protocol as UIApplicationDelegate. this should open the class or the protocol in a second pane. Is it what you mean ? If so, I tested both in Xcode 16.4 and 26ß7. It works as described in both.
2d
Example default dialer project
I'm trying to create a dialer app for iOS that will make verified cellular, not voip, calls by registering the calls on my server with an option for passphrase offline verification. This means that I want to build a dialer with a nice UX, so I'm trying to use the new default dialer capability. I've read https://developer.apple.com/documentation/livecommunicationkit/preparing-your-app-to-be-the-default-dialer-app which links to https://developer.apple.com/documentation/livecommunicationkit/startcellularconversationaction for starting a call, but when I try to actually use it in my app it says Cannot find type 'TelephonyConversationManager' in scope and similar, despite importing LiveCommunicationKit. Is there a default dialer example app & xcode project I can look at for how this should be set up? As I understood it I should be able to use these from iOS 18.2, and I'm targeting that version in my project. The page for StartCellularConversationAction says Beta 26.0 though, have I misunderstood some
2
0
69
2d
Foundation Models framework dyld symbol errors after macOS 26 Beta 2 - LanguageModelSession constructor missing
Foundation Models framework worked perfectly on macOS 26 Beta 2, but starting from Beta 3 and continuing through Beta 6 (latest), I get dyld symbol errors even with the exact code from Apple's documentation. Environment: macOS 26.0 Beta 6 (25A5351b) Xcode 26 Beta 6 M4 Max MacBook Pro Apple Intelligence enabled and downloaded Error Details: dyld[Process]: Symbol not found: _$s16FoundationModels20LanguageModelSessionC5model10guardrails5tools12instructionsAcA06SystemcD0C_AC10GuardrailsVSayAA4Tool_pGAA12InstructionsVSgtcfC Referenced from: /path/to/app.debug.dylib Expected in: /System/Library/Frameworks/FoundationModels.framework/Versions/A/FoundationModels Code Used (Exact from Documentation): import FoundationModels // This worked on Beta 2, crashes on Beta 3+ let model = SystemLanguageModel.default let session = LanguageModelSession(model: model) let response = try await session.respond(to: Hello) What I've Verified: FoundationModels.framework exists in /System/Library/Frameworks/ Framework is properl
1
0
460
3d
401 Unauthorized when attempting to access Apple Music Feed API
Hello, I am trying to access the Apple Music Feed API, but I am recieving a 401 Unauthorized error message whenever I try to access it. I have tried using my own code to generate a JWT and directly call the API (which can call the standard Apple Music API successfully). > GET /v1/feed/song/latest HTTP/2 > Host: api.media.apple.com > user-agent: insomnia/2023.5.8 > authorization: Bearer [REDACTED] > accept: */* < HTTP/2 401 < content-type: application/json; charset=utf-8 < content-length: 0 < x-apple-jingle-correlation-key: AV5IOHBNM2UUJVOFQ4HZ2TGF6Q < x-daiquiri-instance: daiquiri:10001:daiquiri-all-shared-ext-7bb7c9b9bb-r459v:7987:25RELEASE91:daiquiri-amp-kubernetes-shared-ext-ak8s-prod-pv4-amp-daiquiri-ingress-prod and also the Apple provided Python example code, which gives me authentication errors too. $ python3 ./apple_music_feed_example.py --key-id NMBH[...] --team-id 3TNZ[...] --secret-key-file-path /Users/foxt/Documents/am-feed/NMBH[...
0
0
319
3d
Xcode Cloud error 401
I have now signed out of my account in Xcode, quit the application, signed back in, and also cleared the Xcode derived data and cache. However, I am still receiving the 401 Unauthorized error Any operation related to Xcode Cloud (e.g., viewing the dashboard, creating a workflow) fails immediately across all Xcode projects, including brand-new empty projects. The error is consistent and always appears as: API Invalid status code: 401. Domain: XcodeCloudCombineAPI.XCCResponseError Code: 1 System Information: macOS Version 15.6.1 (Build 24G90) details : Error alert: API Invalid status code: 401.: XCCResponseError(responseErrorType: XcodeCloudCombineAPI.XCCResponseError.XCCResponseErrorType.invalidStatusCode(XcodeCloudCombineAPI.LegacyHttpStatus.unauthorized), requestUrl: Optional(https://appstoreconnect.apple.com/ci/api/teams//apps/find?bundle_id=), traceId: Optional(2ab09bea8da9ef39), retryAfterSecsStr: nil, response: Optional( { URL: https://appsto
0
0
149
3d
Button Glass Style Incorrect in Sheet + ScrollView on Mac Catalyst 26
Hi everyone! I've encountered an issue when using Sheet + ScrollView on Mac Catalyst: the buttons in the toolbar appear with an abnormal gray color. import SwiftUI struct ContentView: View { var body: some View { VStack { } .sheet(isPresented: .constant(true)) { Sheet() } } } struct Sheet: View { var body: some View { NavigationStack { ScrollView { // <-- no issue if use List } .toolbar { Button(action: {}) { // <-- 👀 weird gray color Image(systemName: checkmark) } } } } } Steps to Reproduce: On macOS 26.0 beta 9, use Xcode 26.0 beta 7 to create an iOS project and enable Mac Catalyst. Paste the code above. Select the Mac Catalyst scheme and run the project. The buttons in the toolbar show a strange gray appearance. If you change the ScrollView to a List in the code, the issue does not occur. FB20120285
1
0
245
3d
UDP Broadcast fails on the first try after the iOS 18.5 update but works after restart
Upgrade iOS to 18.5, then install app in Xcode and grant permissions to send UDP but it won't work. Then restart device, open this installed app and send UDP again and this time it becomes OK. Repeat these steps and it all goes well. The UDP pod I use in app is CocoaAsyncSocket. The same thing happens on iPhone 14 Plus and 16 Pro, both iOS 18.5. How to explain this phenomenon, thanks for your help in advance.
3
0
116
3d
Reply to Best practices for post-build codesigning
Thank you for such a thorough response! It's at least reassuring that I'm on the right path 😁 I posted a suggestion request under FB20115488. As a quick fix solution, I'm going to try storing the identity as a Base64 encoded environment variable and adding it to the keychain during the build. This is the approach advocated when using GitHub Actions and (somewhat) Azure DevOps Pipelines. I'll report back if that hits a roadblock...
3d
Reply to Value of the key in App.entitlements file for enabling In-App Purchase capability. Which one?
To implement In-App Purchase in your app, you need: Accept the Paid Apps Agreement and complete all tax and banking information. Have an explicit App ID registered in App Store Connect. The In-App Purchase capability appears enabled by default for an explicit App ID and disabled for a wildcard App ID. Hence, it is unnecessary to add the capability in Xcode. Remove it from your project. Configure In-App Purchases products for your App ID in App Store Connect. You can test In-App Purchases in Xcode test local environment or sandbox. For more information, see Testing at all stages of development with Xcode and the sandbox TN3186: Troubleshooting In-App Purchases availability in the sandbox TN3185: Troubleshooting In-App Purchases availability in Xcode.
3d
Reply to Apple pay processing payment fail
Hi @Idang, You wrote: Hey, I am trying to implement the apple pay process pay backend service, I have checked everything and somehow it fails. I only have 1 certificate for merchant and 1 for the apple pay process, I have the private keys and try to run this following code that fails - [...] Please review the following post so we can gather the proper data from your testing device and server-side implementation: Gathering Required Information for Troubleshooting Apple Pay on the Web Merchant Issues https://developer.apple.com/forums/thread/762994 Additionally, common reasons for payment token decryption errors are also listed in the technote below: TN3176: Troubleshooting Apple Pay payment processing issues: Possible reasons for payment token decryption errors https://developer.apple.com/documentation/technotes/tn3176-troubleshooting-apple-pay-payment-processing-issues#Possible-reasons-for-payment-token-decryption-errors If you continue to have issues with your description, please reply to your post
3d