Other Issues

A collection of FAQs related to using other Hive products.


Hive Certification Key-based API end of service and transition to JWT-based APIs FAQ
  1. Which APIs are subject to the transition?
  2. Where can I check client_id and client_secret?
    • You can check them after creating a security key in the Hive Console > App Center > Security Key Settings menu. For details, see the related console guide.
  3. Do I need to issue a separate OAuth Token for each App ID?
    • OAuth Tokens are issued per project, so you do not need to issue one for each App ID.
    • A token issued with any one of the App IDs in the same project can be used across all platforms and App IDs within that project.
  4. Do earlier tokens expire when I issue a token multiple times?
    • They do not expire. Each time you call the token issuance API, a new token is created, and each token is valid for one hour from the time it was issued.
    • However, frequent token issuance calls can put a load on the server, so we recommend caching and reusing an issued token until it is close to expiring or token verification fails.
  5. Are existing tokens invalidated immediately if the client_id changes?
    • The client_id cannot be changed arbitrarily after it is issued. In addition, an issued token remains valid until its own validity period (one hour) expires.
  6. Does the app client need to take any action?
    • X-Access-Token is either the User Token returned from the app client or the OAuth 2.0 Access Token, depending on the authentication method. For details, see the Verify token guide.
    • Server APIs called after initialization and SignIn in the app (such as token verification and account deletion) must receive the PlayerInfo.accessToken value from the app client and use it as the X-Access-Token header value.
    • PlayerInfo.accessToken is valid for one hour. When the token expires, call the AuthV4.refreshAccessToken() method of the Hive SDK and pass the refreshed token to your app server.
If you try to purchase from Google Play and see "The item that you were attempting to purchase could not be found"
  • You must have the Google Play app (the Market app) installed and Google Play Services enabled on your device.
  • The account that set up the payment method must be registered in the Market app, and the app must be launched at least once to keep the Market Terms agreement up to date.
  • The keystore file that signed the build registered in Google Console must be the same as the keystore file for the app you're testing.
  • You must be released to at least alpha in Google Console Release Management > App version.
  • The Google account registered on the device must be registered as a tester for the released version.
  • Even if the account registered to the device is enrolled as a Google Console tester, the device account still needs to opt-in via the “Test Join URL” in Google Console Release Management.
  • For more information, see the Google Developer
Setting Google Cloud API usage limits

When using the PGS login provided by Hive, a new PGS profile is created when a user checks the “Create, edit, or delete Google Play game activity” box, which will use the Google Cloud APIs.

API usage is set to 10,000 by default and will throw an error if the request is exceeded, so you'll need to apply for an increase before your game launches.

See the Google Cloud