In fact, made some changes.
Launched the command
expo build: android
And that's it.
After a while, I’m watching it come from the playlist update.
Why?
After all, I did not upload at all in any way, either through the expo upload: command, or into manual upload via the web.
Same thing with appstore.
  • The build command builds on the expo servers and gives you to download the .apk file locally, at this stage the expo does not request any data for publication in Google Play.
    Are you sure that the update came with a new build - maybe just an update with the old build seemed to be late?)
    – Musical Alien May 25 '19 at 21:15
  • Musical Alien, thanks for the comment.Yes, 100% sure.
    I then began to ask friends and acquaintances who have my application with a request to send a screenshot.
    All of them sent an already updated version, with new features that I added.
    Although I did not pour anything in there at all.

    I just can not find a rational explanation, except that the Expo can somehow update itself bypassing the playmarket and app.
    – Chinese Paintball May 25 '19 at 21:54
  • Chinese Paintball, and in this case, the build command also performs publish and your changes are published in the current build, if OTA is not disabled.

    Alternatively, use the pull channel, for example:
    expo build: ios --release-channel prod-100
    and for the beta version
    expo build: ios --release-channel prod-101

    In this case, if your friends have a release build with prod-100, and you test and send to prod-101 beta, this update will not come to them
    As soon as you release a beta into the release, your friends will also get a build with the channel prod-101

    accordingly, you can send OTA updates using
    expo publish --release-channel prod-101
    – Musical Alien May 25 '19 at 22:00
  • Musical Alien and what is OTA?
    And I can not understand here I entered the command:
    expo build: android
    Why did the application update with the owners of IOS.

    In general, your comment is the answer to the question.
    Thank you very much.
    – Chinese Paintball May 25 '19 at 22:08
  • OTA - updates by air
    You can disable them, but they are useful for minor edits: )

    when build: android starts publish, which applies to both platforms
    – Musical Alien May 25 '19 at 22:11
  • Musical Alien, Thank you! This is how you opened my eyes.
    If you want, you can post your comment back.
    Since this is a real solution.Maybe someone else will come in handy, just as I did not step on this rake.
    – Chinese Paintball May 25 '19 at 22:53

1 Answers 1

in this case, the build command also performs publish and your changes are published in the current build, if OTA is not disabled.
You can disable them, but they are useful for minor edits: )

when build: android, publish is launched, which applies to both platforms

Alternatively, use the pull channel, for example:
expo build: ios --release-channel prod-100
and for the beta version
expo build: ios --release-channel prod-101

In this case, if your friends have a release build with prod-100, and you test and send to prod-101 beta, this update will not come to them
As soon as you release a beta into the release, your friends will also get a build with the channel prod-101

accordingly, you can send OTA updates using
expo publish --release-channel prod-101