I also thought that it would generate code for iOS (the enum code for iOS presented last week at CocoaheadsNL) but I only see the .strings files.

Yes, that does seem to work. When I now set the output path to some other folder it seems to completely ignore that and just puts it in the render folder of the working directory.

node path_to_localicious/bin/localicious render LocaliciousConfig.yaml . --platforms android --languages en

I've changed the contents to exactly that and now I get this:

❌ Something went wrong rendering.
Something went wrong.

The yarn install is missing from the Requirements and installation section so I didn't run that.

When I now run it, it still fails.

Am I supposed to run it with localicious render ./copy.yaml or localicious render ./LocaliciousConfig.yaml? Both result in different errors. I don't have a file named copy.yaml but the docs mention this so I'm not sure if it's supposed to be the output or input file.

When running localicious render LocaliciousConfig.yaml . --platforms android --languages en I get the following:

let result = Object.keys(data).map(key => {
                      ^

TypeError: Cannot convert undefined or null to object
    at Function.keys (<anonymous>)
    at aggregate (/Users/lwesterhoff/Developer/forks/localicious/src/actions/normalize.js:28:23)
    at /Users/lwesterhoff/Developer/forks/localicious/src/actions/normalize.js:17:24
    at Array.map (<anonymous>)
    at normalizeYaml (/Users/lwesterhoff/Developer/forks/localicious/src/actions/normalize.js:17:8)
    at render (/Users/lwesterhoff/Developer/forks/localicious/src/actions/render.js:10:24)
    at /Users/lwesterhoff/Developer/forks/localicious/src/actions/validateAndRender.js:14:22
    at Result.flatMap (/Users/lwesterhoff/Developer/forks/localicious/src/utils/result.js:42:17)
    at validateAndRender (/Users/lwesterhoff/Developer/forks/localicious/src/actions/validateAndRender.js:14:6)
    at Object.<anonymous> (/Users/lwesterhoff/Developer/forks/localicious/bin/localicious-render:44:1)

Contents of LocaliciousConfig.yaml:

shared:
  eneco:
    company:
      name:
        en: 'Test'
        nl: 'Test'

Running localicious gives me the following error:

internal/modules/cjs/loader.js:775
    throw err;
    ^

Error: Cannot find module 'commander'
Require stack:
- /Users/lwesterhoff/Developer/forks/localicious/bin/localicious
    at Function.Module._resolveFilename (internal/modules/cjs/loader.js:772:15)
    at Function.Module._load (internal/modules/cjs/loader.js:677:27)
    at Module.require (internal/modules/cjs/loader.js:830:19)
    at require (internal/modules/cjs/helpers.js:68:18)
    at Object.<anonymous> (/Users/lwesterhoff/Developer/forks/localicious/bin/localicious:2:17)
    at Module._compile (internal/modules/cjs/loader.js:936:30)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:947:10)
    at Module.load (internal/modules/cjs/loader.js:790:32)
    at Function.Module._load (internal/modules/cjs/loader.js:703:12)
    at Function.Module.runMain (internal/modules/cjs/loader.js:999:10) {
  code: 'MODULE_NOT_FOUND',
  requireStack: [ '/Users/lwesterhoff/Developer/forks/localicious/bin/localicious' ]
}

I was unable to create a EnvironmentVariable without name being public and having a public init. This fixes that.

I'm running into the same problem. And the DynamicUIColor even has explicit support for versions before iOS 13. So why is the minimum target set to iOS 13?

Seems like you can just use the Xcode-11-beta7 branch to build in Xcode 11 GM.

I guess this issue is easily fixed by dropping support for iOS 9 correct? In that case it can just use UIScreen.main.traitCollection.preferredContentSizeCategory:

    public var bon_preferredContentSizeCategory: BonMotContentSizeCategory {
        if preferredContentSizeCategory != .unspecified {
            return preferredContentSizeCategory
        }

        return UIScreen.main.traitCollection.preferredContentSizeCategory
    }

Since we're almost at iOS 13 now wouldn't it be ok to just drop iOS 9 support?