I'm developing a macOS console application that uses ODBC to connect to PostgreSQL. The application works fine when run normally, but fails to load the ODBC driver when debugging with LLDB(under root works fine as well). Error Details When running the application through LLDB, I get this sandbox denial in the system log (via log stream): Error 0x0 0 0 kernel: (Sandbox) Sandbox: logd_helper(587) deny(1) file-read-data /opt/homebrew/lib/psqlodbcw.so The application cannot access the PostgreSQL ODBC driver located at /opt/homebrew/lib/psqlodbcw.so(also tried copy to /usr/local/lib/...). Environment macOS Version: Latest Sequoia LLDB: Using LLDB from Xcode 16.3 (/Applications/Xcode16.3.app/Contents/Developer/usr/bin/lldb) ODBC Driver: PostgreSQL ODBC driver installed via Homebrew Code Signing: Application is signed with Apple Development certificate What is the recommended approach for debugging applications that need to load dynamic libraries? Are there specific entitlements or configurations that would
Search results for
İOS 26 beta battery %1
250,969 results found
Selecting any option will automatically load the page
Post
Replies
Boosts
Views
Activity
On macOS Sequoia, I'm having the hardest time getting this basic audio output to work correctly. I'm compiling in XCode using C99, and when I run this, I get audio for a split second, and then nothing, indefinitely. Any ideas what could be going wrong? Here's a minimum code example to demonstrate: #include <AudioToolbox/AudioToolbox.h> #include <stdint.h> #define RENDER_BUFFER_COUNT 2 #define RENDER_FRAMES_PER_BUFFER 128 // mono linear PCM audio data at 48kHz #define RENDER_SAMPLE_RATE 48000 #define RENDER_CHANNEL_COUNT 1 #define RENDER_BUFFER_BYTE_COUNT (RENDER_FRAMES_PER_BUFFER * RENDER_CHANNEL_COUNT * sizeof(f32)) void RenderAudioSaw(float* outBuffer, uint32_t frameCount, uint32_t channelCount) { static bool isInverted = false; float scalar = isInverted ? -1.f : 1.f; for (uint32_t frame = 0; frame < frameCount; ++frame) { for (uint32_t channel = 0; channel < channelCount; ++channel) { // series of ramps, alternating up and down. outBuffer[frame * channelCount +
The same store kit configuration file works in iOS and iPadOS, but not in macOS for the same multi platform application project with a single scheme. Here’s a more detailed write up with the sample code and screenshots. When the simple app is run on https://www.reddit.com/r/SwiftUI/s/KJsYcggWOa EDIT: I’m using Xcode 16.4
I get the same issue with my store kit configuration file. interestingly It still works on iOS in a simulation, but it does not work on macOS in a simulation. macOS always returns no products when I call the API. Here’s a post where I’m looking for an answer to that issue as well. https://www.reddit.com/r/SwiftUI/s/64xfCfbIPM
Topic:
App & System Services
SubTopic:
StoreKit
Tags:
One can remove a language from the .xcstrings file through the .xcodeproj file, under Localization → (-) [Language]. The .xcstrings file seems to lack a minus (-) Button. However, in my project I could remove a language like this: I added the language (L) in the .xcstrings file to test it. After some time, the language L showed up in .xcodeproj file, under Localization. ❗️3. Here, there is a (+) and a (-) button, I selected the language L and removed it using the (-) button.❗️ After some time again, the language L did not appear in the .xcstrings file anymore. I assume it takes some time to synchronize between .xcstrings and .xcodeproj. Best, Tim :)
Topic:
Developer Tools & Services
SubTopic:
Xcode
Tags:
Hi, I am experiencing an issue where Xcode displays a Provisioning profile doesn't support the capability error for the User Assigned Device Name capability, despite it being approved by Apple and visible in our provisioning profile on the Developer Portal. Background We have completed and submitted the required capability request form to Apple for the User Assigned Device Name capability and received approval. The capability appears correctly in our provisioning profile on the Apple Developer Portal and shows among the enabled capabilities alongside other standard capabilities like In-App Purchase and Push Notifications. Issue However, Xcode consistently displays the error message when trying to enable the User Assigned Device Name capability in our project settings, preventing successful builds with this functionality. Troubleshooting Steps Attempted We have tried multiple troubleshooting steps including: Regenerating provisioning profiles Performing clean builds Clearing DerivedData Manually installing pro
Topic:
Code Signing
SubTopic:
Certificates, Identifiers & Profiles
Tags:
Xcode
Provisioning Profiles
Hello everyone. Hope this one finds you well) I have an issue with integrating a FIDO2 server with ASAuthorizationController. I have managed to register a user with passkey successfully, however when authenticating, the request for authentication response fails. The server can't validate signature field. I can see 2 possible causes for the issue: ASAuthorizationPlatformPublicKeyCredentialAssertion.rawAuthenticatorData contains invalid algorithm information (the server tries ES256, which ultimately fails with false response), or I have messed up Base64URL encoding for the signature property (which is unlikely, since all other fields also require Base64URL, and the server consumes them with no issues). So the question is, what encryption algorithm does ASAuthorizationController use? Maybe someone has other ideas regarding where to look into? Please help. Thanks)
No idea if this pending authorization disposition is relevant or not, but I do not know what else I as a user can possibly authorize beyond flipping the switch in System Settings. #9: UUID: 0C6D2CA3-9BAF-45D8-819B-604F52203F56 Name: SMAppServiceSampleCode Developer Name: ABCDEFG Team Identifier: *****437 Type: app (0x2) Disposition: [disabled, allowed, visible, not notified] (2) Identifier: identifier com.example.apple-samplecode.SMAppServiceSampleCode8B59GX9437 and anchor apple generic and certificate leaf[subject.CN] = Apple Development: user@host.com (XXXXXXX) and certificate 1[field.1.2.840.113635.100.6.2.1] /* exists */ URL: file:///Applications/SMAppServiceSampleCode.app/ Generation: 0 Bundle Identifier: com.example.apple-samplecode.SMAppServiceSampleCode8B59GX9437 Embedded Item Identifiers: #1: com.xpc.example.agent #10: UUID: F8746E58-2ADA-4840-82E7-9DCC1F77FD72 Name: SampleLaunchAgent Developer Name: (null) Type: daemon (0x10) Disposition: [enabled, allowed, visible, notified] (pend
Topic:
App & System Services
SubTopic:
Processes & Concurrency
Tags:
ASWebAuth + Universal link issue -In login iOS application we are launching the Login URL in the ASWebAuth to support the auto-saving of the username and password. -It enables the passkey options seamlessly. When user enters into the Native app using the passkey or saved credentials, we send an Auth-Return URL to Login system -login in response of successful authentication redirect user to the Auth-Return URL along with an authenticated Auth-Code value. -When the Auth-Return URL is evaluated, it is expected that we should redirect user back the Native application and proceed with the session of the user along with the Auth-Code received. Problem is ASWebAuth not dismissing and handover to app
Topic:
Privacy & Security
SubTopic:
General
Tags:
OK, that’s definitely a sysex. Thanks for confirming. Given that, you should be able to export it for direct distribution with Developer ID signing. You’ll have to carefully work through the steps in Exporting a Developer ID Network Extension. Make sure that: The code is signed with the Developer ID variants of the com.apple.developer.networking.networkextension entitlement values. That entitlement claim is authorised by a Developer ID provisioning profile. Make sure to check both the container app and the embedded sysex. I also recommend that you add a ‘first light’ log point to your sysex so you can see whether it’s code runs at all. See Debugging a Network Extension Provider for more about that. And if you don’t get that log point, make sure to check for crash reports. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com
Topic:
App & System Services
SubTopic:
Networking
Tags:
Again, I recommend that you use a .exp file so you have direct control over what gets exported. If you don’t want to do that, you’ll have to combine information about how the symbols are exported from the static library with information about how the framework is linked. For the former, see An Apple Library Primer and the Understanding Mach-O Symbols post it links to. For the latter, see Command [something] failed with a nonzero exit code for the commands passed to the linker, cross referencing that with the help in the ld man page. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com
Topic:
Developer Tools & Services
SubTopic:
General
Tags:
[quote='857868022, ski4funSonoma, /thread/799933?answerId=857868022#857868022, /profile/ski4funSonoma'] it seems to be the remedy to the helper/daemon crash. [/quote] That’s unlikely. Launch contraints typically cause things to fail rather than make things work. Hence the constraint. My advice here is that you remove anything you’ve done with regards launch constraints and then debug the original problem you were seeing. If that’s a crash and you post a crash report, I’d be happy to take a look. See Posting a Crash Report for advice on how to post a crash report. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com
Topic:
Code Signing
SubTopic:
General
Tags:
The answer here is… well… fuzzy. I’m gonna recommend that you file a bug about the weird behaviour you’re seeing, so we can use that to investigate further. IMPORTANT Make sure to include information about why you’re accessing ARP, that is, what high-level goal you’re trying to achieve this way. Please post your bug number, just for the record. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com
Topic:
App & System Services
SubTopic:
Networking
Tags:
You tagged your thread with metal-cpp so I’d like to clarify how Metal fits into this. Neon intrinsics are obviously limited to the GPU. So what’s up with Metal? [quote='800232021, anthony_gaudino, /thread/800232, /profile/anthony_gaudino'] in macOS 15.6.1 [/quote] Also, just to be clear, macOS doesn’t ship with any headers. You get headers when you install developer tools, either Xcode or the Command Line Tools package. So, which of those do you have installed? And what version? Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com
Topic:
Programming Languages
SubTopic:
General
Tags:
I generally recommend that you direct questions about the Swift open source effort to Swift Forums. And lo! it seems that you’ve already done that, and got some useful response. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com
Topic:
Programming Languages
SubTopic:
Swift
Tags: