iOS plist setup during build process
I'm new to react-native, coming from Cordova/Ionic and would like to know if there is something similar in React Native regarding the build process.
In Cordova/Ionic, you can specify some config into a config.xml and/or a build.json file.
For example, you can set some build flag like:
"ENABLE_BITCODE = YES",
"DISABLE_PUSH_NOTIFICATIONS = 1"
In config.xml, you can also specify some config such as:
preference name="orientation" value="portrait"
So I was wondering if there is something similar for React Native? Or we need to set all of this manually inside Xcode.
Thanks,
Steve
javascript ios react-native plist
add a comment |
I'm new to react-native, coming from Cordova/Ionic and would like to know if there is something similar in React Native regarding the build process.
In Cordova/Ionic, you can specify some config into a config.xml and/or a build.json file.
For example, you can set some build flag like:
"ENABLE_BITCODE = YES",
"DISABLE_PUSH_NOTIFICATIONS = 1"
In config.xml, you can also specify some config such as:
preference name="orientation" value="portrait"
So I was wondering if there is something similar for React Native? Or we need to set all of this manually inside Xcode.
Thanks,
Steve
javascript ios react-native plist
add a comment |
I'm new to react-native, coming from Cordova/Ionic and would like to know if there is something similar in React Native regarding the build process.
In Cordova/Ionic, you can specify some config into a config.xml and/or a build.json file.
For example, you can set some build flag like:
"ENABLE_BITCODE = YES",
"DISABLE_PUSH_NOTIFICATIONS = 1"
In config.xml, you can also specify some config such as:
preference name="orientation" value="portrait"
So I was wondering if there is something similar for React Native? Or we need to set all of this manually inside Xcode.
Thanks,
Steve
javascript ios react-native plist
I'm new to react-native, coming from Cordova/Ionic and would like to know if there is something similar in React Native regarding the build process.
In Cordova/Ionic, you can specify some config into a config.xml and/or a build.json file.
For example, you can set some build flag like:
"ENABLE_BITCODE = YES",
"DISABLE_PUSH_NOTIFICATIONS = 1"
In config.xml, you can also specify some config such as:
preference name="orientation" value="portrait"
So I was wondering if there is something similar for React Native? Or we need to set all of this manually inside Xcode.
Thanks,
Steve
javascript ios react-native plist
javascript ios react-native plist
edited Jan 9 at 21:40
Shog9♦
129k30208227
129k30208227
asked Dec 31 '18 at 17:08
SteveSteve
105211
105211
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
Depending on whether you have created your app with Expo
or with react-native init
will depend on how you configure your application.
react-native init
The short story is that if you have created your project with react-native init
any configuration changes that you want to make must be done in the native application.
For iOS in the appname.xcodeproj
file, in the Info.plist
, the AppDelegate.m
, perhaps you may even need to add an yourappname.entitlements
file too.
Similarly for Android by editing the AndroidManifest.xml
, the build.gradle
files, the settings.gradle
and even the MainActivity.java
and the MainApplication.java
.
There are a lot of places to edit depending on the changes that you wish to make.
Using react-native init
does require some understanding of the native iOS and Android projects.
Expo
Expo
doesn't have native code that you can edit yourself so all of the preferences and settings that you can change are done mainly in the app.json
. You can see more about that in the Expo documentation: https://docs.expo.io/versions/v31.0.0/workflow/configuration
Although Expo can be easier to use as it extracts the complexity of the native code away, it can become limiting as you are unable to use dependencies that are not supported by Expo. This can lead some app builders to start in Expo and then eject once the Expo framework doesn't meet their requirements.
Expo vs react-native init
This SO question has some good responses on the differences between these two ways of setting up a react-native application. It is definitely worth a read.
What is the difference between Expo and React Native?
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53989796%2fios-plist-setup-during-build-process%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
Depending on whether you have created your app with Expo
or with react-native init
will depend on how you configure your application.
react-native init
The short story is that if you have created your project with react-native init
any configuration changes that you want to make must be done in the native application.
For iOS in the appname.xcodeproj
file, in the Info.plist
, the AppDelegate.m
, perhaps you may even need to add an yourappname.entitlements
file too.
Similarly for Android by editing the AndroidManifest.xml
, the build.gradle
files, the settings.gradle
and even the MainActivity.java
and the MainApplication.java
.
There are a lot of places to edit depending on the changes that you wish to make.
Using react-native init
does require some understanding of the native iOS and Android projects.
Expo
Expo
doesn't have native code that you can edit yourself so all of the preferences and settings that you can change are done mainly in the app.json
. You can see more about that in the Expo documentation: https://docs.expo.io/versions/v31.0.0/workflow/configuration
Although Expo can be easier to use as it extracts the complexity of the native code away, it can become limiting as you are unable to use dependencies that are not supported by Expo. This can lead some app builders to start in Expo and then eject once the Expo framework doesn't meet their requirements.
Expo vs react-native init
This SO question has some good responses on the differences between these two ways of setting up a react-native application. It is definitely worth a read.
What is the difference between Expo and React Native?
add a comment |
Depending on whether you have created your app with Expo
or with react-native init
will depend on how you configure your application.
react-native init
The short story is that if you have created your project with react-native init
any configuration changes that you want to make must be done in the native application.
For iOS in the appname.xcodeproj
file, in the Info.plist
, the AppDelegate.m
, perhaps you may even need to add an yourappname.entitlements
file too.
Similarly for Android by editing the AndroidManifest.xml
, the build.gradle
files, the settings.gradle
and even the MainActivity.java
and the MainApplication.java
.
There are a lot of places to edit depending on the changes that you wish to make.
Using react-native init
does require some understanding of the native iOS and Android projects.
Expo
Expo
doesn't have native code that you can edit yourself so all of the preferences and settings that you can change are done mainly in the app.json
. You can see more about that in the Expo documentation: https://docs.expo.io/versions/v31.0.0/workflow/configuration
Although Expo can be easier to use as it extracts the complexity of the native code away, it can become limiting as you are unable to use dependencies that are not supported by Expo. This can lead some app builders to start in Expo and then eject once the Expo framework doesn't meet their requirements.
Expo vs react-native init
This SO question has some good responses on the differences between these two ways of setting up a react-native application. It is definitely worth a read.
What is the difference between Expo and React Native?
add a comment |
Depending on whether you have created your app with Expo
or with react-native init
will depend on how you configure your application.
react-native init
The short story is that if you have created your project with react-native init
any configuration changes that you want to make must be done in the native application.
For iOS in the appname.xcodeproj
file, in the Info.plist
, the AppDelegate.m
, perhaps you may even need to add an yourappname.entitlements
file too.
Similarly for Android by editing the AndroidManifest.xml
, the build.gradle
files, the settings.gradle
and even the MainActivity.java
and the MainApplication.java
.
There are a lot of places to edit depending on the changes that you wish to make.
Using react-native init
does require some understanding of the native iOS and Android projects.
Expo
Expo
doesn't have native code that you can edit yourself so all of the preferences and settings that you can change are done mainly in the app.json
. You can see more about that in the Expo documentation: https://docs.expo.io/versions/v31.0.0/workflow/configuration
Although Expo can be easier to use as it extracts the complexity of the native code away, it can become limiting as you are unable to use dependencies that are not supported by Expo. This can lead some app builders to start in Expo and then eject once the Expo framework doesn't meet their requirements.
Expo vs react-native init
This SO question has some good responses on the differences between these two ways of setting up a react-native application. It is definitely worth a read.
What is the difference between Expo and React Native?
Depending on whether you have created your app with Expo
or with react-native init
will depend on how you configure your application.
react-native init
The short story is that if you have created your project with react-native init
any configuration changes that you want to make must be done in the native application.
For iOS in the appname.xcodeproj
file, in the Info.plist
, the AppDelegate.m
, perhaps you may even need to add an yourappname.entitlements
file too.
Similarly for Android by editing the AndroidManifest.xml
, the build.gradle
files, the settings.gradle
and even the MainActivity.java
and the MainApplication.java
.
There are a lot of places to edit depending on the changes that you wish to make.
Using react-native init
does require some understanding of the native iOS and Android projects.
Expo
Expo
doesn't have native code that you can edit yourself so all of the preferences and settings that you can change are done mainly in the app.json
. You can see more about that in the Expo documentation: https://docs.expo.io/versions/v31.0.0/workflow/configuration
Although Expo can be easier to use as it extracts the complexity of the native code away, it can become limiting as you are unable to use dependencies that are not supported by Expo. This can lead some app builders to start in Expo and then eject once the Expo framework doesn't meet their requirements.
Expo vs react-native init
This SO question has some good responses on the differences between these two ways of setting up a react-native application. It is definitely worth a read.
What is the difference between Expo and React Native?
answered Jan 1 at 14:25
AndrewAndrew
3,69911026
3,69911026
add a comment |
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53989796%2fios-plist-setup-during-build-process%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown