Search results | Apple Developer Forums

Reply to Apple Developer Enrollment Pending

I applied in August 2025 and called approx every other week for about 4 months. I was told the same thing every time - you just have to wait. Finally, I was told that I would likely be approced next week instead, I was rejected and no explanation. No one to talk to. I have done everything imaginable, no one is helping at all and it's having a big effect on our nonprofit.

Developer Tools & Services Apple Developer Program

1w

Big probelms loging into apple account

Hi there, I'm trying to build my APP with EAS, unfortunately I can't log in the 2FA. I get the call from apple giving me the 2FA code and I enter it correctly but if gives me an error. So I read if I connect it to my laptop (macbook) it should work. However I try to connect my account to my macbook I just get another error: Verification failed Verification codes cannot be sent to this phone number at this time. Please try again later. I suspect it is because I get the codes via voice call and not SMS. However: 1. I can't log into my account anymore as the 2FA always fails now. 2. I can't get SMS on my number. 3. I can't change number, there is also always an unknown error if I try that. This is pretty frustrating especially given I already paid the 100€ for the developer account.

App & System Services General Accounts

1

0

172

2w

Questions on OS Activity Tracing

This is stemmed from another forum post on Apple Unified Logging. A few additional questions were raised towards a relevant but different topic - activity tracing, starting a new post following The Eskimo's suggestion. The first question is on log capture from an activity chain. The related documentation stated something but very vaguely. https://developer.apple.com/documentation/os/generating-log-messages-from-your-code?language=objc#Choose-the-Appropriate-Log-Level-for-Each-Message If an activity object exists, the system captures information for the related process chain We had hoped that this would somewhat play into the speculative logging approach we had touched upon in the original post, in the sense that if we try to log an error or fault within an activity, then it helps to capture and persist other logs on the activity chain even though they are originally not meant to be. But unfortunately from our test it didn't seem to be behaving towards that understanding. Then our question is, if we may ask -

App & System Services Core OS OSLog

1

0

80

2w

Reply to MacOS(Apple Silicon) IOKit driver for FPGA DMA transmission, kernel panic.

Hi Kevin, filed bug number is FB21888307. I provide partial code on bug. Reply to your question: That address should have come from your driver, so how did it exceed 32 bits? All of our APIs for retrieving a bus address should either provide an address that meets your specification or fail entirely. More to the point, even if they some how did return a larger address, why/how would your driver have written a larger address when it was only prepared to handle a 32 bit address? Yes, address comes from my driver by gen64IOVMSegments API. And at the beginning, I didn't know that the address allocated through the API were always >32 bit, so when I received an address >32 bit, I didn't directly return, but continued to use it, resulting in a kernel panic. Next, the big question is how much memory are you actually trying to map? And have you done any experimentation with smaller mappings? I trying to map 20 KB memory, I have already tried 1 Byte or 4 KB, still get 64-bit address. And maximum DMA data

App & System Services Drivers

2w

Reply to MacOS(Apple Silicon) IOKit driver for FPGA DMA transmission, kernel panic.

It seems that the DMA request address initiated by FPGA exceeded 32 bits, which was intercepted by PCIe root port and resulted in a kernel panic.This is also the case on macOS (M2). Please file a bug on this, upload the full panic report there, and then post the bug number back her. I'd like to get a clearer picture of what actually failed. I'm also a bit confused by this point: It seems that the DMA request address initiated by FPGA exceeded 32 bits, That address should have come from your driver, so how did it exceed 32 bits? All of our APIs for retrieving a bus address should either provide an address that meets your specification or fail entirely. More to the point, even if they some how did return a larger address, why/how would your driver have written a larger address when it was only prepared to handle a 32 bit address? Next, the big question is how much memory are you actually trying to map? And have you done any experimentation with smaller mappings? __ Kevin Elliott DTS Engineer, CoreOS/Ha

App & System Services Drivers

2w

Reply to filecopy fails with errno 34 "Result too large" when copying from NAS

This doesn't make sense to me... In brief, compressed files were implemented by: Compressing the file’s contents. Storing that data in the resource fork. Adding a file flag (UF_COMPRESSED) which tells the VFS layer this file is compressed. The VFS layer then checks for files with the UF_COMPRESSED flag. When it sees that flag: It hides the resource fork from most/some API layers. When the file is opened, it decompresses the contents returning them as if it were a normal file. That last point means that a copy engine that's unaware that a file is compressed: cp decompressed the file, which ended up stripping the xattrs …ends up automatically decompressing it. Reordering things a bit: That I can only reproduce it when at the other end of the SMB connection there is a Mac, or if the volume at the other end is formatted APFS? Yes and no. The problem here is that the full range of SMB servers is EXTREMELY large and diverse. Similarly, you can have cases where you get exactly the same behavior for

App & System Services Core OS

2w

Reply to filecopy fails with errno 34 "Result too large" when copying from NAS

I'm confused. Earlier you wrote the resource fork should only exist on compressed files, and cp DOES copy those but in your last reply Use the Finder to do the copy, not cp and cp decompressed the file, which ended up stripping the xattrs This doesn't make sense to me... I tried creating a file with a resource fork as you suggested, but again I wasn't able to reproduce the Result too large issue. The file, an empty .txt file on my Mac (macOS 26.2) which I added a 14.1 MB resource fork to, now displays as 14’136’946 bytes (14.1 MB on disk) in the Finder. Copying it to the FAT volume (inserted in my router and connected via SMB to my Mac) with the Finder, the cp command, or the test app I showed at the beginning which uses copyfile: they all worked, and the Finder displays the destination file as 14.1 MB. The only error I got was when trying to add the resource fork to an empty file created on the SMB volume: cat: stdout: Operation not permitted So I copied the file with the resource fork on m

App & System Services Core OS

2w

Reply to My app seems to cause Time Machine errors

Might the document's size be an issue? They tend to be over 100 Mb. It's certainly not ALL the documents that I open: only a few. Possibly. The data object you're handed was created by passing NSDataReadingMappedIfSafe into the NSData initializer, which means you do have a certain connection to the file system. However, the bigger issue is whether or not you have unsaved changes. It's worth saying that I've deliberately switched off the auto-save functionality (autosavesInPlace = false). Can I ask what you mean by checking the documentEdited property“? NSDocument.documentEdited is the property which notes whether or not the document has been modified, which would generally indicate there are unsaved changes. Among other properties, it's actually what triggers this alert: If I close a document with unsaved changes, it flags an alert saying that there are unsaved changes; do you want to save them? If there aren't, then the document closes gracefully. I'll see if I can trigger it again and investigate a bit. Aga

App & System Services Core OS

2w

Reply to filecopy fails with errno 34 "Result too large" when copying from NAS

I ran the following commands in Terminal: Use the Finder to do the copy, not cp. More to the point, jumping back to what I posted in earlier, this pattern (logical size > physical size) is the easy way to check if you're looking at a compressed file: Get Info: Size: 56,090 bytes (45 KB on disk) Similarly: I tried copying the same System/Library/CoreServices/Finder.app/Contents/Resources/Invitation.aiff file to a FAT volume connected via SMB, and the results are the same. The system is ACTIVELY trying to prevent compressed files from leaking out of its control. Basically, it will only preserve compression when you're doing local copies to file systems that specifically support it. That means APFS-> APFS and MAYBE HFS+. Note that this does NOT include smb. If you start with a compressed file and copy it across smb, the system ends up decompressing it as part of the copy. That's almost certainly what happened here: but the output of each of these commands was empty, so again it s

App & System Services Core OS

2w

Reply to filecopy fails with errno 34 "Result too large" when copying from NAS

I ran the following commands in Terminal: cp /System/Library/CoreServices/Finder.app/Contents/Resources/Invitation.aiff ~/Downloads/Invitation.aiff xattr ~/Downloads/Invitation.aiff chflags -v 0 ~/Downloads/Invitation.aiff xattr ~/Downloads/Invitation.aiff but the output of each of these commands was empty, so again it seems that even with the chflags -v 0 Invitation.aiff command no extended attributes are revealed on that file. I tried copying the same System/Library/CoreServices/Finder.app/Contents/Resources/Invitation.aiff file to a FAT volume connected via SMB, and the results are the same. I'm afraid we'll never know how that file (and hundreds others) got to the SMB volume. The user told me they're currently unable to reproduce the issue and are tired of running experiments, so I guess that's it for now... until I'll hear from the next user having the same issue. I have lost count of how many users have already contacted me about the exact same issue and how many days I've already spen

App & System Services Core OS

2w

Reply to NSFileSandboxingRequestRelatedItemExtension: Failed to issue extension

Since my AppStore app works, I must oversee something little that has this big effect. I can't otherwise explain the negative result. I have setup a super simple Git project here: https://github.com/vrunkel/RelatedFileTest I took a look at your sample and I'm not sure what's going on here either. Can you file a bug on this and then post the bug number back here? __ Kevin Elliott DTS Engineer, CoreOS/Hardware

App & System Services Core OS

2w

Reply to Any (developer) option to override log quarantine?

Apologies I meant to ask about activity tracing as well (they are related to this topic but if we think another forum post is better I can do it too). At certain point this also became one of the directions we wanted to explore but we've only uncovered more questions. The related documentation stated something but very vaguely. https://developer.apple.com/documentation/os/generating-log-messages-from-your-code?language=objc#Choose-the-Appropriate-Log-Level-for-Each-Message If an activity object exists, the system captures information for the related process chain We had hoped that this would somewhat play into the speculative logging approach we had touched upon, in the sense that if we try to log an error or fault within an activity, then it helps to capture and persist other logs on the activity chain even though they are originally not meant to be. But unfortunately from our test it didn't seem to be behaving towards that understanding. Then our question is, if we may ask - what are the exact additional in

App & System Services Core OS

2w

Reply to HomePod mini temperature sensor in HomeKit with Mac Catalyst

Thanks a lot! As for simulating an accessory on iOS isn't really all that useful I guess in my specific case this would not be a big problem, for I can either — for the time when I actually need to observe those automations, which would be limited to days, weeks at worst — keep my app foreground on an iPad; or simply run my application on a Mac, where there are no background-execution limits at all, far as I know. Thus, unless I overlook some other hurdle, this would be OK. I am a bit wary of the “large-scale projects” though: for me, this functionality is not extremely important (rather “just a bit helpful”), and if the only way to achieve it would mean to write, test and maintain heaps of complex code, I can do without (e.g., for automations triggered by HMCalendarEvents I've already wrote a tool which reads the fireDateComponents and then simply keeps track of the time; whilst there of course could be a small difference betwixt the time the trigger assumed to fire and the moment it actually did, u

App & System Services Hardware

2w

Reply to filecopy fails with errno 34 "Result too large" when copying from NAS

Thanks for all the details and the funny anecdote. I'll ask the user to run the cp command, but they told me they have some other work to do at the moment and need a break. In the meantime, since you said it's a SMB issue, is there a way I can reproduce the Result too large myself? Yes. To start with here: Setting a large resource fork like mentioned in that StackOverflow post causes the mentioned error Argument list too long. Was this on your SMB target or on your local (APFS) volume? If this is happening on the local volume, then I think the problem is that you're hitting the max transfer size limitation of fsetxattr. You need to break the transfer up into smaller individual segments, as copyfile does here. As a side note here, there's an open question here as to how the problem file originally got to the SMB server. On modern systems, we primarily use the resource fork to store compressed data (as I described above), but we also got out of our way to NOT export that configuration

App & System Services Core OS

2w

CKSyncEngine initial sync on a new device

I have implemented CKSyncEngine synchronization, and it works well. I can update data on one device and see the changes propagate to another device quickly. However, the initial sync when a user downloads the app on a new device is a significant issue for both me and my users. One problem is that the sync engine fetches deletion events from the server. On a new device, the local database is empty, so these deletions are essentially no-ops. This would not be a big problem if there were only a few records or if it was fast. I measured the initial sync and found that there are 150 modified records and 62,168 deletions. Counting these alone takes over five minutes, even without processing them. The deletions do nothing because the local database has nothing to delete, yet they still add a significant delay. I understand that the sync engine ensures consistency across all devices, but five minutes of waiting with the app open just to insert a small number of records is excessive. The problem would be wors

App & System Services iCloud & Data CloudKit Cloud and Local Storage

4

0

259

2w

smb big sur

Post

Replies

Boosts

Views

Activity