More specifically : 20160101165805 <https://aus5.mozilla.org/update/5/B2G/46.0a1/20160101165805/flame/en-US/nightly/Boot2Gecko%202.6.0.0-prerelease%20%28SDK%2019%29/default/default/> is a newer build id than the current build id in nightly channel
You would have to switch back to nightly-latest if you want a newer build on the phone without QA testing. We never sanctioned the 20160101165805 <https://aus5.mozilla.org/update/5/B2G/46.0a1/20160101165805/flame/en-US/nightly/Boot2Gecko%202.6.0.0-prerelease%20%28SDK%2019%29/default/default/> build in QA. And no, it's not a bug that the channel switched back to nightly from nightly-latest, that's by design. There's a bug where a dev hardened the channel to revert back to whatever the build variable was set to for the channel. <https://aus5.mozilla.org/update/5/B2G/46.0a1/20160101165805/flame/en-US/nightly/Boot2Gecko%202.6.0.0-prerelease%20%28SDK%2019%29/default/default/> On Wed, Jan 13, 2016 at 3:48 PM, A. Crespo <[email protected]> wrote: > Hi :nhirata, as far as I know, my build was old enough to have a newer > nightly build. Like two or three weeks. > _______________________________________________ > dev-fxos mailing list > [email protected] > https://lists.mozilla.org/listinfo/dev-fxos >
_______________________________________________ dev-fxos mailing list [email protected] https://lists.mozilla.org/listinfo/dev-fxos
