Can not confirm on either RC or staging

i confirm if you use this package https://developer.joomla.org/cms-packages/Joomla_3.5.0-beta6-dev-Beta-Full_Package.zip in a clean install and then try to update to joomla 3.5.0 RC using testing channel

but i think this is because the test joomla update xml is not updated. It still says 3.5.0-beta5 and it should be 3.5.0-rc and for version 3.[34] when it should be 3.5 3.[345].
See https://update.joomla.org/core/teststs/extension_sts.xml

@wilsonge @mbabker can you check?

Anyway it should not find the update in that case.

3.5 is probably purposefully left out since you can't update between
beta/RC releases.

On Saturday, March 12, 2016, andrepereiradasilva notifications@github.com
wrote:

but i think this is because the test joomla update xml is not updated. It
still says 3.5.0-beta5 and it should be 3.5.0-rc and for version 3.[34]
when it should be 3.5 3.[345].
See https://update.joomla.org/core/teststs/extension_sts.xml

@wilsonge https://github.com/wilsonge @mbabker
https://github.com/mbabker can you check?

Anyway it should not find the update in that case.

—
Reply to this email directly or view it on GitHub
#9392 (comment).

you can't update between beta/RC releases.

@mbabker i've been doing that in 3.5.0 betas (i think)

Also don't know why you should't ...
From a beta/rc to a stable i understand you can't, but from beta 1 to beta 2 ... i think it should be possible.

Usually the thing that breaks this if you don't know what you're doing is
the database update later. If you edit an old schema file between betas
then the only way to get back in sync is with the Fix button. So the
marketing message is beta upgrades are unsupported.

On Saturday, March 12, 2016, andrepereiradasilva notifications@github.com
wrote:

you can't update between beta/RC releases.

@mbabker https://github.com/mbabker i've been doing that in 3.5.0 betas
(i think)

Also don't know why you should't ...
From a beta/rc to a stable i understand you can't, but from beta 1 to beta
2 ... i think you should.

—
Reply to this email directly or view it on GitHub
#9392 (comment).

ok i see

this is some kind of bug in the updater, not related to any version in particular.

if, for instance, we put <php_minimum>9.9.99</php_minimum> on a valid update or even <targetplatform name="joomla" version="9.9" /> on a valid update that error will appear instead of saying there are no updates.

In other words if the current joomla version doesn't fill some requirements of the update this error will appear.

This happens in latest staging (if you read a custom xml with an higher version) and in older versions too (i tested 3.4.8).

So it's seems this is a bug not a regression.

even if you replace the xml (https://update.joomla.org/core/teststs/extension_sts.xml) by just

<?xml version="1.0" ?>
<updates>
</updates>

this error will appear

OK So i added a extra line in the stream for nic (joomla/update.joomla.org@85e42c0) to help him test a Joomla Update feature he's writing. So it's my bad not updating the extension_sts file as well I guess!

Actually this allows to found a problem in the joomla update. :)
See this PR i made #9401 i tried to explain the problem.

closing as we have a PR.