Closed Bug 570027 Opened 15 years ago Closed 15 years ago

Android fennec does not start with given URL on first run with a new profile

Categories

(Firefox for Android Graveyard :: General, defect)

ARM
Android
defect
Not set
normal

Tracking

(fennec2.0+)

RESOLVED FIXED
Tracking Status
fennec 2.0+ ---

People

(Reporter: cmtalbert, Unassigned)

Details

1. Create a new profile for fennec 2. Push profile to the device, say to /sdcard/profile 3. Launch fennec with command line: org.mozilla.fennec -P /sdcard/profile http://www.mozilla.org = Actual = When Fennec starts, it goes to the first run page = Expected = It should open the given URL and not the first run page. This seems to only happen when starting fennec with a new profile. To recreate specifically my scenario (on linux): 1. Build fennec with the crystax ndk and --enable-tests, install fennec on the device. 1.5 Install an sutagent on the device 2. run make package-tests in your objdir and unzip the tar.bzip of tests into a directory (call it mytests for purposes of illustration) 3. Drop unzip a linux nightly into mytests/bin 4. cd mytests/mochitest and run this command line: python runtestsremote.py --app=org.mozilla.fennec --remote-webserver=<your current ip address> --deviceIP=<IP of device> --xre-path=../bin and you'll see fennec will start with the first run page instead of the mochitest url even though this results into the following call to fennec (or something similar, if you don't have an sdcard installed): org.mozilla.fennec -no-remote -profile /sdcard/tests/profile/ http://mochi.test:8888/tests/?autorun=1&closeWhenDone=1 > /sdcard/tests/process.txt
It seems this happens not only on a new profile, but any time the component registration restart happens. (For example, I see it on Android any time I install a new version of the Fennec.apk package.)
tracking-fennec: --- → 2.0+
This was fixed by the elimination of the EM restart (bug 568691).
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → FIXED
Blassey pointed out in IRC that we are not actually setting NO_EM_RESTART in Fennec; anyway this bug is gone now.
You need to log in before you can comment on or make changes to this bug.