Expo publishing new APK into Playstore without my concern

Expo Development Tools
1

Yesterday I generated a new APK of my app for local testing purposes, but it seems that it also “automaticly uploaded” this new APK into Playstore without my concern(I made sure accessing the playstore and the last update was months ago).

Whoever downloads the app from Playstore, on the second time he opens the app, it will be the App from yesterday build. How could it happen? I don’t remember about enabling some kind of “on air updates” for this app.

❯ expo diagnostics
┌─────────────────────────────────────────────────────────────────────────┐
│                                                                         │
│   There is a new version of expo-cli available (3.27.4).                │
│   You are currently using expo-cli 3.25.1                               │
│   Install expo-cli globally using the package manager of your choice;   │
│   for example: `npm install -g expo-cli` to get the latest version      │
│                                                                         │
└─────────────────────────────────────────────────────────────────────────┘

  Expo CLI 3.25.1 environment info:
    System:
      OS: Linux 4.4 Ubuntu 20.04.1 LTS (Focal Fossa)
      Shell: 5.8 - /usr/bin/zsh
    Binaries:
      Node: 12.18.3 - ~/.nvm/versions/node/v12.18.3/bin/node
      Yarn: 1.22.5 - /mnt/c/Users/T-Gamer/AppData/Roaming/npm/yarn
      npm: 6.14.6 - ~/.nvm/versions/node/v12.18.3/bin/npm
    npmPackages:
      expo: ~37.0.3 => 37.0.8
      react: ~16.9.0 => 16.9.0
      react-dom: ~16.9.0 => 16.9.0
      react-native: https://github.com/expo/react-native/archive/sdk-37.0.1.tar.gz => 0.61.4
2

When you run build:android it’s triggering publish at the same time

If you don’t want update use --release-channel other-channel-name or --no-publish

by default expo is using default channel

1 Like
3

This topic was automatically closed 20 days after the last reply. New replies are no longer allowed.