My code-push is not updating my app

[gmchaturvedi1]

i am new to code-push react native i have setup all things as per the suggested in android setup .

but my update is not working when i am release the it show successful update but in app side nothing happen.

[lostintangent]

@gmchaturvedi1 Could you take a look at the Chrome console or ADB logcat output when you call sync in your app? That should help shed some light on what may be happening. Also, our troubleshooting docs have some common issues and workarounds that could be worth double checking.

[gmchaturvedi1]

when i am using react-native run-android and start chrome console showing
code-push update then showing network error.

kindly find the scrreenshot
[image: Inline image 1]

kindly suggest what to check to resolve the same

reagrds
G M Chaturvedi

On Fri, Apr 22, 2016 at 8:26 PM, Jonathan Carter notifications@github.com
wrote:

@gmchaturvedi1 https://github.com/gmchaturvedi1 Could you take a look
at the Chroome console or ADB logcat output when you call sync in your app?
That should help shed some light on what may be happening. Also, our
troubleshootinf
https://github.com/Microsoft/react-native-code-push/blob/master/README.md#debugging--troubleshooting
docs have some common issues and workarounds that could be worth double
checking.

—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
#304 (comment)

[lostintangent]

Could you try restarting the emulator? Sometimes, when you switch networks there can be connectivity issues. Restarting the emulator will resolve that, if that is in fact the issue.

[gmchaturvedi1]

Now updaye is giving popup but nothing changed .ia it take more time to be
in effect
On 22 Apr 2016 23:07, "Jonathan Carter" notifications@github.com wrote:

Could you try restarting the emulator? Sometimes, when you switch networks
there can be connectivity issues. Restarting the emulator will resolve
that, if that is in fact the issue.

—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
#304 (comment)

[lostintangent]

What does the console output show after you try to install the update? Also, can you share how you're calling sync?

[gmchaturvedi1]

I am just calling sync woth root component componentdidmount lifecycle and
call codePush.sync() as suggested in documents
On 22 Apr 2016 23:54, "Jonathan Carter" notifications@github.com wrote:

What does the console output show after you try to install the update?
Also, can you share how you're calling sync?

—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
#304 (comment)

[lostintangent]

OK cool. After you install the update, and then kill and restart the app, you're not seeing the changes take affect? Could you try looking at the Chrome logs to see what may be going on?

[gmchaturvedi1]

in localhost update is working but in googleplay pop up update is coming
but changes is not done.

On Sat, Apr 23, 2016 at 12:07 AM, Jonathan Carter notifications@github.com
wrote:

OK cool. After you install the update, and then kill and restart the app,
you're not seeing the changes take affect? Could you try looking at the
Chrome logs to see what may be going on?

—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
#304 (comment)

[geof90]

From what I am understanding, you are calling codePush.sync() without any additional options, so the installMode will default to ON_NEXT_RESTART. Therefore, the changes will only show up when you kill the app. This can appear to behave different sometimes for certain emulators from my experience, where if the system resources allocated are not enough, sometimes backgrounding the app will immediately cause the process to get killed, in which case simply returning to the app will cause it to pick up the updates.

So, I would suggest for the googleplay version, to either try forcibly killing the app after the update is installed, or changing the call to codePush.sync() to use InstallMode.ON_NEXT_RESUME or InstallMode.IMMEDIATE, and see if it solves your problem. Let us know if otherwise!

[gmchaturvedi1]

i did the same as you have suggested in your trail mail.But still not
updating. i set InstallMode.IMMEDIATE .Update dialogue box show
immediateley after release update but when we continue nothing chnaged as
per the release(whilein locl system it is working).Is their anything so it
is not updating in app install through google play.

Regards
G m chaturvedi

On Sat, Apr 23, 2016 at 4:13 AM, Geoffrey Goh notifications@github.com
wrote:

From what I am understanding, you are calling codePush.sync() without any
additional options, so the installMode will default to ON_NEXT_RESTART.
Therefore, the changes will only show up when you kill the app. This can
appear to behave different sometimes for certain emulators from my
experience, where if the system resources allocated are not enough,
sometimes backgrounding the app will immediately cause the process to get
killed, in which case simply returning to the app will cause it to pick up
the updates.

So, I would suggest for the googleplay version, to either try forcibly
killing the app after the update is installed, or changing the call to
codePush.sync() to use InstallMode.ON_NEXT_RESUME or
InstallMode.IMMEDIATE, and see if it solves your problem. Let us know if
otherwise!

—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
#304 (comment)

[lostintangent]

Can you share what your MainActivity looks like? And also, can you try copying and pasting the logs of the app when trying to sync an update in the Google Play version? That should help us figure out what might be going on. You can't use Chrome with the release build, but you can use ADB via "adb logcat *:S ReactNative:V ReactNativeJS:V".

[gmchaturvedi1]

i see a weired thing that when update is available the update window is
showing only continue button. but as i am watching one screecast of mr
purushottam ,on update two button will rise install and ignor.

MainActivty

package com.go4skillcom;

import com.facebook.react.ReactActivity;
import io.realm.react.RealmReactPackage;
import com.oblador.vectoricons.VectorIconsPackage;
import com.microsoft.codepush.react.CodePush;
import com.facebook.react.ReactPackage;
import com.facebook.react.shell.MainReactPackage;

import java.util.Arrays;
import java.util.List;

public class MainActivity extends ReactActivity {

/**
 * Returns the name of the main component registered from JavaScript.
 * This is used to schedule rendering of the component.
 */
@Override
protected String getMainComponentName() {
    return "go4skillcom";
}

/**
 * Returns whether dev mode should be enabled.
 * This enables e.g. the dev menu.
 */
@Override
protected boolean getUseDeveloperSupport() {
    return BuildConfig.DEBUG;
}

/**
 * A list of packages used by the app. If the app uses additional views
 * or modules besides the default ones, add more packages here.
 */
@Override
protected List<ReactPackage> getPackages() {
    return Arrays.<ReactPackage>asList(
        new MainReactPackage(),
        new RealmReactPackage(),
        new VectorIconsPackage(),
        new CodePush("6fmr8pcJ2Ov51fm3at9_ioOn5TXEVy9szxs6g", this,

BuildConfig.DEBUG)
);
}
}

regards
G M chaturvedi

On Sat, Apr 23, 2016 at 9:23 PM, Jonathan Carter notifications@github.com
wrote:

Can you share what your MainActivity looks like? And also, can you try
copying and pasting the logs of the app when trying to sync an update in
the Google Play version? That should help us figure out what might be going
on. You can't use Chrome with the release build, but you can use ADB via
"adb logcat *:S ReactNative:V ReactNativeJS:V".

—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
#304 (comment)

[gmchaturvedi1]

Sorry for the delayed response from my side asbibm not access vthe
network.kindly help me out on yhis
On 25 Apr 2016 18:54, "gajendra nath" gmchaturvedi@gmail.com wrote:

i see a weired thing that when update is available the update window is
showing only continue button. but as i am watching one screecast of mr
purushottam ,on update two button will rise install and ignor.

MainActivty

package com.go4skillcom;

import com.facebook.react.ReactActivity;
import io.realm.react.RealmReactPackage;
import com.oblador.vectoricons.VectorIconsPackage;
import com.microsoft.codepush.react.CodePush;
import com.facebook.react.ReactPackage;
import com.facebook.react.shell.MainReactPackage;

import java.util.Arrays;
import java.util.List;

public class MainActivity extends ReactActivity {

/**
 * Returns the name of the main component registered from JavaScript.
 * This is used to schedule rendering of the component.
 */
@Override
protected String getMainComponentName() {
    return "go4skillcom";
}

/**
 * Returns whether dev mode should be enabled.
 * This enables e.g. the dev menu.
 */
@Override
protected boolean getUseDeveloperSupport() {
    return BuildConfig.DEBUG;
}

/**
 * A list of packages used by the app. If the app uses additional views
 * or modules besides the default ones, add more packages here.
 */
@Override
protected List<ReactPackage> getPackages() {
    return Arrays.<ReactPackage>asList(
        new MainReactPackage(),
        new RealmReactPackage(),
        new VectorIconsPackage(),
        new CodePush("6fmr8pcJ2Ov51fm3at9_ioOn5TXEVy9szxs6g", this,

BuildConfig.DEBUG)
);
}
}

regards
G M chaturvedi

On Sat, Apr 23, 2016 at 9:23 PM, Jonathan Carter <notifications@github.com

wrote:

Can you share what your MainActivity looks like? And also, can you try
copying and pasting the logs of the app when trying to sync an update in
the Google Play version? That should help us figure out what might be going
on. You can't use Chrome with the release build, but you can use ADB via
"adb logcat *:S ReactNative:V ReactNativeJS:V".

—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
#304 (comment)

[lostintangent]

@gmchaturvedi1 Your MainActivity class needs to override the getJSBundleFile file in order for the React Native runtime to ask CodePush where to get the JS bundle from when the app starts. Refer to step #2 in the Android configuration docs.

@Override
protected String getJSBundleFile() {
   return CodePush.getBundleUrl();
}

This was likely working for you during development because the changes you were deploying to CodePush were also available locally, so when the app would restart, the packager would pick them up. This issue wouldn't be exclusive to the Google Play store, and should also repro in any release build.

[gmchaturvedi1]

so shall i need to add these as suggested in mainActivity. Kindly tell me
the location .

so i can try and get back with update.

thanks & Regards
G M Chaturvedi

On Mon, Apr 25, 2016 at 9:23 PM, Jonathan Carter notifications@github.com
wrote:

@gmchaturvedi1 https://github.com/gmchaturvedi1 Your MainActivity class
needs to override the getJSBundleFile file in order for the React Native
runtime to ask CodePush where to get the JS bundle from when the app
starts. Refer to step #2
#2 in the Android
configuration docs
https://github.com/Microsoft/react-native-code-push#plugin-configuration-android
.

@Overrideprotected String getJSBundleFile() {
return CodePush.getBundleUrl();
}

This was likely working for you during development because the changes you
were deploying to CodePush were also available locally, so when the app
would restart, the packager would pick them up.

—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
#304 (comment)