Post not yet marked as solved
I have an app which uses SwiftUI and Mac Catalyst. When running on a Mac I want to provide a preferences menu entry with the usual keyboard shortcut Command + ,. An implementation via the Settings bundle is out of question since my preferences are too complex for this. Here is a reduced example of my implementation: import SwiftUI @main struct PreferencesMenuTestApp: App { @UIApplicationDelegateAdaptor private var appDelegate: AppDelegate var body: some Scene { WindowGroup { ContentView() } } } class AppDelegate: UIResponder, UIApplicationDelegate { override func buildMenu(with builder: UIMenuBuilder) { let preferencesCommand = UIKeyCommand(title: Preferences…, action: #selector(showPreferences), input: ,, modifierFlags: .command) // let preferencesCommand = UIAction(title: Preferences…) { action in // debugPrint(show preferences) // } let menu = UIMenu(title: Preferences…, options: .displayInline, children: [preferencesCommand]) builder.insertSibling(menu, afterMenu: .about) } @objc func sh
Post not yet marked as solved
I am trying to access API of Apple Music API > https://developer.apple.com/documentation/applemusicapiAfter creating the JWT developer token, when i try to access the API, An error of 401 - Unauthorized occurs. I am doing it in the following way : 1) Registering a new music identifier > https://help.apple.com/developer-account/#/devce5522674?sub=dev0416b90042) Creating a MusicKit identifier and private key > https://help.apple.com/developer-account/#/devce5522674 also downloading the private key file. 3) Getting the Kid (Key Id) and issuer (Team Id) . 4) Running the following code to generate the token : const jwt = require(jsonwebtoken); const privateKey = fs.readFileSync(AuthKey_KEY_ID.p8).toString(); const teamId = TEAM_ID_HERE; const keyId = KEY_ID_HERE; const jwtToken = jwt.sign({}, privateKey, { algorithm: ES256, expiresIn: 120d, issuer: teamId, header: { alg: ES256, kid: keyId } }); console.log(jwtToken);And after that checking the code using the curl command : curl -v -H 'Authorizati
Post not yet marked as solved
I recently encountered a difficult-to-diagnose bug in an app that I'm working on, and I thought I would share it with the Apple Developer community. The app that I'm working on is an iOS app that uses Core Location's Visit Monitoring API, and it is essential that the app is able to process incoming visits while running in the background. However, after real-world testing, I discovered several crash reports which were difficult to understand, as SwiftUI symbols are not symbolicated on debug builds. Eventually I discovered that the app was crashing when calling an @EnvironmentObject property of the root ContentView from that view's body when the app was launched directly into the background from not running at all. After creating a small test app to isolate the problem, I discovered that any environment object declared in the App struct and referenced from the root ContentView causes the crash, with the exception message: Fatal error: No ObservableObject of type ArbitraryEnvObject found. A Vie
Post not yet marked as solved
As far as the suppression file is concerned, you'd want to put the suppression file in the bundle. But even after that, it's possible there are entries that need to be fixed in the suppression file. If you'd like us to take a look, can you open a bug report with us and provide the following information: What does the backtrace of the runtime issue look like in the issue navigator ? If you are willing to do so, can you provide the symbolicated backtrace in the bug report ? A screenshot and a copy-paste of the backtrace from the issue navigator would be helpful. If your code uses languages that mangle symbol names, can you run symbols on macOS and provide the raw mangled symbols of your binary in the bug report ?
Post not yet marked as solved
Thanks, Quinn, for the explanation; I like the for fun stuff .. it makes perfect sense, and is a little obvious after the fact! In passing, I'll mention finding another way of defeating (which I won't be explicit about, though it's not too hard to find). Dropping a particular plist file into a particular /Library/Preferences/.. location enables opening for a command line app (and everything else). It's not useful to me (and neither is the config profile) because I need to ask someone else, with a wider range of models of the hardware I'm working with), to run my program. I won't ask someone else to open global holes in their security .. an app-local solution which only opens for that one app and only for the duration of its execution is essential. For my immediate need, I can wrap the command line into a trivial *.app. I'll file a bug and report the FB# here ..
Post not yet marked as solved
When viewing total downloads for an App in App Store Connect App Analytics, the option to filter Total Downloads by version is greyed out when clicking Add Filter even though the app has had a version change 1 week ago as shown in the App Store Version history. The version option is greyed out when running App Store Connect from Windows (using Firefox) and from a Mac (using Safari)
Post not yet marked as solved
Hi there Hosting in my server a no-doubt-well-formed AR file, as is the CosmonautSuit_en.reality from Apple's examples (https://developer.apple.com/augmented-reality/quick-look/) the infamous and annoying Object requires a newer version of iOS. message appears, even when I'm running iOS 17.1 in my iPad. That is, the very last available version. All works flawless in uOS16 and below. Of course, my markup is following the required format, namely: Accessing this same .reality file from the aforementioned Apple's site page works fine. Why is not working in my hosting server? For you rinformation, when I use in my server a USDZ instead, also from the Apple's web page of examples, as is the toy_drummer_idle.usdz file, all works flawless. Again, I'm using the same markup schema: Also, when I delete the rel=ar option, AR experience is launched, but by means of an extra step, that implied go thought an ugly poster (generated by QLAR on-the-fly), that ruins all the UX/UI of my webapp. This bahavior is, b
Post not yet marked as solved
We are working on a new iOS application utilizing the new iOS 17 APIs, and I have updated Xcode to Xcode 15 Beta, and my iPhone 12 Pro to iOS 17 Beta 2, though this issue was also present on iOS 17 Beta 1. In Xcode, for Signing and Capabilities I have my Team set to my personal team, utilizing the Automatically manage signing tick. While the app will build and install on my phone, I immediately receive this error, with no popup to trust the developer. Going to Settings > General > VPN and Device Management, I can see my Development Team, and I am able to Trust my team. When trying to then Verify App(s), it tells me it will use my internet connection to verify the application. However, it will then do nothing, with no error, regardless of how many times I attempt to verify. Trying to open the app from my home screen will result in the repeated Unable to Verify Error. Trying to reset network settings does not result in any change in this behavior, nor does a reset of the phone. I have tried 4 different hi
Post not yet marked as solved
This was mentioned in another thread 4 years ago: This whole discussion assumes that every network connection requires a socket. This isn’t the case on most Apple platforms, which have a user-space networking stack that you can access via the Network framework [1]. [1] The one exception here is macOS, where Network framework has to run through the kernel in order to support NKEs. This is one of the reasons we’re in the process of phasing out NKE support, starting with their deprecation in the macOS 10.15 SDK. Is macOS still an unfortunate exception that requires a socket per Network framework's connection?
Post not yet marked as solved
Hi, I'd really appreciate if anyone here could run my self-contained test above on their current macOS version to see if it matches my results or not. If you do please share your result here indicating the OS version and whether you have VPN installed or not (and whether it's activated or disabled).
Post not yet marked as solved
I'm seeing a similar problem. Here I'm using an ObservedObject to update my app settings but get a build warning in the Command section Main actor-isolated property 'body' cannot be used to satisfy nonisolated protocol requirement The app seems to compile and run fine otherwise. Feedback raised: FB13801673 struct MyCommands: Commands { @ObservedObject var globalAppSettings: GlobalAppSettings var body: some Commands { SidebarCommands() CommandGroup(after: CommandGroupPlacement.newItem) { Divider() Toggle(Debug Mode, isOn: $globalAppSettings.debugMode) } } }
Post not yet marked as solved
I have been working with a framework to add multiplayer support to my app. The app runs on test devices, simulators, and archives perfectly fine and the app is fine without the framework. But when I go to distribute the app, I see get this error related to the multiplayer framework I have added. I have tried updating the minimumOSVersion to 9.0, 10.0, 12.0, and 13.0 everywhere (info.plist, deployment info, build settings, etc) and they all match with each build/archive but no matter what I can't get fix this error. This error only shows up when I go to distribute the app to the store. Any ideas on what to try or how to fix this issue? I've attached a screenshot of the issue below.
Post not yet marked as solved
Hello, I am trying to debug Swift Concurrency codes by using Swift Concurrency Instruments. But in our project which has been maintained for a long time, Swift Concurrency Instruments seems not working. Task { print(async code) await someAsyncFunction() } When I run Swift Concurrency Instruments with the above codes in our project, I could check that the print works well by checking stdout/stderr Instruments, but there are no records on Swift Concurrency Instruments. But in the small simple sample project, I checked that Swift Concurrency Instruments works well. Are there any settings that I need to do for the legacy project to debug Swift Concurrency?
Post not yet marked as solved
Thank you for the answer. So far, I managed to implement the OTA enrollment mechanism. This includes the following steps for reference: User navigates to the first URL in order to start the enrollment process. User authenticates using the web view. Server returns a payload to request device attributes. Payload is signed using the trusted server certificate. Mobile device POST (first) the requested information. Payload is signed using the device identity certificate (issued by Apple). Server returns a SCEP payload to continue the enrollment process. Mobile device reaches the server to get the SCAP certificate authority. Mobile device reaches the SCAP endpoint with PKCS7 embedded CSR to get signed. Inbound payload is decrypted using the SCEP certificate authority private key. Server returns a PKCS7 embedded X509 - SCEP issued certificate. Returned payload is signed using the certificate extracted from the inbound SCEP request. Returned payload is signed using the SCEP authority. Mobile device POST (second) usin
I'm using Apple Clang to build a C++ project from the terminal. The following lines are printed when building the project: -- The C compiler identification is AppleClang 15.0.0.15000100 -- The CXX compiler identification is AppleClang 15.0.0.15000100 clang --version and gcc --version commands show me the following: Apple clang version 15.0.0 (clang-1500.1.0.2.5) Target: arm64-apple-darwin23.3.0 Thread model: posix The next function, while valid with other compilers, displays an error for Apple Clang: std::vector read_file() { return {}; } error: non-aggregate type 'std::vector' cannot be initialized with an initializer list return {}; My questions: Am I on the latest Apple Clang version? If not, how can I upgrade to it? So far, I've tried: xcode-select --install command, the result: xcode-select: note: Command line tools are already installed. Use Software Update in System Settings or the softwareupdate command line interface to install updates softwareupdate -l command, the result: Software Update T
RayWo.
