Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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
[Android][libs] Introduce GetLocalUtcOffset temporary fast result #74459
[Android][libs] Introduce GetLocalUtcOffset temporary fast result #74459
Changes from 8 commits
a3f0e9f
a44084a
1edaeee
0712f57
96bf37f
582c359
9a2a8a2
f352b3a
f7dc8e9
32451c8
1a55a0c
61af7b7
50ff121
b1531b6
533ad1c
ef7729e
55fcccc
1cfc352
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
Like @eerhardt mentioned the 1 second here, a slow app could be more than 1 second, is there a way this can use
ManualResetEvent
? (or whatever the "good" reset event is)Then something in xamarin/xamarin-android, maybe
Android.App.Activity.OnCreate()
could call into the runtime. @grendello do you have any thoughts how we could signal to the runtime the app is done loading?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.
If the app takes more than 1s to start, then the time to load TZ doesn't really matter. There's no reason to complicate the code with signalling, especially that Android is notoriously hard in this respect... The app is done loading when the
Displayed: app
line is output to logcat, but there's no way to catch that event in the app itself.1s is very generous, but we can increase it to 1.5s if we think this is better. However, anything above ~700ms is perceived as "slow" by the user, so I really wouldn't worry about this.