I'm pretty sure I'm missing something completely obvious, but I can't see what. I watched WWDC session, read the Swift evolution blog, and they all make sense, but still it doesn't click for me. Please help me out here :) . I'm diving into adopting the 'new' async/await style of coding (I know, it's old news at this point, but I could only get to it now), and so I'm all pumped to get my code to go eleven and therefore I wrote a small data-downloader class. It has one method, well two: one oldskool function with a completionHandler, and one new style async/await one. When using the oldskool one, it works as everyone would expect: print(1) dataFetcher.fetchSomeData { print(2) let data = $0 // process data ... print(3) } print(4) The output is, unsurprisingly: 1 4 2 3 Now, when I use my new style function: let data = await dataFetcher.fetchSomeData() // process data ... Xcode gives me an error: 'async' call in a function that does not support concurrency That makes sense, I am calling this in the viewDi
missing package product
42,946 results found
Post
Replies
Boosts
Views
Activity
Hi Quinn, I have tried the installation of my package on a fresh macOS 14.5 VM. Downloaded the package, disconnected the network. I could install and launch the application without any issue. I did not observe the firewall popup as well. I have tried following command on the app and bundle as well. These commands executed successfully. spctl -a -t exec -vvv codesign -vvvv -R=notarized --check-notarization On other machines, I could see the firewall popup for the same . Regards Prema
The most common cause of this is a missing intermediate. See Fixing an untrusted code signing certificate. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com
[quote='794989022, jalkut, /thread/759366?answerId=794989022#794989022, /profile/jalkut'] I'll try it in a VM first... [/quote] That’s the approach I recommend. See Testing a Notarised Product for an example of the process I use. I’ve seen a lot of folks suggest a lot of hacky solutions to problems like this. Frankly, I’m not a fan of those because they make it hard to tell whether the behaviour you’re seeing is what your users will see or just an artefact of your hackery. Ripley I say we take off and nuke the entire site from orbit. [dramatic pause] Ripley It’s the only way to be sure. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com
[quote='794939022, Ferdinand-Activate, /thread/759185?answerId=794939022#794939022, /profile/Ferdinand-Activate'] Is there a way to do pinning without it going through SSL_CTX_set_custom_verify? [/quote] What pinning? In the example from my previous post, there’s no pinning at all. Rather, the program is just calling standard Apple APIs. [quote='794939022, Ferdinand-Activate, /thread/759185?answerId=794939022#794939022, /profile/Ferdinand-Activate'] Does NSPinnedDomains goes through SSL_CTX_set_custom_verify eventually? [/quote] As I demonstrate above, all TLS trust evaluation on our system goes through that call. [quote='794939022, Ferdinand-Activate, /thread/759185?answerId=794939022#794939022, /profile/Ferdinand-Activate'] It is a requirement … to not be intercepted by hackers and scripts to bypass this SSL pinning checks. [/quote] I see a lot of this and IMO this issue here isn’t your code but your security requirements. If someone attacking your app is able to intercept the code path between your app cal
It was fantastic news to hear, last year, that Xcode was getting a Vim mode. Apple's implementation of it was a great first step, but it was missing a bunch of key features. Most importantly the dot command (and by, extension, macros) and creating marks in files, which are functions that I use/rely on on a daily basis. I thought I would finally be able to stop having to self-sign Xcode (which causes problems) in order to use XVim2 plugin, but no such luck. Will these features get added in for Xcode 14 (they don't seem to be in the beta) or are they far out on the roadmap?
I was trying to load an Entity by Entity(named: sceneName, in: realityKitContentBundle), which works for many of my .usda file. But this time I got an error: Error loading asset from scene PinballTable.usda: failed to load '7058602595919186152 Scene (RealityFileAsset)Bundle/RealityKitContent-RealityKitContent-resources/RealityKitContent.reality/Scene_14.compiledscene' (Asset provider load failed: type 'RealityFileAsset' -- Failed to load compiled data for asset path 'Scene_14.compiledscene', due to error: Failed to deserialize asset data.) Any ideas on why this won't work? I have checked the size of my .usda file it's around 42kb so I won't think it's sake of file size. Due to many .usda reference inside of this scene, I suspect that it might be the case the bundle cannot locate other usda reference. So I export the whole scene into .usdz file and it turns to 118kb. Wonder if this could be the only issue here that affect the loading result but this is what I have tried so far. visionOS System: visionOS beta 2
Thank you @ssmith_c. I had followed the same steps before the forum post to diagnose the problem, and we both observed the same results. Unfortunately, I am having a hard time explaining this to the App review team. It has been two weeks. I requested code-level support, appeal, and rejection clearance, but these are not working as they should. At this rate, it may take a month for them to admit they are wrong, and a simple sorry shouldn't be an answer to the financial losses caused by the delay of the software to market.
Hi, Two years ago we launched a business for readers and writers. People buy a subscription through our website, where they also upload books, articles, journals, etc. They are then directed to download either the iOS or Android apps where they can read the content writers have uploaded. The App also includes social functions allowing members to leave reviews, create discussions on each piece of writing, etc. When reviewing the Apple Developer guidelines, we were confident we met the definition of a ‘Reader’ App (defined by Apple as an App whose primary purpose is to access previously purchased content, being books, magazines, music, videos, etc). We completed the External Link Request process as a Reader App and were successfully provided the exemption authority. However, in our latest version update (one that includes a critical bug fix stopping us from promoting the business until it is fixed) we were rejected on the basis that the reviewer considered any inclusion of additional functionality automatically
Hi! I'm running into a warning from a SwiftUI.DynamicProperty on a 6.0 development build (swift-6.0-DEVELOPMENT-SNAPSHOT-2024-03-26-a). I am attempting to build a type (conforming to DynamicProperty) that should also be MainActor. This type with also need a custom update function. Here is a simple custom wrapper (handwaving over the orthogonal missing pieces) that shows the warning: import SwiftUI @MainActor struct MainProperty: DynamicProperty { // Main actor-isolated instance method 'update()' cannot be used to satisfy nonisolated protocol requirement; this is an error in the Swift 6 language mode @MainActor func update() { } } Is there anything I can do about that warning? Does the warning correctly imply that this will be a legit compiler error when 6.0 ships? I can find (at least) two examples of types adopting DynamicProperty from Apple that are also MainActor: FetchRequest and SectionedFetchRequest. What is confusing is that both FetchRequest^1 and SectionedFetchRequest^2 explicitly declare th
I'm seeing this same error from Xcode_16_beta_3. Is there anything that can be communicated to engineers about the future direction of DynamicProperty? It seems like the type of work that could be expected to be on main… is the explicit MainActor requirement on DynamicProperty coming later before the new OS goes to production?
Thanks James. I see the Timeline feature is available in XCode 16 Beta (I was using XCode 15). Unfortunately when I try to install XCode 16 Beta I get this error, Loading a plug-in failed. The plug-in or one of its prerequisite plug-ins may be missing or damaged and may need to be reinstalled.. I guess that's an issue for a new post. I'll report back once I can get the software working.
Hi donezio, Apologies you are hitting this blocker. I had seen something similar to this sporadically in development, but I have not been able to reproduce this on my end in recent times. In the past, a combination of restarting Xcode, deleting DerivedData, and selecting Package Dependencies > Reset Package Caches worked to get me back on track. Another thing to try is to select the Studio scheme to build the Studio package on its own. Regardless of whether you can work around this, please file a Feedback request using the Feedback Assistant app. This will allow us to get to the underlying bug, or determine if it is already fixed in a newer release. Keep us updated if you are able to get around this. Thanks!
Thanks for sharing your post and the error message. From the detailed error log, it's not clear that the issue has come from the PDFDocument.h file, even though it manifests in another component. This suggests that the problem might be rooted in the class importation of the PDFKit framework. Specifically, the error message on line 26 of PDFDocument.h points out that it expects an identifier or '{', which hints at a missing brace { probably in one of the following locations: in your code where you import the PDFKit framework. in the header file of the component causing the error (NSImage+Additions.h). Here's the exact line where the error seems to be at: PDFDocument.h:26. But it can be in the nested file. Please, do post your relevant code snippets, especially where you import PDFKit and include other header files, so that we can take a closer look. This will enable us to identify the exact missing brace and assist you in resolving the issue. It might also be helpful to double-check that you
hi. I think you should provide more log data from the failing build process. did you made changes in build settings about compiler optimization flags/settings? maybe overwritten by mistake some values? compare with other easypeasy sample project…any difference in build settings? same result? check build setting: SWIFT_OPTIMIZATION_LEVEL -Onone is to my knowledge more or less the default setting. so if missing, just create/modify the entry in the project build settings.