Search Unity

  1. Megacity Metro Demo now available. Download now.
    Dismiss Notice
  2. Unity support for visionOS is now available. Learn more in our blog post.
    Dismiss Notice

activityStartTrigger: not whitelisted -- com.unity.purchasing.googleplay.PurchaseActivity

Discussion in 'Unity IAP' started by r137, Nov 6, 2020.

  1. r137

    r137

    Joined:
    Mar 12, 2018
    Posts:
    47
    Hi,

    I am using Unity 2018.4.26f1 and latest versions of Unity IAP from package manager and services window. (2.0.6 and 2.1.1). This is the error I got when I click the iap button. In game on Android I got an error message "The item you requested in not available for purchase". This is not related to Google Play settings. Previous version of the app is working without any issue.

    What should I do? image_2020-11-06_181046.png 2020-11-06 18_12_28-.png
     

    Attached Files:

  2. JeffDUnity3D

    JeffDUnity3D

    Joined:
    May 2, 2017
    Posts:
    14,446
    Please share your code, the full device logs, and a screenshot that shows your Google dashboard settings for the ProductID that matches the ProductID in the code. Understood you claim it worked previously, but we need to cover the basics, thanks. Are you testing by side loading the new version, or going through Google Play testing after uploading the new build?
     
  3. JeffDUnity3D

    JeffDUnity3D

    Joined:
    May 2, 2017
    Posts:
    14,446
  4. r137

    r137

    Joined:
    Mar 12, 2018
    Posts:
    47
    Hi, Thanks for the quick response.

    Issue is solved. I was side loading the test builds with adb. The issue was I was using increased bundle version code. To clarify, this game is already published on Google Play and in app purchases are working on current published version. Current published version is 1.1.3 and its bundle version is 28. I was testing with a build with version 1.1.4 and bundle version 29 with adb (not uploading to Google Play). This caused the issue. Now I tested with bundle version 28 with side loading and issue is solved. This was hard to spot because test builds with bundle version 29 is working on co-developers test devices. So I guess this issue is device depended.
     
    JeffDUnity3D likes this.