“apple pencil battery life”

[quote='820155021, alex_strong, /thread/820155, /profile/alex_strong'] I've had issues getting the dmg signed by the Apple notary service [/quote] That text suggests that you’ve misunderstood how notary works. The notary service doesn’t sign your product. Rather, you present it with a distribution-ready product, one that’s already signed, and the notary service checks it and, if all is well, issues a signed ticket. See Notarisation Fundamentals for more about how this process works. As to why the notary service is refusing to notarise your product, it’s hard to say without more info. It sounds like you were able to submit the product and get a response, but the status is Invalid, indicating a problem with your submission. In that case the next step is to look at the notary log. What does it say? See Fetching the Notary Log for info on how to get the log. [quote='820155021, alex_strong, /thread/820155, /profile/alex_strong'] The only big change we made this time was switching to Maven [/quote] Ah, Jav

[quote='820080021, nixx, /thread/820080, /profile/nixx'] I have submitted this via Feedback Assistant (FB22312299). [/quote] Thanks. I’m not sure what’s going on here, but it’s clearly a regression and thus warrants a bug report. Having said that, there’s a long-standing gotcha you need took out for. Using non-ASCII names for pure data should be fine, but you have to be careful when using non-ASCII names for files within a code-signed bundle. There’s a long-standing problem with that, as explained in this post. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

I want to be clear about terminology here: A load-time import is one that’s statically declared in the binary via the LC_LOAD_DYLIB load command. A run-time import is one that you do from code, using dlopen or some API layered on top of that. Beyond that, I’m going to use the terms from an An Apple Library Primer, and you should read before continuing. [quote='820251021, vd02, /thread/820251, /profile/vd02'] What is the recommended approach on macOS for this kind of explicit dynamic loading … ? [/quote] My recommendation is that you not do this. Apple platforms generally prefer load-time imports because it enables optimisations in the dynamic linker. Specifically, the dynamic linker can build and cache a closure for an app, reusing that closure the next time the app launches. Note We discussed this in detail in WWDC 2017 Session 413 App Startup Time: Past, Present, and Future. Sadly, it’s no longer available from Apple, but the core info is still available from third-party sources.

For 2 years our app was reviewed under 2 days. This time after a week we asked an urgent review because it contained important fixes. The worst part is that Apple is also blocking our work in Testflight. even after a week it is still under review. I submitted a new build and asked to review that one instead. Still nothing after two days. To me it seems Apple is having internal issues and we are powerless and can't work properly with our Testers.

Hello, Thanks for your response. Have you tested this? As I'm fairly sure that's what Numbers is doing. NSMetadataQueryUpdateRemovedItemsKey and NSMetadataQueryDidUpdateNotification which are iCloud Document API, have the following two limitations. Therefore, I believe Numbers uses other methods as well. On iOS, NSMetadataQuery cannot handle files stored in local storage. File changes can only be detected while the app is running. Also, and I should have mentioned this in my previous reply, make sure you're using file coordination for all of this. We found that it is possible to detect deletion of files in local storage while the app is running by using the NSFilePresenter API. However, these APIs unable to detect whether a file was deleted while the app was not running. If there is a better way than checking whether the URL contains “.Trash” to determine whether a file was deleted while the app was not running—like the method used by Numbers.app—we would like to adopt it in our app as well. That said, as you

I’m sorry but I don’t understand the question here. Are you asking for someone to provide the code that ‘answers’ that experiment? Or asking about how you actually experience with this within the Swift Playground app? Please elaborate. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

For context, that date was announced in Developer > WWDC26 > Special Event. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

Oh, and regarding the “sensitive language” issue, I’m sorry about the confusion there. I tracked it down to a misguided content filter [1], which has now been reeducated (i. 101267407). Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com [1] It didn’t like the word diploma.

I can actually reproduce that quite easily. But my biggest concern so far are other issues which makes me wondering if fskit is of production quality and should I continue making a fuse bridge with it. I got a couple of kernel panics while developing a new plugin. Can send logs if needed. With the passthrough fs: git clone which I usually use for filesystem validation and testing doesn't work: git clone https://github.com/arthenica/ffmpeg-kit.git Cloning into 'ffmpeg-kit'... remote: Enumerating objects: 11760, done. fatal: Unable to create temporary file '/Users/alexf/333/ffmpeg-kit/.git/objects/pack/tmp_pack_XXXXXX': Permission denied fatal: fetch-pack: invalid index-pack output With the passthrough fs: Recursive rm doesn't work either rm -rf ffmpeg-kit rm: ffmpeg-kit/docs/apple/html: Directory not empty rm: ffmpeg-kit/docs/apple: Directory not empty rm: ffmpeg-kit/docs/linux/html: Directory not empty rm: ffmpeg-kit/docs/linux: Directory not empty rm: ffmpeg-kit/docs/android/doc/html: Direc

Since adopting a newer AppStoreConnect API OpenAPI spec, the trailing '/' in the server was added back; this was something I manually patched last summer. Without the patch to remove the trailing '/', when used with the Swift OpenAPI Generator, a URL with two slashes is produced which was invalid against the SCOPE of the token evidently. Notice .com//v1 and the double slash. https://api.appstoreconnect.apple.com//v1/apps/1672441148/perfPowerMetrics There is nothing wrong with the App Store Connect API itself other than perhaps the scope should honor two slashes since the spec declares it? I submitted a feedback for this last summer to have the Apple minted OpenAPI spec remove the trailing slash in the server url. FB18389250 - AppStoreConnect API: OpenAPI spec file has a server trailing '/' which results in Swift OpenAPI Generator code to have paths with two slashes unexpectedly