This issue was reported than closed 2 years ago https://issues.joomla.org/tracker/joomla-cms/6920
I experienced an update issue for my package (J!TrackGallery) when the minimum stability (MS) of the package (RC) is lower then the one require by Joomla website (stable in my case).
Using Joomla 2.5.19 this package is correctly update using the update server
Using Joomla 3.6.5 or 3.7.5 the update fail with message Error Invalid extension update
Using Joomla 3.6.5 or 3.7.5 the update success if package MS is set higher or equal to joomla MS
using Joomla >3.6 with installer MS set to stable
install a old version of one package for example http://jtrackgallery.net/downloads/J-TrackGallery-0.9.23.zip
search for updates
try to update pkg_jtrackgallery (the proposed 0.9.27 is a RC)
N.B. It's better trying upgrading 2 packages at the same time for final testing: one with correct MS and the other with insufficient MS
a message should indicate that update is not allowed due to insufficient stability
The update fails with message Error Invalid extension update whilst the extension update file is correct
No messge indicates which update failed (when upgrading several package at the same time)
My extension was fired from the JED because
"The extension violates the JED Submission checklist:
Site Package 0.9.25 0.9.27 N/A Update http://jtrackgallery.net/downloads/J-TrackGallery-updates.xml
this update is not working, it just gives a error without Information
Please, fix the autoupdate process, resubmit the fixed extension and submit a ticket in Unublished section in order to get listed again."
I investigated this issue in more detail and concluded that when Joomla check an xml update file, scanning all tags the 'invalid extension error' arises when at least one of these conditions is raised:
Futhermore, when upgrading 2 packages at the same time:
|Closed_Date||0000-00-00 00:00:00||⇒||2017-09-26 21:05:51|
pull request : #18132
Three questions about this pull request:
1- Does the upgrade extension manifest file contains only one component or one package?
if no, giving the package name in the error message is not relevant.
2- Another possible way to solve this issue could be:
only browse upgrade satisfying PHP Database and minimum stability. This seems quite uneasy and need more code change
3- A user can install an extension with lower minimum stability (RC as exemple) then Joomla requirements (Stable). This install will success. Future upgrade with same Minimum stability RC will fails whilst the user already accepted the low minimum stability of this extension. For this reason, a clearer warning message should be issued as proposed in the pull request.