How to localize FileProviderUI Action name?
| Originator: | henriqueponde90 | ||
| Number: | rdar://34397618 | Date Originated: | 09/12/2017 |
| Status: | Closed | Resolved: | No |
| Product: | FileProvider Framework | Product Version: | iOS 11 GM (15A372) |
| Classification: | Bug | Reproducible: | Always |
Area: FileProvider Framework Summary: Unclear how we can localize the action name for one of the FileProviderUI custom actions. The name is defined in an info.plist and it is unclear what key to use for an infoPlist.strings file. Since there can be multiple actions and they are added to an array under `NSExtension/NSExtensionFileProviderActions` and under the key `NSExtensionFileProviderActionName` inside each item. Simply having `NSExtensionFileProviderActionName` on `infoPlist.string` doesn't seem to work. Steps to Reproduce: Build the app in another language and see the FileProviderUI action not be localized. Expected Results: Expected a way to localize FileProviderUI actions Actual Results: The title of the action is not localized. Version/Build: iOS 11 GM (15A372) Configuration: Xcode 9.0 GM (9A235 ) iPhone X Simulator
Comments
Please note: Reports posted here will not necessarily be seen by Apple. All problems should be submitted at bugreport.apple.com before they are posted here. Please only post information for Radars that you have filed yourself, and please do not include Apple confidential information in your posts. Thank you!
Answers
Apple Developer Relations - October 18 2017, 10:35 PM
Engineering has provided the following feedback regarding this issue: We don’t have a solution for you currently. The most probable course of action is that we will end up asking you to localize you action name in Localizable.strings, not InfoPlist.strings. If you do that (and the plan does not change), then your action name will be localized once the original bug here (34197258) gets fixed. This is a dupe but we’re holding on to it and not closing it for now but we wanted you to know that it has been analyzed and we’re working on the original so that you can do something about this once the dupe gets fixed.
Apple Developer Relations - October 25 2017, 7:08 PM
Engineering has determined that your bug report is a duplicate of another issue and will be closed. The open or closed status of the original report your bug was duplicated to appears in a text box within the bug detail section of the bug reporter user interface. For security and privacy reasons, we don't provide access to the original bug yours was duped to. If you have any questions or concerns, please update your report directly at this link: https://bugreport.apple.com/.