Post not yet marked as solved
Thank you very much, Quinn, We need to set the thread priority for our streaming engine. Our unit tests are testing its modules - beneath other things - with all kinds of (unrealistic) sample rates. And it tries to set thread priorities for standard sample rates like 44.1kHz, 48kHz, ..., 192kHz, etc. while setting up the streaming engine to run on block sizes from 1 sample to something like 16384, which means the thread needs to be set up for computation down to every 1/44100, 1/192000 sec, etc. IIRC setting the thread_policy below 4/44100 fails. Although this is (for our current tasks) not a very realistic scenario, I think it should work, at least I would like to know how low the unit tests can go, or even better be able to ask the specific machine about its valid thread_policy range.
Post not yet marked as solved
Hi everyone, I'm encountering an intermittent issue with my Xcode Cloud CI/CD pipeline when pulling Swift Package Manager (SPM) dependencies from AWS CodeArtifact. The build process occasionally fails with an SSL error, but other times it succeeds without any issues. This inconsistency is causing significant disruption to our continuous integration process. Environment: Xcode Cloud Swift Package Manager (SPM) for dependency management AWS CodeArtifact as the package registry Error Message: Error: registry login using https://xx-xx-xx.codeartifact.eu-central-1.amazonaws.com/swift/***/login failed: The certificate for this server is invalid. You might be connecting to a server that is pretending to be xx-xx-xx.codeartifact.eu-central-1.amazonaws.com which could put your confidential information at risk.. Would you like to connect to the server anyway?
Post not yet marked as solved
I faced a problem during development that I could not scan Code39 barcode with iPad using Vision. A sample label I used for test has multiple Code39 barcode on it and I could scan almost all barcodes except for specific one. And when I use conventional barcode scanner and free apps to scan barcode, I could scan the barcode with no problem. I failed to scan the barcode only when I use Vision function. Has anyone faced similar situation? Do you know the cause why specific barcode could not be scanned with iPad with Vision?
Post not yet marked as solved
I have a sample iOS app in Xcode that I run in the iOS 17.5 Simulator. It creates a WKWebView and configures a proxy via the ProxyConfiguration API, it works as expected unless the proxy tries to establish mTLS. It seems there is no way to handle the client certificate request when using a proxy. If I navigate to a page that requests mTLS without a proxy configured, it works as expected. Here is a minimal repro: #import ViewController.h #import @import Foundation; @import WebKit; @interface ViewController () @property (nonatomic,strong) WKWebView* webView; @property (nonatomic, strong) WKWebViewConfiguration * webConfig; @end @implementation ViewController - (void)loadView { [super loadView]; nw_protocol_options_t tls_options = nw_tls_create_options(); sec_protocol_options_t sec_options = nw_tls_copy_sec_protocol_options(tls_options); sec_protocol_options_set_challenge_block( sec_options, ^(sec_protocol_metadata_t metadata, sec_protocol_challenge_complete_t challenge_complete) { NSLog(@Inside of challenge b
Post not yet marked as solved
One of our apps got hit by the ITMS-91065: Missing Signature issue when we attempted to distribute it to externally via TestFlight. The email said FirebaseCore is missing the signature file within our own framework. After investigation, I realized our recent update to the version of Firebase that has the proper signatures and privacy manifest wasn't enough by itself. Similar to Apple's own instructions on embedding static frameworks since Xcode 15, Firebase instructs us to select the Embed & Sign option. After making the appropriate changes though, we're getting the error in Transporter: Asset validation failed (90085): No architectures in the binary Our setup is as follows: We have an analytics dynamic framework, which depends on Firebase's static framework. The Firebase related frameworks are embedded and signed in our analytics framework. Our app depends on the analytics dynamic framework, which now includes Firebase frameworks within its framework. Since the Firebase frameworks are static, on
Post not yet marked as solved
This issue is a bit strange. On one machine at work, attempting to use the Xcode 15.0 CarPlay simulator results in devices saying Accessory Not Supported. The redesigned 15.3 simulator crashes on launch. We have tried 5 different phones with USB C, Lightning to USB C, Lighting to USB A, etc and the same result occurs on all of the above. Taking the same phones and cables to 4 other laptops works fine. The non functioning machine connects to any other USB device just fine. We even tried different partitions, installing Xcode, different macOS versions, etc. There are some suspicious parts of the log on the non working machine: default 09:18:10.075726-0400 mobileactivationd Client certification requested by CarPlay Simulator error 09:18:10.088862-0400 CarPlay Simulator Failed to obtain valid certificates from server: error 09:18:10.103753-0400 CarPlay Simulator Incoming message ID 0xaa04 AuthenticationFailed and error 09:18:09.452387-0400 CarPlaySimulatorDeviceLink RemotePairing.framework is not availa
Post not yet marked as solved
Did anyone end up figuring this out? This is working fine on one of my machines, but not another. There are some suspicious parts of the log on the non working machine default 09:18:10.075726-0400 mobileactivationd Client certification requested by CarPlay Simulator error 09:18:10.088862-0400 CarPlay Simulator Failed to obtain valid certificates from server: error 09:18:10.103753-0400 CarPlay Simulator Incoming message ID 0xaa04 AuthenticationFailed and error 09:18:09.452387-0400 CarPlaySimulatorDeviceLink RemotePairing.framework is not available. default 09:18:09.452419-0400 CarPlaySimulatorDeviceLink RemotePairing.framework not found. Meanwhile the working machine according to Activity Monitor is loading /Library/Apple/System/Library/PrivateFrameworks/RemotePairing.framework/Versions/A/RemotePairing just fine. The non working machine does have that file on disk.
Post not yet marked as solved
Attaching error log below. Incident Identifier: 5CE05737-666A-4AD8-9BC5-D3ECD4CE2F71 Distributor ID: com.apple.AppStore Hardware Model: iPhone14,2 Process: App [482] Path: /private/var/containers/Bundle/Application/B0D2B0B9-831F-401F-B00D-E733A35D72BD/App.app/App Identifier: uk.co.bbc.cbeebiesplaytimeisland Version: 9.10.0 (5836) AppStoreTools: 15E204 AppVariant: 1:iPhone14,2:15 Code Type: ARM-64 (Native) Role: Foreground Parent Process: launchd [1] Coalition: uk.co.bbc.cbeebiesplaytimeisland [681] Date/Time: 2024-05-01 16:47:45.5386 +0100 Launch Time: 2024-04-28 20:20:20.0516 +0100 OS Version: iPhone OS 17.4.1 (21E236) Release Type: User Baseband Version: 3.50.04 Report Version: 104 Exception Type: EXC_CRASH (SIGKILL) Exception Codes: 0x0000000000000000, 0x0000000000000000 Termination Reason: RUNNINGBOARD 0xd00d2bad Triggered by Thread: 0 Kernel Triage: VM - (arg = 0x3) mach_vm_allocate_kernel failed within call to vm_map_enter Thread 0 name: Thread 0 Crashed: 0 libsystem_kernel.dylib 0x00000001d730
Post not yet marked as solved
I am trying to bring my iOS App to native macOS. I am using exactly the same TimelineProvider and widgets (the ones not supported on macOS surrounded by #if(os)). Running the whole app or just the WidgetExtension on iOS works perfectly fine. Running the mac app works perfectly fine apart from missing Widgets. When running the WidgetExtension on My Mac, the WidgetKit Simulator opens and only presents Failed to load widget. The operation couldn't be completed. (WidgetKit_Simulator.WidgetDocument.Error error 4.) The code compiles fine without any warnings, only a file path is printed into the console. file:///Users/myName/Library/Developer/Xcode/DerivedData/MyAppName-dfsiuexplidieybwvbkqofchxirp/Build/Products/Debug/MyApp.app/Contents/PlugIns/MyAppNameWidgetExtensionExtension.appex/ Shortly after I get a log entry Logging Error: Failed to initialize logging system. Log messages may be missing. If this issue persists, try setting IDEPreferLogStreaming=YES in the active scheme actions environment
Post not yet marked as solved
Hi, I have been receiving an email error message: ITMS-90426: Invalid Swift Support - The SwiftSupport folder is missing. Rebuild your app using the current public (GM) version of Xcode and resubmit it. when submitting an app to the App Store Connect using xcode. I have searched for many solutions online, but none of them have worked. Later, I manually created the SwiftSupport directory and copied the Swift dynamic library (dylib) that the app depends on to this directory, as well as copying them to the. app/Frameworks directory. After submitting, I received an email saying that these. dylib dynamic libraries are not in the. app/Frameworks directory. I opened the IPA file and checked the directory, and I really saw that they are located below. I don't know where the problem is, can you tell me the exact reason?
Post not yet marked as solved
The fact that this bug that's related to the core features of the SPM still exists after several versions of the IDE is mindblowing. Whenever I change branches, it starts to update dependencies altough all branches have the same .resolved file in them and failing to do so randomly is extremely frustrating. Closing Xcode before switching branches doesn't always work either. I have to randomly try resetting package caches multiple times and restarting the IDE several times to make it work again. A collosal waste of time.
Post not yet marked as solved
Sometimes upload fails. You have to reload again the specific image. yYou do not show the screenshots section, that would be useful.
Post not yet marked as solved
Hello, If you want to get approval from the Apple Store, you need to ensure that your dating app is unique and also provides a valuable environment for users. One of the reasons the app is rejected is because it failed to have a unique value proposition. You should ensure your app offers a distinct set of features or functionalities to stand out from the crowd. Other than that, here are some factors you shouldn’t overlook if you want to pass guideline 4.3: Ensure that your app actually addresses the needs of a particular/target group. Features are up to the market standards. Prioritize high-quality and visually appealing Design. Make sure to have transparency. To learn more in detail about how to submit your app to the App Store, check out this link: https://www.nimbleappgenie.com/blogs/submit-app-to-app-store/
Post not yet marked as solved
Hello Quinn, Your question: What are the array elements? My app comprises about 500 methods, many of them contain pairs of deprecated… -> Elements are NSStrings, NSArrays, NSMutableArrays, NSNumbers, NSSets, NSMutableSets I don't understand what you mean by I think you should take this opportunity to factor out the common code so that you only have one copy of your archiving code. What do you mean by common code? Do you mean deprecated code? … only have one copy of your archiving code? As already said in my previous reply: Your proposal works. I need to do a big job to change them all bit by bit. What is irritating is this Console feedback: *** -[NSKeyedUnarchiver validateAllowedClass:forKey:] allowed unarchiving safe plist type ''NSString' (0x1f30548c8) [/System/Library/Frameworks/Foundation.framework]' for key 'NS.objects', even though it was not explicitly included in the client allowed classes set: '{( 'NSMutableArray' (0x1f304d690) [/System/Library/Frameworks/CoreFoundation.framework] )}'. This will b
Post not yet marked as solved
App crash happens. Not sure about the reason. Could you please help me with this? Attached the complete crash log in a file Incident Identifier: 845F6892-F0C9-4090-9690-802CB9CA51B0 Hardware Model: iPhone11,8 Process: Asset [3649] Path: /private/var/containers/Bundle/Application/2433DB3D-1B7C-41E3-917B-A92FFFED95EC/Asset.app/Asset Identifier: com.mt.AssetPlus.SWDC.IN Version: 1.3.84 (20240416) AppStoreTools: 15E204 AppVariant: 1:iPhone11,8:15 Beta: YES Code Type: ARM-64 (Native) Role: Foreground Parent Process: launchd [1] Coalition: com.mt.AssetPlus.SWDC.IN [420] Date/Time: 2024-05-14 08:29:23.7648 -0700 Launch Time: 2024-05-14 08:28:50.8616 -0700 OS Version: iPhone OS 15.6.1 (19G82) Release Type: User Baseband Version: 4.04.02 Report Version: 104 Exception Type: EXC_CRASH (SIGABRT) Exception Codes: 0x0000000000000000, 0x0000000000000000 Exception Note: EXC_CORPSE_NOTIFY Triggered by Thread: 3 Kernel Triage: VM - Compressor failed a blocking pager_get VM - Compressor failed a blocking pager
