Initialize deviceInfo
in constructor of ParselyTracker
#58
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.
Closes: #57
Description
This PR addresses the issue reported in #57 by initializing
deviceInfo
synchronously in the constructor of theParselyTracker
, rather than waiting forGetAdKey
async task to complete.It brings back part of the behavior from before #56 (which introduced the discussed bug) but makes it more explicitly, that initial creation of
deviceInfo
passesnull
foradKey
property.Reproduction
trunk
PATCH
example
app and within 10 seconds tap on "track url" button.