“translate scheme”

I changed the device language to Spanish (for an app localized for Spanish), and this is what I got: ibb.co/jLZx3VH Everything is localized correctly except for the Choose 1 to 7 invitees text.In your screenshot, all the text is English, which is different from what I got. What device language are you using? And what languages is your app localized for?Regardless, all the text should be translated by Apple, and it looks like some translations are missing. You should file a bug report for the translations to be added.

did you use Google Translator?

I realized having headAnchor = worldTracking.queryDeviceAnchor(atTimestamp: CACurrentMediaTime()) right after the run ar session is problematic, I moved this line to system component in Immersive view, it works fine now. root.components.set(ClosureComponent(closure: { deltaTime in let headAnchor = tracking.worldTracking.queryDeviceAnchor(atTimestamp: CACurrentMediaTime()) let translation = ConvertTrackingTransform .GetHeadPosition(headAnchor) sphere.transform.translation = translation // print(Head position (translation)) }))` I also got scene reconstruction to work at the same time.

Thank you for checking out the Translation API and letting us know what you think. While the Translation APIs do need to be triggered from SwiftUI, there's still a straightforward workaround to get this working from a mostly UIKit (or AppKit) app. You can add UIHostingController (or NSHostingController) to the place in your app you want any translation UI to present from. You can add the .translationPresentation or .translationTask modifier to a simple SwiftUI view, even though most of your app doesn't use SwiftUI.

Rosetta 2 only translates 64bit Intel binaries to work on Apple Silicon. You can find out more about the translation and the limitations in this Rosetta 2 support article - https://developer.apple.com/documentation/apple_silicon/about_the_rosetta_translation_environment.

Reviewing the documentation and WWDC session I don't see anything about the Translation framework requiring the Translate app being installed. Unless I missed something, this could be bug. However, the settings area for the Translate app appears to be he place where you manage and download languages to available to the Translation framework. Are you making appropriate checks to make sure the languages you are trying to use are installed and available for translation? Please see the directions starting at ~ 12:00 in the following presentation for how to check if a language is available: Meet the Translation API If those checks fail, you can present directions for the user explaining how to fix the problem instead of crashing. If that does not help, our engineering teams need to investigate this issue, as resolution may involve changes to Apple's software. Please file a bug report, include a small Xcode project and some directions that can be used to reprodu

Resolution Incase anyone stumbles on this, here's our solution to can't use if-statements in .translationTask(configuration) Originally I built a ViewModifier to switch between conditions (download only, or perform translation); but that didn't work for our use case. View Modifiers redraw the view causing TextEditors to lose their focus, which would not work for us. I landed on making a second TranslationSession.Configuration one for checking if language is downloaded, one for performing the translation. We check which to execute when the user taps the translate button: Two Configurations device owner is translating to @State var configurationForDownloadCheck: TranslationSession.Configuration? @State var configuration: TranslationSession.Configuration? Check which to run .onTapGesture { Task { // check if languages are downloaded and set control var let languagesFullyDownloaded = await translationLanguageIsDownloaded(from: nativeLanguageCode!, to: guestLanguageCode!) perfor

I’ll second that request. I would definitely be interested in access to the underlying on-device api that the new iOS 14 translate app uses. I’m currently using google translate via firebase, but would prefer to get rid of this dependency.

Is there a clear timeline for Apple to introduce a standalone Translation API? Many use cases require translation to be handled outside the UI layer. Why hasn’t Apple provided a lower-level API to enable broader integration and flexibility?

What translation mechanism are available in iOS?