Availability in Build settings and Info.plist instructions work locally on MAC but not on Circle CI

[JanithaR]

The vars are always correctly populated when building/archiving locally on my MAC but always empty when built/archived on Circle CI.

I'm not really sure what other information to give on this other than that. Basically, I ran into this problem when integrating Codepush to my app, where they expect the keys to be defined in the Info.plist file. I took the traditional route of specifying build settings as a temporary workaround for the moment.

Let me know how I can help with any additional logs or similar.

[luis-f-lins]

I'm also having this problem, but we're using Bitrise for CI/CD

[JanithaR]

Check #391

[tpucci]

Perhaps this will help: #391 (comment)

[twelve17]

#391 (comment) Didn't apply in my case (I don't see the Build input file cannot be found: GeneratedDotEnv.m error). The app just always ends up with a Info.plist with empty values where the env values should be at. Unless I run it again. I'm going to try the other workaround in #391 (comment).

[lucianomlima]

Have the same problem with Bitrise. Defined secrets and env vars correctly there, but get AAPT: error: resource string/FACEBOOK_APP_ID (aka com.myapp.example/FACEBOOK_APP_ID) not found.

Add .env file to repository seems strange to me.

[shaddeen]

Did anyone figure this out? Same issue on Bitrise

[luis-f-lins]

@lucianomlima @shaddeen on Bitrise, I've used a temporary fix based on #391 (comment). I've created the following .js script and put it in the source folder. Then, in the Bitrise workflow (I've personally changed both the staging and production workflows), right after the yarn install step, I added a Script Runner step, to run the following script with node. This fixed the problem, and I've been using it for a few months now. Hope this helps you guys!

const fs = require('fs');
const dotenv = require('dotenv');
const promisify = require('util').promisify;
const writeFile = promisify(fs.writeFile);
const readFile = promisify(fs.readFile);

async function main() {
  try {
    console.log('===================== THIS IS A TEMPORARY SCRIPT ===================');
    console.log('===================== UPDATING Info.plist with .env ================');
    console.log('====================================================================');

    let isProduction;
    try {
      if(fs.existsSync('./.env.production')) {
        isProduction = true;
        console.log('production environment');
      } else {
        isProduction = false;
        console.log('staging environment');
      }
    } catch (err) {
        console.error(err);
    }
    const envfile = isProduction ? await readFile('./.env.production', 'utf-8') : await readFile('./.env', 'utf-8');
    const plist = await readFile('./ios/[***  PROJECT_FOLDER  ***]/Info.plist', 'utf-8');
    const env = dotenv.parse(Buffer.from(envfile));
    let plistupdated = plist;
    Object.entries(env).forEach(([key,value]) => {
      plistupdated = plistupdated.replace(new RegExp(`\\$\\(${key}\\)`, 'g'), value);
    });
    await writeFile('./ios/[***  PROJECT_FOLDER  ***]/Info.plist', plistupdated, 'utf-8');
    await writeFile('./ios/[***  PROJECT_FOLDER  ***]/Info.plist.bak', plist, 'utf-8');
  } catch (e) {
    console.error(e);
    console.error(`Unable to read .env file`);
    process.exit(1);
  }
}

main();

[shaddeen]

@luis-f-lins thanks! Do you have something for android?

[luis-f-lins]

@luis-f-lins thanks! Do you have something for android?

I don’t think this problem occurs on Android, because it’s related to the Info.plist file, which is an iOS file.

[lucianomlima]

@lucianomlima @shaddeen on Bitrise, I've used a temporary fix based on #391 (comment). I've created the following .js script and put it in the source folder. Then, in the Bitrise workflow (I've personally changed both the staging and production workflows), right after the yarn install step, I added a Script Runner step, to run the following script with node. This fixed the problem, and I've been using it for a few months now. Hope this helps you guys!

const fs = require('fs');
const dotenv = require('dotenv');
const promisify = require('util').promisify;
const writeFile = promisify(fs.writeFile);
const readFile = promisify(fs.readFile);

async function main() {
  try {
    console.log('===================== THIS IS A TEMPORARY SCRIPT ===================');
    console.log('===================== UPDATING Info.plist with .env ================');
    console.log('====================================================================');

    let isProduction;
    try {
      if(fs.existsSync('./.env.production')) {
        isProduction = true;
        console.log('production environment');
      } else {
        isProduction = false;
        console.log('staging environment');
      }
    } catch (err) {
        console.error(err);
    }
    const envfile = isProduction ? await readFile('./.env.production', 'utf-8') : await readFile('./.env', 'utf-8');
    const plist = await readFile('./ios/[***  PROJECT_FOLDER  ***]/Info.plist', 'utf-8');
    const env = dotenv.parse(Buffer.from(envfile));
    let plistupdated = plist;
    Object.entries(env).forEach(([key,value]) => {
      plistupdated = plistupdated.replace(new RegExp(`\\$\\(${key}\\)`, 'g'), value);
    });
    await writeFile('./ios/[***  PROJECT_FOLDER  ***]/Info.plist', plistupdated, 'utf-8');
    await writeFile('./ios/[***  PROJECT_FOLDER  ***]/Info.plist.bak', plist, 'utf-8');
  } catch (e) {
    console.error(e);
    console.error(`Unable to read .env file`);
    process.exit(1);
  }
}

main();

I have been resolved in a similar way, but using a bash script.

[shaddeen]

@luis-f-lins thanks! Do you have something for android?

I don’t think this problem occurs on Android, because it’s related to the Info.plist file, which is an iOS file.

Strange, I have the exact same issue with Android

[jaexplorer]

@luis-f-lins I'm still having issues with Bitrise, are you able to help me?

[luis-f-lins]

@luis-f-lins I'm still having issues with Bitrise, are you able to help me?

Can you describe a little more of what you’re running into?

[jaexplorer]

Managed to figure out I was trying to fix the wrong iOS target, all good

[geraintwhite]

The issue with the first CI build not having the Info.plist processed is that the build relies on tmp.xcconfig existing at the start of the build (seemingly before the pre-action script is run).

My workaround is to run touch ios/tmp.xcconfig at the start of my CI process so that all builds will have the Info.plist processed correctly.