AquaMail Updater

[Soko]

Hello,

I had the same problem here.

Saved configuration, deinstalled Aquamail, reinstalled it from market and then used the updater...

Worked and needs less than 2 minutes.

Ciao,
Joachim

[Kostya Vasilyev]

Sometimes I make internal builds (with five number groups, like 1.5.0.21.4) -- and they usually have the same "versionCode" as what they're based on. If the updater is not supposed to download and install those, then there probably should not be a notification...

[grumpy]

Thanks Kostya
I didn't spot that the version number has effectively gone down rather than up (i.e. you are using 1.5.0.... when the published version is 1.5.1....). Presumably this is what is confusing the updater and why we would need to re-install rather than install over the top. Wonder if @pyler can fix this?

[pyler]

You cant downgrade apps normally.
Kostya decided not to share 1.5.1 to stable TXT for AMU so I can do nothing.

[mikeone]

Thanks Kostya
I didn't spot that the version number has effectively gone down rather than up (i.e. you are using 1.5.0.... when the published version is 1.5.1....). Presumably this is what is confusing the updater and why we would need to re-install rather than install over the top. Wonder if @pyler can fix this?

The build number went always up from published version 1.5.0.19 in play store to last staple version 1.5.0.22.3 in the internal download section.
That's what AquaMail Updater is supporting.
If you have installed the preview of the next version 1.5.1.x you are out of the usual update procedure....

[pyler]

Maybe 1.5.1 can go to beta "channel"?

[mikeone]

Maybe 1.5.1 can go to beta "channel"?

This sounds like a good idea.

[Kostya Vasilyev]

There will be a few more 1.5.1 versions before it starts hitting Play.

[pyler]

Well, I ment beta as xversion-aquamail-market-beta, not as beta in Google Play

[mikeone]

Well, I ment beta as xversion-aquamail-market-beta, not as beta in Google Play

So that was also my understanding.

[g6agarwal]

Which is the latest version??

[pyler]

We, there is quite a chaos here. But I can do nothing, Kostya has final word. If he shows X build to AMU, AMU will see it and offer it to download.

[mikeone]

We, there is quite a chaos here. But I can do nothing, Kostya has final word. If he shows X build to AMU, AMU will see it and offer it to download.

In my opinion it's not really a "chaos":
The 1.5.0.23 build is indeed the latest "stable" version and the 1.5.0.23.1 is only a small preparatory step through the next stable version, e.g. the 1.5.0.24 build.

[Kostya Vasilyev]

Correct.

Even though I doubt that there will be more Google Play updates to 1.5.0 (latest is 1.5.0.19), I do get bug reports from time to time and fix them, and send new builds to those users. Those builds have minimal changes just to fix whatever issue that particular user reported (and I fixed). I also post those builds here (what the hell, why not).

There is a separate branch of source code where I work on 1.5.1, and I posted the first (and so far the only) build from that branch. For example, Android Wear support (for which I got zero feedback so far -- does anyone here have one?). The next build from this branch, let's say "-dev2", will hit Google Play as a "Beta".

So it's just like Microsoft releasing updates to Windows 8.1 and at the same time there is a preview for Windows 10.

Or Android L and Android 4.4 (oh wait, they stopped at 4.4.4).

[Soko]

Hello Kostya,

Android Wear support (for which I got zero feedback so far -- does anyone here have one?).

I'm waiting for a moto 360. Should be available end of october. You'll get feedback as soon as i have the device...

Ciao,
Joachim