-
Notifications
You must be signed in to change notification settings - Fork 289
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fixes asynch launchTwa freezing splash screens #297
Conversation
- Moved code that builds the splash screen strategy to run on `onCreate()`, so they will already be available when `onEnterAnimationComplete()` is invoked. - When `finish()` is called early, on `onCreate()`, to bring an existing Activity to front, `launchTwa()` shouldn't be invoked. - We update the Firebase demo to reflect that and add a guard in `launcTwa()`.
- Uses an early return in the Firebase demo
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM with comment nit.
// The Activity was finished before the launch because an existing instance of | ||
// the app was brought to front. We don't want to call launchTwa() in this case. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I find this comment a little confusing - would you be happy with:
super.onCreate may have called finish, in this case, don't do any work.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
done.
You guys work fast, thanks for fixing! |
Can we bump the version up to include this fix? Thanks! |
This has been published on |
onCreate()
, so they will already be available whenonEnterAnimationComplete()
is invoked.finish()
is called early, ononCreate()
, to bring anexisting Activity to front,
launchTwa()
shouldn't be invoked.launchTwa()
.Closes #281