Login Start for Free

Blog • How-to?

Localising an iOS watch app extension with the Applanga CLI

Keeping your iOS watch app extension Localised with the Applanga CLI is a quick and painless experience.

Published on 15 November 2019

Written by Richard

Keeping your iOS watch app extension Localised with the Applanga CLI is a quick and painless experience.

Once you have your base app localisation setup to use string files, add the WatchTarget as a target for those files, that way you will be able to access the strings via their keys in your watch app.

If you've read the Applanga CLI Documentation you know that in order to localize files with it you need to specify them in the configuration file (.applanga.json) and for your Localizable.strings to be included in the configuration you're config should look something like this:

{
  "app": {
    "access_token": "YOUR_ACCESS_TOKEN", 
    "base_language": "en",
    "pull": {
      "target": [
        {
          "exclude_languages": [
            "en"
          ],
          "file_format": "ios_strings",
          "path": "./<language>.lproj/Localizable.strings",
          "tag": "app:Localizable.strings"
        }
      ]
    },
    "push": {
      "source": [
        {
          "language": "en",
          "file_format": "ios_strings",
          "path": "./en.lproj/Localizable.strings",
          "tag": "app:Localizable.strings"
        }
      ]
    }
  }
}

So, now after making changes on the Applanga Dashboard whenever you call applanga pull your watch extension will pickup all the latest translations.

A simple example app can be found here: https://github.com/applanga/IosWatchExtentionExample

Related Articles