450251 - Xulrunner Application update never starts downloading mar file for minor updates

Status: RESOLVED INCOMPLETE

(Toolkit Graveyard :: XULRunner, defect)

Description

[Marcin Raczkowski]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 6.0; pl; rv:1.9.0.1) Gecko/2008070208 Firefox/3.0.1
Build Identifier: 

We have problem with cusotm xulrunner application, when run it does download xml file with information about updates, if release is major - it does download file.

But if update is marked as minor, it never starts downloading the update mar.
It creates update.status - where it says downloading, but download request never hit servers.

any ideas? pointers? we are working second day on it, and we are stuck.

Xulrunner is mint 1.9
we are using http not https but major downloads so why not minor?

Reproducible: Always

Comment 1

[Dave Townsend [:mossop]]

What app.update preferences do you have set?

Comment 2

[Marcin Raczkowski]

we tried every app.update.mode from 0 to 3 including




pref("toolkit.defaultChromeURI", "chrome://myapp/content/contacts.xul");
pref("toolkit.defaultChromeFeatures", "chrome,dialog=no");
/* debugging prefs */
pref("browser.dom.window.dump.enabled", true);
pref("javascript.options.showInConsole", true);
pref("javascript.options.strict", true);
pref("nglayout.debug.disable_xul_cache", true);
pref("nglayout.debug.disable_xul_fastload", true);

// Whether or not app updates are enabled
pref("app.update.enabled", true);

// This preference turns on app.update.mode and allows automatic download and
// install to take place. We use a separate boolean toggle for this to make
// the UI easier to construct.
pref("app.update.auto", true);

// Defines how the Application Update Service notifies the user about updates:
//
// AUM Set to:        Minor Releases:     Major Releases:
// 0                  download no prompt  download no prompt
// 1                  download no prompt  download no prompt if no incompatibilities
// 2                  download no prompt  prompt
//
// See chart in nsUpdateService.js.in for more details
//
pref("app.update.mode", 0); 

// If set to true, the Update Service will present no UI for any event.
pref("app.update.silent", false);

// Update service URL:
// You do not need to use all the %VAR% parameters. Use what you need, %PRODUCT%,%VERSION%,%BUILD_ID%,%CHANNEL% for example
pref("app.update.url", "http://url.here.com/remote/updates?product=%PRODUCT%&version=%VERSION%&build_id=%BUILD_ID%&build_target=%BUILD_TARGET%&locale=%LOCALE%&ch=%CHANNEL%&os_version=%OS_VERSION%&dist=%DISTRIBUTION%&dist_ver=%DISTRIBUTION_VERSION%");


// URL user can browse to manually if for some reason all update installation
// attempts fail.
pref("app.update.url.manual", "http://url.her.com/");

// A default value for the "More information about this update" link
// supplied in the "An update is available" page of the update wizard.
pref("app.update.url.details", "http://url.here.com/");

// User-settable override to app.update.url for testing purposes.
//pref("app.update.url.override", "");

// Interval: Time between checks for a new version (in seconds)
//           default=1 day
pref("app.update.interval", 7200); //86400);

// Interval: Time before prompting the user to download a new version that
//           is available (in seconds) default=1 day
pref("app.update.nagTimer.download", 30); // 86400);

// Interval: Time before prompting the user to restart to install the latest
//           download (in seconds) default=30 minutes
pref("app.update.nagTimer.restart", 50); // 1800);

// Interval: When all registered timers should be checked (in milliseconds)
//           default=5 seconds
pref("app.update.timer", 5000);

// Whether or not we show a dialog box informing the user that the update was
// successfully applied. This is off in Firefox by default since we show a
// upgrade start page instead! Other apps may wish to show this UI, and supply
// a whatsNewURL field in their brand.properties that contains a link to a page
// which tells users what's new in this new update.
pref("app.update.showInstalledUI", true);

// 0 = suppress prompting for incompatibilities if there are updates available
//     to newer versions of installed addons that resolve them.
// 1 = suppress prompting for incompatibilities only if there are VersionInfo
//     updates available to installed addons that resolve them, not newer
//     versions.
pref("app.update.incompatible.mode", 0);

// suppress external-load warning for standard browser schemes
pref("network.protocol-handler.warn-external.http", false);
pref("network.protocol-handler.warn-external.https", false);
pref("network.protocol-handler.warn-external.ftp", false);
pref("toolkit.singletonWindowType", "xulmine"); swistak@swistak:~/sub

Comment 4

[Robert Strong (they/them - no direct email)]

From Bug 451031

Problem occurs when update is marked as minor. Xulrunner is not downloading
pointed update, but it creates dir structure (updates/0), and update.status
file. Status is marked as downloading.

Reproducible: Always

Steps to Reproduce:
1. Create update.xml, mark update type as "minor", and put it on update server.
2. Set preferences as described on
http://developer.mozilla.org/en/docs/XULRunner:Application_Update, change
app.update.url to your update server and app.update.interval to 10 seconds.
3. Run application and wait.
Actual Results:  
Update is marked as downloading, but .mar file is not even created, connection
is broren with tcp rst flag (sniffed with tcpdump and wireshark).

Expected Results:  
Xulrunner should download file and inform about available update.

I've done some research, and I find out solution. Problem seems to be in
nsUpdateService.js file. When DOWNLOAD_BACKGROUND_INTERVAL is set to 600
(default), or even 1, download won't start. But when i set it to 0, xulrunner
downloaded file normally and informed me about available update.

Comment 5

[Mike Kaply [:mkaply]]

Is this still a bug? I'm having trouble getting xulrunner updates to happen.

Comment 6

[Benjamin Smedberg]

XULRunner has been removed from the Mozilla tree: see https://groups.google.com/forum/#!topic/mozilla.dev.platform/_rFMunG2Bgw for context.

I am closing all the bugs currently in the XULRunner bugzilla component, in preparation for moving this component to the graveyard. If this bug is still valid in a XULRunner-less world, it will need to be moved to a different bugzilla component to be reopened.