Attempt to address reported NPE on startup #236
Merged
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.
Linear Ticket: SDK-2311
Changes:
null
value and then emits the desired value in the new-at-the-bottominit
method? This goes along with the above. If I move the property initializers above the "source" properties, I don't want the source property initialization to happen before the flows are created.emit
calls withtryEmit
, which removes the need for launching in a coroutine. Both methods are thread-safe, but maybe that gets out-of-whack when the emissions were launched in the application-level scope (ie: trying to call a method from Thread 2 on a property created on Thread 1)? We don't need the suspending fallback ofemit
because we're the only ones observing these flows AND we're guaranteed to not be listening to them until AFTER the session storages have been initialized due to the lazy delegation in the clients.Notes:
Checklist: