“translate scheme”

But when I use the newer API (that you say is identical to the old, or rather that the 'old' API translates to the newer) This caught my eye so I went back over your code and the problem is that you're NOT making the same API call. Here is the code from your original post: res = es_mute_path(self.esClient, [mutePath UTF8String], ES_MUTE_PATH_TYPE_TARGET_LITERAL); You passed ES_MUTE_PATH_TYPE_TARGET_LITERAL, which means: ES_MUTE_PATH_TYPE_TARGET_LITERAL-> The command targets this specific You should have passed ES_MUTE_PATH_TYPE_LITERAL, which means: ES_MUTE_PATH_TYPE_LITERAL-> The executable path is I actually copied that mistake in my previous reply so, correcting my mistake, these calls are direct equivalents. res = es_mute_path_literal(...); and res = es_mute_path(..., ES_MUTE_PATH_TYPE_LITERAL); Finally, on this point: I don't know how to extract a simple C project to demonstrate the issue, because my code is big and quite complicated, but I will make an attempt to provide such a sample. Th

The goal is to play facial expressions (like blinking or talking) while a body animation (like waving) is playing. I'm actually working on something similar, wondering the same question. Model imported from usdz with a list of animations (walk, idle, etc). E.g. entity.playAnimation(animations[index], transitionDuration: 0.2, startsPaused: false) I can manipulate joints for the neck or jaw programmatically to adjust the model. By doing: // input variable mouthOpen: Float let target = Root_M/.../Jaw_M var newPose = basePose guard let index = newPose.jointNames.firstIndex(of: target) else { return } let baseTransform = basePose.jointTransforms[index] let maxAngle: Float = 40 let angle: Float = maxAngle * mouthOpen * (.pi / 180) let extraRot = simd_quatf(angle: angle, axis: simd_float3(x: 0, y: 0, z: 1)) newPose.jointTransforms[index] = Transform( scale: baseTransform.scale, rotation: baseTransform.rotation * extraRot, translation: baseTransform.translation ) skeletalComponent.poses.default = newPose cre

The edge cases and qualifiers you provide here are very far from my needs. Most executables I want to mute are well protected by SIP, and will never move (MacOS private frameworks, daemons etc. plus few third-party that are also very well defined). My issue is very blunt. I mute a simple and perfect executable path. Here are some - my list is much longer, but you'll get the idea: +(NSSet *) baseBinaryPathWhitelist { static NSSet *_baseBinaryPath = nil; // any executable in these specific paths will be ignored static dispatch_once_t onceToken; dispatch_once(&onceToken, ^{ _baseBinaryPath = [NSSet setWithArray: @[ NSProcessInfo.processInfo.arguments[0], // don't inspect our own ITProtector process. @/sbin/launchd, @/bin/launchctl, @/bin/ps, @/bin/sleep, @/usr/bin/dscl, @/usr/bin/log, @/usr/bin/vmmap, @/usr/sbin/syslogd, @/usr/sbin/spindump, @/usr/sbin/usernoted, @/usr/sbin/securityd, @/usr/sbin/ipconfig, @/usr/libexec/biomesyncd, @/usr/libexec/logd]; But when I use the newer API (that you say is identical t

The URL loaded as part of ASWebAuthentication is not redirecting back into our application with Universal Link option, however it works perfectly with CustomURL scheme. Universal Link in combination with ASWebAuth is the issue and area of the concern. Does Universal Link and ASWebAuth combination to get the redirection is known issue in Apple ? Thank you.

You make no mention of where you are looking in Xcode for the option. First, you need to add the StoreKit configuration file to your project properly. Use Xcode -> File -> New -> File from template... Then on the template screen, scroll down to the Other section and select StoreKit Configuration File. Once that file is setup, you make use of it by going to Xcode -> Product -> Scheme -> Edit Scheme. Then select the Run/Debug tab on the left. Then select the Options tab on the right. There you will see the StoreKit Configuration option where you can select the configuration file you created as described above.

Hello, apologies for the late reply. Yes, indeed, the API is not working if the Translate app is not installed, even if the languages' dictionaries are downloaded through the settings. I will file a bug report soon. Thanks a lot about the video reference - good to know that I can check the availability of languages.

There are limits to how much I can help you with your third-party tooling; if you need help with those, I recommend that you raise this via the support channel for those tools. Still, I wanted to offer some insight into the overall issue here. Both of your crash reports suggest that you have a memory management issue. You’re crashing deep in Apple libraries as they try to work with Objective-C objects. I have a couple of suggestions on that front. First, you’re encountering this problem on TestFlight but it’s unlikely to be TestFlight related. I suspect that it’s actually tied to your Debug vs Release build configuration. When you test at your desk you use the Debug build configuration, but when you submit to the App Store you use the Release build configuration. It’s very common to see memory management problems like this show up only in the Release configuration. You can tease these apart using the Xcode organiser. See Isolating Code Signing Problems from Build Problems. You can also tweak your project to b