You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Games are identified by 8 characters. However, these 8 characters can be proceeded by another 4 characters indicating the player POV (essentially, white or black). URLs with these full game IDs are often shared from desktop or mobile web, since they're contained in the browser URL at the end of (or during) a game.
The app does not intercept this 12-character full game ID, so visiting such a link on mobile will direct you to whatever browser is installed instead of the native app experience.
Suggestion
Intercept this app link and open the corresponding game, showing the corresponding perspective.
On desktop, when someone visits a URL with a POV that's not actually their own, they're redirected to the appropriate path, which is /<gameId>/<color> (or, in the case of white, just /<gameId>). Unfortunately, that is not the case when accessing the game via the API, but I imagine with a little server-side work, the API could return a reference to the game ID and the appropriate color perspective.
The text was updated successfully, but these errors were encountered:
Current situation
Games are identified by 8 characters. However, these 8 characters can be proceeded by another 4 characters indicating the player POV (essentially, white or black). URLs with these full game IDs are often shared from desktop or mobile web, since they're contained in the browser URL at the end of (or during) a game.
The app does not intercept this 12-character full game ID, so visiting such a link on mobile will direct you to whatever browser is installed instead of the native app experience.
Suggestion
Intercept this app link and open the corresponding game, showing the corresponding perspective.
On desktop, when someone visits a URL with a POV that's not actually their own, they're redirected to the appropriate path, which is
/<gameId>/<color>
(or, in the case of white, just/<gameId>
). Unfortunately, that is not the case when accessing the game via the API, but I imagine with a little server-side work, the API could return a reference to the game ID and the appropriate color perspective.The text was updated successfully, but these errors were encountered: