LiveUpdate switch channel on runtime

[jongbonga]

I'm struggling to pull updates from a dev-channel when I switch from the prod-channel.

//app.ts

    this.platform
      .ready()
      .then(async () => {
        if (this.platform.is("capacitor")) {
          await LiveUpdate.ready();

//trigger

  async toggleEnv(envMode: string) {
    this.settingsStore.update({ envMode });
    await LiveUpdate.reset();
    await LiveUpdate.reload();
  }

//check & update

      try {
        const { versionCode } = await LiveUpdate.getVersionCode();
        const isProd = this.settingsQuery.prodMode;
        const channel = isProd
          ? `production-${versionCode}`
          : `development-${versionCode}`;

        const result = await LiveUpdate.sync({ channel });
        if (result.nextBundleId) {
          updating = true;
          await LiveUpdate.reload();
        }
      } catch (error) {
        console.error("LiveUpdate sync error:", error);
      }

I tried to setChannel({ channel }) before sync but the app is still stuck on the prod- version

What am I missing?

[robingenz]

The setChannel(...) method definitely works (we test the plugin extensively before each release) but I recommend you to pass the channel directly to the sync(...) method as option. This often prevents mistakes. You can then go to the "Log" page of your app within the Capawesome Cloud Console and check the request URL and response body for any errors. The request URL should contain the channel name. The response body should contains the response the plugin receives.

[jongbonga]

Should I call setChannel before triggering every action, such as sync & fetchLatestBundle? I pass the channel on every action that accepts it

[robingenz]

Sure, if you want the channel to be respected by a method, then you have to set it before that. As i said, check the logs first to see if it's really a problem with your code. If you want, we can take a look at it together. Feel free to send me a DM on Discord.

[jongbonga]

Thanks for the offer. I think I found the issue. The reset() method wasn't implemented on the production channel yet, hence it wasn't triggering.