Updated FirstRunActivity#exitFirstRun() to skip FRE for pending intent.
The old handling of exitFirstRun() simply relaunched the pending intent. This turned out to be a problem because the intent dispatcher read the durable settings for if the FRE was needed, and would decide it was. Interestingly, there can only be one FirstRunActivity active at a time, and so the relaunch was actually ignored. This would cause the existing FirstRunActivity get stuck because the replacement activity was never started. This fixes the problem by introducing a new "ephemeral" static variable that remembers we just decided to skip the FRE, so the next intent dispatch/routing will be aware of this decision. Bug: 1106987 Change-Id: Id8502956236f76c93091452fe580ae0d6fea2c80 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2343553Reviewed-by:Yusuf Ozuysal <yusufo@chromium.org> Reviewed-by:
Theresa <twellington@chromium.org> Reviewed-by:
Wenyu Fu <wenyufu@chromium.org> Commit-Queue: Sky Malice <skym@chromium.org> Cr-Commit-Position: refs/heads/master@{#799483}
Showing
Please register or sign in to comment