Localize libraries and sub projects with CocoaPods

If you wish to use the Applanga iOS framework in an Xcode subproject (dynamic or static lib), then you need to tell your Podfile about those projects. source 'https://github.com/CocoaPods/Specs.git' platform :ios, '9.0' #source "https://github.com/CocoaPods/Old-Specs" #link_with 'MyTestApp' def myPods use_frameworks! pod 'Applanga' end workspace 'MyTestApp.xcworkspace' target 'MyTestApp' do myPods end target 'MyStaticSubProject' do myPods project 'MyStaticSubProject/MyStaticSubProject' end target 'MyDynamicSubProject' do myPods project 'MyStaticSubProject/MyStaticSubProject' end The important part is to make sure you specify in the Podfile exactly where your target sub project is. That way it will install those pods for the sub project too. If you wish to localise a .strings file within a dynamic »

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. 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": [ { "file_format": "ios_strings", "path": "./<language> »