258476 - XULRunner doesn't launch my app

Status: RESOLVED INVALID

(Toolkit :: Startup and Profile System, defect)

Description

[Jan Varga [:janv]]

Here are some observations
- it displays "*** loading the extensions datasource" endlessly
- compreg.dat is created in the profile and then deleted in a loop

my .moz file:
[XRE]
Version=0.1
                                                                                
[App]
Vendor=Sparky.com
Name=IIS
Version=0.9
BuildID=2004090814
Copyright=Copyright (c) 2004 Sparky.com
                                                                                
[Shell]
Icon=chrome\icons\default\iis.ico

Comment 1

[Darin Fisher]

did you create a prefs file under defaults/pref/something.js?
 
you need to override these prefs:
 
  pref("app.id", "{0ac57cfd-1996-489b-beb6-93a1f417daf1}");
  pref("app.version", "1.0.2");
  pref("app.build_id", "2004080914");
  pref("app.extensions.version", "1.0.2");
 
the values i've given are copied out of one of my test apps.  you need to make
sure that the app.version and app.build_id are in sync with the values set in
your .moz file.  otherwise, EM will keep restarting the app.

Comment 2

[Jan Varga [:janv]]

(In reply to comment #1)
> did you create a prefs file under defaults/pref/something.js?
>  
> you need to override these prefs:

sigh, they were not in sync, thanks for the hint (now it works)
anyway, it seems that wrong app.build_id causes the loop

one thing, there should be probably separate chrome.rdf, too

Comment 3

[Darin Fisher]

> anyway, it seems that wrong app.build_id causes the loop

yeah... it seems to me that the extension manager should do something to protect
against this problem.  if we were not using firefox as XULRunner, then we would
not have firefox.js being loaded, and as a result none of the EM required prefs
would be set, so in that case we could potentially disable EM.  that's what i
hope to do once we have a separate XULRunner package.


> one thing, there should be probably separate chrome.rdf, too

the plan is to use the chrome.rdf that lives in the profile directory.  there
was one issue with that choice, which came up as bug 258491.

Comment 4

[Benjamin Smedberg]

(In reply to comment #3)
> > anyway, it seems that wrong app.build_id causes the loop
> 
> yeah... it seems to me that the extension manager should do something to protect
> against this problem.  if we were not using firefox as XULRunner, then we would
> not have firefox.js being loaded, and as a result none of the EM required prefs
> would be set, so in that case we could potentially disable EM.  that's what i
> hope to do once we have a separate XULRunner package.

In addition, we shouldn't need prefs for these. When we expose nsXULAppAPI as an
XPCOM service, the EM should take the data directly from there, and bypass the
prefs entirely. The EM also need documentation, but it needs to shake out and
stabilize first.

--BDS

Comment 5

[Darin Fisher]

my patch in bug 258470 allows XUL apps to completely bypass the EM code.