Published React Native app pulls changes from private repository
I've encountered a very mysterious and baffling phenomenon in the process of publishing a React Native app to both the Apple App Store and the Google Play Store. It seems like witchcraft.
The app, which we have already published on both stores, updates every time we push changes to our private repository.
EDIT: The app, which we have already published on both stores, updates SOME OF THE TIME (not every time) we push changes to our private repository.
For example, let's say the app started out with page A and page B. We publish the app, we'll call it "Witchcraft", to both app stores. We then push an update to our private repository (on BitBucket) that includes the addition of page C. The next day, someone (outside of the company) downloads our app from one of the app stores (without cloning our repository), and their install of "Witchcraft" includes page C.
What in the world is going on?
Here are some details:
- The app was developed in React Native.
- We used Expo for development and testing of the app.
- We host our repository using BitBucket.
- We are NOT developing in the master branch.
- New users, when they install the app from either play store, seem to see ALMOST all the changes we've pushed to the repository, BUT...
- There is one property of the repository that users do NOT acquire in their fresh installation - their installation correctly points to the production database (for retrieving user info, etc) instead of the development database, which is what is referenced in what is pushed to the repository.
- We have NOT updated the builds on the app stores, so we do not expect these changes to appear in the app store builds.
We are very concerned because we do not want breaking changes being reflected in the production app.
We haven't the slightest idea what is going on. Any insight would be appreciated.
android ios git react-native bitbucket asked Nov 22 '18 at 4:04
Johiasburg FrowellJohiasburg Frowell
17315
add a comment |
I've encountered a very mysterious and baffling phenomenon in the process of publishing a React Native app to both the Apple App Store and the Google Play Store. It seems like witchcraft.
The app, which we have already published on both stores, updates every time we push changes to our private repository.
EDIT: The app, which we have already published on both stores, updates SOME OF THE TIME (not every time) we push changes to our private repository.
For example, let's say the app started out with page A and page B. We publish the app, we'll call it "Witchcraft", to both app stores. We then push an update to our private repository (on BitBucket) that includes the addition of page C. The next day, someone (outside of the company) downloads our app from one of the app stores (without cloning our repository), and their install of "Witchcraft" includes page C.
What in the world is going on?
Here are some details:
- The app was developed in React Native.
- We used Expo for development and testing of the app.
- We host our repository using BitBucket.
- We are NOT developing in the master branch.
- New users, when they install the app from either play store, seem to see ALMOST all the changes we've pushed to the repository, BUT...
- There is one property of the repository that users do NOT acquire in their fresh installation - their installation correctly points to the production database (for retrieving user info, etc) instead of the development database, which is what is referenced in what is pushed to the repository.
- We have NOT updated the builds on the app stores, so we do not expect these changes to appear in the app store builds.
We are very concerned because we do not want breaking changes being reflected in the production app.
We haven't the slightest idea what is going on. Any insight would be appreciated.
android ios git react-native bitbucket asked Nov 22 '18 at 4:04
Johiasburg FrowellJohiasburg Frowell
17315
add a comment |
I've encountered a very mysterious and baffling phenomenon in the process of publishing a React Native app to both the Apple App Store and the Google Play Store. It seems like witchcraft.
The app, which we have already published on both stores, updates every time we push changes to our private repository.
EDIT: The app, which we have already published on both stores, updates SOME OF THE TIME (not every time) we push changes to our private repository.
For example, let's say the app started out with page A and page B. We publish the app, we'll call it "Witchcraft", to both app stores. We then push an update to our private repository (on BitBucket) that includes the addition of page C. The next day, someone (outside of the company) downloads our app from one of the app stores (without cloning our repository), and their install of "Witchcraft" includes page C.
What in the world is going on?
Here are some details:
- The app was developed in React Native.
- We used Expo for development and testing of the app.
- We host our repository using BitBucket.
- We are NOT developing in the master branch.
- New users, when they install the app from either play store, seem to see ALMOST all the changes we've pushed to the repository, BUT...
- There is one property of the repository that users do NOT acquire in their fresh installation - their installation correctly points to the production database (for retrieving user info, etc) instead of the development database, which is what is referenced in what is pushed to the repository.
- We have NOT updated the builds on the app stores, so we do not expect these changes to appear in the app store builds.
We are very concerned because we do not want breaking changes being reflected in the production app.
We haven't the slightest idea what is going on. Any insight would be appreciated.
android ios git react-native bitbucket asked Nov 22 '18 at 4:04
Johiasburg FrowellJohiasburg Frowell
17315
I've encountered a very mysterious and baffling phenomenon in the process of publishing a React Native app to both the Apple App Store and the Google Play Store. It seems like witchcraft.
The app, which we have already published on both stores, updates every time we push changes to our private repository.
EDIT: The app, which we have already published on both stores, updates SOME OF THE TIME (not every time) we push changes to our private repository.
For example, let's say the app started out with page A and page B. We publish the app, we'll call it "Witchcraft", to both app stores. We then push an update to our private repository (on BitBucket) that includes the addition of page C. The next day, someone (outside of the company) downloads our app from one of the app stores (without cloning our repository), and their install of "Witchcraft" includes page C.
What in the world is going on?
Here are some details:
- The app was developed in React Native.
- We used Expo for development and testing of the app.
- We host our repository using BitBucket.
- We are NOT developing in the master branch.
- New users, when they install the app from either play store, seem to see ALMOST all the changes we've pushed to the repository, BUT...
- There is one property of the repository that users do NOT acquire in their fresh installation - their installation correctly points to the production database (for retrieving user info, etc) instead of the development database, which is what is referenced in what is pushed to the repository.
- We have NOT updated the builds on the app stores, so we do not expect these changes to appear in the app store builds.
We are very concerned because we do not want breaking changes being reflected in the production app.
We haven't the slightest idea what is going on. Any insight would be appreciated.
android ios git react-native bitbucket android ios git react-native bitbucket asked Nov 22 '18 at 4:04
Johiasburg FrowellJohiasburg Frowell
17315
asked Nov 22 '18 at 4:04
Johiasburg FrowellJohiasburg Frowell
17315
edited Dec 5 '18 at 16:06
Johiasburg Frowell
asked Nov 22 '18 at 4:04
Johiasburg FrowellJohiasburg Frowell
17315
asked Nov 22 '18 at 4:04
Johiasburg FrowellJohiasburg Frowell
17315
asked Nov 22 '18 at 4:04
Johiasburg FrowellJohiasburg Frowell
17315
17315
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
It may be possible that you have OTA updates enabled, in your app.json add the following:
{
"updates": {
"enabled": false,
}
}
Also check if at any point of the process you are doing expo publish maybe in git hook?
answered Nov 22 '18 at 4:22
Cristian GomezCristian Gomez
1,40421026
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%2f53423716%2fpublished-react-native-app-pulls-changes-from-private-repository%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
It may be possible that you have OTA updates enabled, in your app.json add the following:
{
"updates": {
"enabled": false,
}
}
Also check if at any point of the process you are doing expo publish maybe in git hook?
answered Nov 22 '18 at 4:22
Cristian GomezCristian Gomez
1,40421026
add a comment |
It may be possible that you have OTA updates enabled, in your app.json add the following:
{
"updates": {
"enabled": false,
}
}
Also check if at any point of the process you are doing expo publish maybe in git hook?
answered Nov 22 '18 at 4:22
Cristian GomezCristian Gomez
1,40421026
add a comment |
It may be possible that you have OTA updates enabled, in your app.json add the following:
{
"updates": {
"enabled": false,
}
}
Also check if at any point of the process you are doing expo publish maybe in git hook?
answered Nov 22 '18 at 4:22
Cristian GomezCristian Gomez
1,40421026
It may be possible that you have OTA updates enabled, in your app.json add the following:
{
"updates": {
"enabled": false,
}
}
Also check if at any point of the process you are doing expo publish maybe in git hook?
answered Nov 22 '18 at 4:22
Cristian GomezCristian Gomez
1,40421026
answered Nov 22 '18 at 4:22
Cristian GomezCristian Gomez
1,40421026
answered Nov 22 '18 at 4:22
Cristian GomezCristian Gomez
1,40421026
answered Nov 22 '18 at 4:22
Cristian GomezCristian Gomez
1,40421026
1,40421026
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%2f53423716%2fpublished-react-native-app-pulls-changes-from-private-repository%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
