SyncPlay, don't use bad ApiClient #2183
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.
I think this is more a hack than a fix.
In multiserver app (Tizen), SyncPlay starts too early and undefined
apiClient
is passed to it.SyncPlay probably requires some changes to support server switching (cc @OancaAndrei).
Changes
apiClient
before use.ApiClient
.Issues
In multiserver app, undefined
apiClient
is passed to SyncPlay.How to check multiserver with DevServer
mutliserver
yarn serve
localStorage
for DevServer.