Search results for

apple pencil battery life

146,441 results found

Post

Replies

Boosts

Views

Activity

Reply to codesign stubbornly failing
[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. Identify whether that item is bundle
1d
Reply to App sometimes crashes when inserting String into Set with assertion ELEMENT_TYPE_OF_SET_VIOLATES_HASHABLE_REQUIREMENTS
[quote='862963022, Nickkk, /thread/804313?answerId=862963022#862963022, /profile/Nickkk'] Do you know what that is? [/quote] What what is? The vmhkb.mspwftt.com website? Nope, no idea. FWIW, a DuckDuckGo search for ELEMENT_TYPE_OF_SET_VIOLATES_HASHABLE_REQUIREMENTS (with the quotes) turns up this thread [1] and a related thread on Swift Forums. Amusingly, a DevForums search for the same string gives exactly the results you’d hope for (-: The search button on the Developer website proper is not as helpful )-: Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com [1] Well, indirectly. It actually takes you to the Programming Languages > Swift subtopic.
Topic: Programming Languages SubTopic: Swift Tags:
1d
Reply to Change default handler for tel URL scheme on macOS
Hmmm, that seems bugworthy to me. Have you checked this on the latest 26.1 beta? [2] If it’s still a problem there then, yeah, I reckon you should file a bug about that. If you do file a bug, 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 [2] Again, I’m sorry for not checking this myself. I’ve been OOO for a few weeks and am still wrangling a significant backlog.
Topic: App & System Services SubTopic: General Tags:
1d
DeclaredAgeRange import error in Mac Catalyst app
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 Catalyst (SDK 26+). Bu
6
0
194
1d
Reply to DeclaredAgeRange import error in Mac Catalyst app
[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
1d
Developer ID Notary Service - Outage
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.
1
0
250
1d
“In Progress” status stuck for over 21 hours with no result
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
4
0
306
1d
Reply to “In Progress” status stuck for over 21 hours with no result
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. nitroagility, As it’s been a week since you started this thread, I suspect that things are now unblocked. If not, reply here and I’ll take a proper look at this. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com
Topic: Code Signing SubTopic: Notarization Tags:
1d
Reply to “In Progress” status stuck for over 2 days with no result
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. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com
Topic: Code Signing SubTopic: Notarization Tags:
1d
Reply to Notarize stuck "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 > Notarization
Topic: Code Signing SubTopic: Notarization Tags:
1d
Reply to Notary service stuck for took long
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. As it’s been more than a week since you posted the above, I suspect that things are now unblocked. If not, reply here and take a proper look at this. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com
Topic: Code Signing SubTopic: Notarization Tags:
1d
Reply to Notary Tool credentials failing to stay persistently in the keychain
[quote='804029021, rapier, /thread/804029, /profile/rapier'] 2. These should remain in the keychain for as long as the user process is running (just like any other process) [/quote] I’m confused by this comment. They keychain is a per-user persistent database. Stuff you put into the keychain should stick around indefinitely, as long as you’re logged into that user account. Are you able to reproduce this when running these commands from Terminal? Or are you testing this only in some other environment, like a CI system or over SSH? Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com
1d
Notary Tool credentials failing to stay persistently in the keychain
The problem is the following: We create a keychain item called NotaryTool (There are multiple accounts that use Notary tool and we created it for all of them ) This is created in the following way: $ xcrun notarytool store-credentials This process stores your credentials securely in the Keychain. You reference these credentials later using a profile name. Profile name: NotaryTool We recommend using App Store Connect API keys for authentication. If you'd like to authenticate with an Apple ID and app-specific password instead, leave this unspecified. Path to App Store Connect API private key: //AuthKey_ABCDEFGH.p8 App Store Connect API Key ID: App Store Connect API Issuer ID: ABCDEF-ABCD-1234-1234-1234567 Validating your credentials... Success. Credentials validated. Credentials saved to Keychain. To use them, specify `--keychain-profile NotaryTool` The key is downloaded from Apple and some other IDs are provided alongside. These should remain in the keychain for as long as the user process i
1
0
98
1d