How to generate buildConfigField with String type

Question

In my Android Studio project there are two build configuration with some buildConfigField:

    buildTypes {
    def SERVER_URL = "SERVER_URL"
    def APP_VERSION = "APP_VERSION"

    debug {
        buildConfigField "String", SERVER_URL, "http://dev.myserver.com"
        buildConfigField "String", APP_VERSION, "0.0.1"
    }

    release {
        buildConfigField "String", SERVER_URL, "https://myserver.com"
        buildConfigField "String", APP_VERSION, "0.0.1"

        minifyEnabled false
        proguardFiles getDefaultProguardFile('proguard-android.txt'), 'proguard-rules.pro'
    }
}

I am getting and error as follows:

/path/to/generated/BuildConfig.java
    Error:(14, 47) error: ';' expected
    Error:(15, 47) error: ';' expected

the generated BuildConfig.java is as follows:

public final class BuildConfig {
    public static final boolean DEBUG = Boolean.parseBoolean("true");
    public static final String APPLICATION_ID = "com.mycuteoffice.mcoapp";
    public static final String BUILD_TYPE = "debug";
    public static final String FLAVOR = "";
    public static final int VERSION_CODE = 1;
    public static final String VERSION_NAME = "1.0";
    // Fields from build type: debug
    public static final String APP_VERSION = 0.0.1;
    public static final String SERVER_URL = http://dev.mycuteoffice.com;
}

I think the APP_VERSION and SERVER_URL are not getting generated properly as being String type they do not have quotes.

I am not sure why it is being generated in such a way. Please let me know how can I resolve this issues.

Just add single quotes around the value with double quotes: `buildConfigField "String", APP_VERSION, ' "0.0.1" '` (without spaces of course) — Pierre, Sep 18 '19 at 07:50
https://stackoverflow.com/a/65624195/3970630 can be define on your gradle files :) — Ric17101, Mar 22 '21 at 02:42

Vladyslav Matviienko · Accepted Answer · 2018-05-18T04:56:40.950

348

String type build config fields should be declared like this:

buildConfigField "String", "SERVER_URL", "\"http://dev.myserver.com\""

the field name in quotes, the field value in escaped quotes additionally.

edited May 18 '18 at 04:56

answered Jun 12 '15 at 06:28

Vladyslav Matviienko

10,610
4
33
52

1

The Question intended to use 'SERVER_URL' as a variable. Putting "SERVER_URL" in quotes makes the value a String literal. @madhead's answer is therefore more correct (and prettier). – Will Vanderhoef Jul 21 '16 at 19:48
My bad. I used Simas's answer as a base and just copied it. My point was not about third field (variable name), but about using double quotes for escaping variable value: if the variable itself does not have double quotes, you can simply single outer quotes to get rid of backslashes. I've edited both answers. – madhead Jul 22 '16 at 07:52
@VladMatvienko definitely works, I am actually using it the way I describe. `def FIELD_NAME = "SERVER_URL"` and `buildConfigField "boolean", FIELD_NAME, "false"` work just fine together. If you're missing the definition of SERVER_URL you'll crash, that's probably what you're doing wrong. – Will Vanderhoef Aug 01 '16 at 21:55
Use buildConfigField "String", "FILE_NAME", "\"{$fileName}\"" for variable names. – Adolf Dsilva Feb 09 '18 at 10:23
@Audi, thanks, but that is exactly what my answer states (for 3 years already) – Vladyslav Matviienko Feb 09 '18 at 12:35
If anything i declared like this, its shown when i decompile the apk... How will protect those kind of the secure values? – Saikumar May 22 '18 at 05:38
@Kums that does not relate to this question. If you have another question then ask a new question. – Vladyslav Matviienko May 22 '18 at 05:39
base url is getting displayed even after putting url in build gradle file after decompile apk this is not working. – karan May 02 '23 at 09:33

madhead · Answer 2 · 2016-07-22T07:49:29.453

126

Why everybody is so mad about escaping double quotes? Looks ugly! This is Groovy, guys, you can just mix single and double quotes:

buildConfigField "String", 'SERVER_URL', '"http://dev.myserver.com"'
buildConfigField "String", 'APP_VERSION', '"0.0.1"'

edited Jul 22 '16 at 07:49

answered May 05 '16 at 21:44

madhead

31,729
16
153
201

6

That's still not the way to go, we shouldn't have to escape or use nested quotes it since it's String – Fabio Jun 10 '16 at 00:48
5

@Fabio Using nested quotes allows using expressions that can be evaluated. See [this answer](http://stackoverflow.com/a/38290751/4034572). – Albert Vila Calvo Feb 21 '17 at 11:06
Any reason why you put `String` in double quotes and `SERVER_URL` in single quotes? – Adam Johns Aug 24 '20 at 14:58
@AdamJohns, I guess no. Just to demonstrate that both `'` and `"` could be used. – madhead Aug 24 '20 at 18:36
base url is getting displayed even after putting url in build gradle file after decompile apk – karan May 02 '23 at 09:33

score 39 · Answer 3 · edited Jun 27 '17 at 06:38

If by "resolving the issues" you mean not having to double quote literals, I haven't come across anything as it seems to be working as designed.

I've been experimenting with moving the literals into "gradle.properties" as a workaround, turning potentially multiple ugly lines into one ugly line.

Like so:

buildTypes {
def SERVER_URL = "SERVER_URL"
def APP_VERSION = "APP_VERSION"

def CONFIG = { k -> "\"${project.properties.get(k)}\"" }

debug {
    buildConfigField "String", SERVER_URL, CONFIG("debug.server.url")
    buildConfigField "String", APP_VERSION, CONFIG("version")
}

release {
    buildConfigField "String", SERVER_URL, CONFIG("release.server.url")
    buildConfigField "String", APP_VERSION, CONFIG("version")

    minifyEnabled false
    proguardFiles getDefaultProguardFile('proguard-android.txt'), 'proguard-rules.pro'
}
}

gradle.properties

version=0.1.1
...
debug.server.url=http://dev.myserver.com
...
release.server.url=http://myserver.com
...

Further thoughts:

def CONFIG = { b,k -> "\"${project.properties.get(b+'.'+k)}\"" }
def CONFIG_DEBUG = { k -> CONFIG('debug',k) }
def CONFIG_RELEASE = { k -> CONFIG('release',k) }

def CONFIG = { b,k -> "\"${project.properties.get(b+'.'+k)}\"" }
def CONFIG_INT = { b,k -> "${project.properties.get(b+'.'+k)}" }
...

i have a build config field and i want to access that variable in myn def in same gradle .. i am new to gradle plz helpp!! — Adeel Turk, Mar 08 '18 at 14:35
Thanks for CONFIG script! In team we slightly improved it to throw exception if var doesn't exists: `CONFIG = { k -> if (project.properties.containsKey(k)) "\"${project.properties.get(k)}\"" else throw new RuntimeException("No such variable: " + k) }` — demaksee, Aug 28 '18 at 15:55

score 19 · Answer 4 · answered Feb 09 '18 at 10:24

19

Use

 buildConfigField "String", "FILE_NAME", "\"{$fileName}\""

for variable. Reference from here

answered Feb 09 '18 at 10:24

Adolf Dsilva

13,092
8
34
45

score 12 · Answer 5 · edited Jul 22 '16 at 07:49

12

Escape your string quotes:

buildConfigField "String", 'SERVER_URL', "\"http://dev.myserver.com\""
buildConfigField "String", 'APP_VERSION', "\"0.0.1\""

edited Jul 22 '16 at 07:49

madhead

31,729
16
153
201

answered Jun 12 '15 at 06:32

Simas

43,548
10
88
116

score 10 · Answer 6 · answered Jul 10 '16 at 10:07

10

I was confused as well. But there is a sense - "String" defines the field's type, whereas the field value isn't get quoted automatically in order to allow us to use expressions here:

buildConfigField "String", "TEST", "new Integer(10).toString()"

Otherwise, it wouldn't be possible.

answered Jul 10 '16 at 10:07

geiger

722
7
12

1

It's possible if you use string interpolation, e.g: buildConfigField "String", "TEST", "\"${10}\"" This way you can use methods or variables in your build file as well. – Szörényi Ádám Oct 17 '19 at 14:32

score 5 · Answer 7 · edited Sep 05 '20 at 22:05

We should scape our Gradle constant defined in our Gradle properties or somewhere else:

buildConfigField "String", "CONSTANT_NAME", "\"${CONSTANT_VALUE}\""

Where CONSTANT_VALUE is defined in our gradle.properties or somewhere else:

CONSTANT_VALUE=string_goes_here

It applies the same way when getting constants gotten from our environment:

buildConfigField "String", "CONSTANT_NAME", "\"${System.getenv('PATH')}\""

The most voted solution works in case we just need to add a String manually, this solution just goes a step further.

score 4 · Answer 8 · answered Dec 05 '22 at 07:02

write code in gradle.properties

YOUR_ACCESS_PARAMS = "YOUR_VALUE"

write code into app level build.gradle

android{
    ...
     buildTypes.each{
        it.buildConfigField 'String', 'ACCESS_PARAMS', YOUR_ACCESS_PARAMS
    }
}

the generated BuildConfig.java is as follows:

public final class BuildConfig {  
    public static final boolean DEBUG = Boolean.parseBoolean("true");   
    public static final String APPLICATION_ID = "xxx.xxxxxxxx.xxx";   
    public static final String BUILD_TYPE = "debug";  
    public static final String FLAVOR = "";  
    public static final int VERSION_CODE = 1;  
    public static final String VERSION_NAME = "1.0.0";  
    // Fields from build type: debug  
    public static final String ACCESS_PARAMS = "YOUR_VALUE";  
}

score 1 · Answer 9 · answered Oct 31 '18 at 03:21

in app build.gradle

def buildTimeAndVersion = releaseTime() + "-" + getSvnVersion()    
buildTypes {
debug {
    signingConfig signingConfigs.config
    buildConfigField "String", 'BIULD_TIME', "\"${buildTimeAndVersion}\""
    proguardFiles getDefaultProguardFile('proguard-android.txt'), 'proguard-rules.pro'
    }
}
...
}

static def releaseTime() {
return new Date().format("yyyyMMdd", TimeZone.getDefault())
}

def getSvnVersion() {
def pro = ("svnversion -c " + getBuildDir().parent).execute()
pro.waitFor()
def version = pro.in.text
Pattern p = Pattern.compile("(\\d+\\:)?(\\d+)\\D?")
Matcher m = p.matcher(version)
if (m.find()) {
version = m.group(m.groupCount())
}
try {
return version
} catch (e) {
println e.getMessage()
}
return 0
}

then in BuildConfig

public final class BuildConfig {  
public static final boolean DEBUG = Boolean.parseBoolean("true");   
public static final String APPLICATION_ID = "xxx.xxxxxxxx.xxx";   
public static final String BUILD_TYPE = "debug";  
public static final String FLAVOR = "";  
public static final int VERSION_CODE = 53;  
public static final String VERSION_NAME = "5.4.4";  
// Fields from build type: debug  
public static final String BIULD_TIME = "20181030-2595";  
}

Code only answers are really discouraged. To help future readers, please explain what you are doing too! — itsmysterybox, Oct 31 '18 at 03:52
and next time reference to your previous answer https://stackoverflow.com/a/53056170/1084764 instead of just copy pasting — Raykud, Mar 20 '20 at 18:47

score 1 · Answer 10 · answered Feb 25 '21 at 08:39

I need the variable in buildConfigField and manifestPaceholder. To solve this I do

def appAuthScheme= "appauth.myscheme"
buildConfigField 'String', 'APP_AUTH_SCHEME',"\"$appAuthScheme\""

manifestPlaceholders = [lowerApplicationId : applicationId.toLowerCase(),
                        appAuthRedirectScheme : appAuthScheme]

BuildConfig.APP_AUTH_SCHEME is a String !

score 0 · Answer 11 · answered Apr 07 '23 at 04:16

0

Need have def variable

debug {
    ...
    def myVersion = '1.0.0'
    buildConfigField 'String', 'TEST', "\"${myVersion}\""
}

answered Apr 07 '23 at 04:16

Trang Đỗ

160
1
9

score 0 · Answer 12 · answered Jun 15 '23 at 09:07

I preferred to highlight that some of those values were strings. At the same time I was not really keen on the escaped quotes for readability reasons.

It might look a little naive, but in the end I settled for this alternative:

buildConfigField "String", "LIB_VERSION_NAME", '"' + "${versionName}" + '"'

and the outcome can look like this:

How to generate buildConfigField with String type

12 Answers12

Linked

Related