You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In `android/app/build.gradle`, if you use `applicationIdSuffix` or `applicationId` that is different from the package name indicated in `AndroidManifest.xml` in `<manifest package="...">` tag, for example, to support different build variants:
- Go to _Edit scheme..._ -> _Build_ -> _Pre-actions_, click _+_ and select _New Run Script Action_. Paste below code which will generate KEYS keys on native ios side (into node*modules) Make sure to select your target under \_Provide build settings from*, so `$SRCROOT` environment variables is available to the script.
This also works for `run-android`. Alternatively, there are platform-specific options below.
@@ -310,13 +331,13 @@ This also works for `run-android`. Alternatively, there are platform-specific op
310
331
311
332
The same environment variable can be used to assemble releases with a different config:
312
333
313
-
```
314
-
$ cd android && KEYSFILE=keys.staging.json ./gradlew assembleRelease
334
+
```sh
335
+
cd android && KEYSFILE=keys.staging.json ./gradlew assembleRelease
315
336
```
316
337
317
338
Alternatively, you can define a map in `build.gradle` associating builds with env files. Do it before the `apply from` call, and use build cases in lowercase, like:
In `android/app/build.gradle`, if you use `applicationIdSuffix` or `applicationId` that is different from the package name indicated in `AndroidManifest.xml` in `<manifest package="...">` tag, for example, to support different build variants:
0 commit comments