Once you have your game created, you can start to develop and debug.
- Make sure you are logged into Developer Console.
- Go to the detail page of the game you'd like to debug against.
- Open the Debug URL
- You'll be navigated to the game. And it will start the game session as a mock user. The user's data and state will not persist after closing the game.
- Open the game in desktop browser first by following the instructions written above.
- Start your game local hosting, e.g. your game is hosted at
- Find the game's Debug URL, append
&game_url=https://localhost:8080/to it, and navigate.
- Now you can find the local game running in the browser and you can debug against it.
Same steps can be also applied to mobile browsers. Please note some features relying on Link app (e.g. Messaging, In-App Purchase, Ads) will not work in this case and throw
CLIENT_UNSUPPORTED_OPERATION errors. In order to test those features, please upload, deploy and test directly in Link app.
Please note when you host
https://localhost with a self signed certificate. By the browser's setting, the certificate may be recognized as an invalid one. This will stop loading any resource from
https://localhost, resulting in loading screen stuck at 0%.
In that case, please double check if there's a security alert in the address bar, and make sure the self signed certificate is trusted. If you happen to be using Chrome, please consider enabling
There're some handy features we have implemeneted in the debug mode, to enable developers to test some edge cases before testing on a native app.
By default, you'll start the game as the number
0 dummy user, and in the contact list you can find the other dummy user from
It's a known issue to have the current user in the contact list. A bugfix will address this issue soon.
5 are already playing this game, while
8 are non-playing users (who don't have a player ID).
You can append
?override_uid=0 parameter to the URL (available from
5) to start the game as a specific user. All these users share the same contact list, so you can send message between them to create contexts.
When calling API that triggers sending a message, such as
LinkGame.shareAsync(), a preview modal will show you how the message looks like, and a link to simulate the situation when the message is opened.
Developer can combine this link with
?override_uid= parameter to simulate the situation when the link is opened by either the sender or the receiver.
It's a known issue that the link should present
https://lg.rgames.jp/debug/ instead of
https://one.rakuten.co.jp/miniapp/games/. A bugfix will address this issue soon.
It's a known issue that sending message to user
8 will reject with an error, which should be resolved without any error. A bugfix will address this issue soon.
It's a known issue that the image in the message doesn't show as the same dimension in native app. A bugfix will address this issue soon.
It's a known issue that the update message doesn't show a link in the preview. A bugfix will address this issue soon.
It's a known issue that the share message prompt doesn't clean its state every time after getting shared, which will need a reload to enable sharing with the same user again in the same game session. A bugfix will address this issue soon.