App-related issues

Available in Classic and VPC

You might run into the following problems when using GAMEPOT. Find out causes and possible solutions.

Push notifications not arriving

Push notifications are not arriving.

Causes

• If the push token was not received correctly
• If push notification permissions were denied
• If push delivery failed with that token

Solution

• Check if push token was received.
  • In the GAMEPOT dashboard > Users > List menu, check if the token value for the relevant user is displayed correctly. If it is not displayed, check the code receiving the push token.
• Check push notification permissions
  • In the GAMEPOT dashboard > Users > List menu, check if the Agree to receive push field of the user is set to "Agree." If the status is not "Agree," change the push consent status to "Agree" using the push status change method.
• GAMEPOT considers failed push delivery as an inactive device and deletes the applicable token. Therefore, if push delivery fails, you must re-allow push notification permissions at least once for the token to be re-collected.
• For Unity
  • Push tokens may not be received due to the implementation of external SDKs outside GAMEPOT. Check files inheriting from UnityAppController to ensure there are no duplicate inheritance points. If duplicate inheritance exists, edit it to inherit from a single file.

Push notification error on Android OS 13 devices

Push notifications are not arriving on Android OS 13 or later devices.

Causes

• Starting with Android OS 13, the android.permission.POST_NOTIFICATIONS permission is required to display push notifications. The GAMEPOT SDK does not automatically support acquiring the android.permission.POST_NOTIFICATIONS permission.

Solution

The developer must implement this feature to obtain the android.permission.POST_NOTIFICATIONS permission at a specific point (e.g., when the user agrees to the terms of service or when the app launches). Additionally, if the user declines, the app must inform them that push notifications will not be received unless they manually enable notification permissions in the app settings.

Precautions when launching services on iOS platform

I'm curious about things to watch out for when launching services targeting the iOS platform.

Causes

/-

Solution

For the iOS App Store, the app review process typically takes about 1 to 2 weeks. Therefore, we recommend submitting your app for review with a buffer period of approximately 2 weeks.

iOS review rejection

The iOS review resulted in rejection.

Causes

The primary reasons for rejection during iOS review are as follows:

• If there are bugs, unfinished features that display phrases such as "coming soon," or the app contains phrases such as beta, test, etc.
• If the purpose and use of collected IDFA values are not clearly explained
• If the app induces app installs or review writing through rewards
• If there are errors in the test ID provided for reviewers to test
• If there is no withdrawal feature or if the app contains coupon functionality
• When utilizing screenshots of Android-powered screens or using low-resolution images, etc.

Solution

• App quality assurance
  • Ensure the app is final and complete. Develop it without including phrases like "beta" or "test."
  • Develop an account withdrawal feature.
  • Instead of an in-app coupon input feature, develop it to redirect users to a web coupon input page.
• Clearly state the purpose and intended use when collecting IDFA values.
• Do not incentivize app installations or reviews through rewards.
• Provide the test ID accurately to enable reviewers to conduct testing.
• Do not use screenshots of Android operating screens or low-resolution images.
  Link to Apple screenshot specifications