Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.
Sign upStub installer to first run conversion #2784
Comments
|
@mbacchi Still working on finalizing this change, but wanted to give you a heads up that this is planned for Hotfix 2 and will require a new build of Omaha when it lands. |
|
Big thanks to @emerick for helping out with the setup! Fiddler SetupIn Fiddler go Configuring WinHTTP’s ProxyOn Windows 8/10 x86 x64, Stub Installer 32 and 64 bit:In cmd.exe with administrative privileges, run
On Windows 7 x64, Stub Installer 64 bit; On Windows 7 x86, Stub Installer 32 bit:In cmd.exe with administrative privileges, run
On Windows 7 x64, Stub Installer 32 bit:In cmd.exe with administrative privileges, run
Important: The server code is not on production yet, it will be 11-01-2019. So all the pings will have 404. This is how it should look when everything is fine: Notes:
|
|
Thanks for gathering all the info and going through this issue @btlechowski |








Description
We currently have stub installer download vs first run mismatch. This issue is to investigate how to improve that with a ping for stub installer successfully run, base installer downloaded, and installer run.
Test Plan
Tests require running a packet sniffer like Fiddler or coordinating with @aekeus to view server logs. You can set the
BRAVE_UPDATE_SERVERenvironment variable to point to the staging server for testing purposes.Testing with No Referral Code
startup,download-complete, andinstaller-runping to the update serverref=noneTesting with Unwhitelisted Referral Code
Referral code whitelist is viewable here: https://github.com/brave/omaha/pull/19/files#diff-ce3476268c7af8bc284a899b3c716e29R187
startup,download-complete, andinstaller-runping to the update serverref=noneTesting with Whitelisted Referral Code
startup,download-complete, andinstaller-runping to the update serverref=XXXYYY, whereXXXYYYis a whitelisted referral codeCC @aekeus