BASIC

Author Topic: inApp issues  (Read 233 times)

Offline MrPlow

  • Prof. Inline
  • *****
  • Posts: 1300
    • View Profile
inApp issues
« on: 2018-Jun-10 »
Hi

Anyone know of a method for verifying the inapp purchase without using inAvailable() function?

My isAvailable is just returning the same value regardless of purchase!

IsAvailable() = fetches value but it always the same
Activate() = works are normal and allow purchase

I am trying out using the inapp_purchase$ string value as the means to record a hidden text file to validate the purchase if the text file is detected...my assumption is that the inapp_purchase$ string is populated after a successful purchase transaction and then I create the file.

Unless anyone can think of a better way to fix this issue - the app was initially in Beta so that might be the cause of the breaking of inAvailable value return.

Thanks
Comp:
Speccy-48k, Speccy-128k, Amigas, PCs

Offline spacefractal

  • Community Developer
  • Prof. Inline
  • ******
  • Posts: 3447
    • View Profile
    • Space Fractal
Re: inApp issues
« Reply #1 on: 2018-Jun-11 »
How often do you check. This command is asyscroll and can take some secs or such after a app launch.
Greedy Mouse - Karma Miwa - Spot Race - CatchOut - Android Extras - is on a vacation trip, home before end of few days in jan.

Offline MrPlow

  • Prof. Inline
  • *****
  • Posts: 1300
    • View Profile
Re: inApp issues
« Reply #2 on: 2018-Jun-11 »
Once per loop - it works for other apps just fine.

But maybe the api-23 declaration is affecting it or the fact the app was in Beta programme.
Something is preventing the isAvailable check - but as said it allow buy and wont allow a re-buy just like normal so wondering if there is another check I can use for a workaround "hack"?

 
Comp:
Speccy-48k, Speccy-128k, Amigas, PCs

Offline spacefractal

  • Community Developer
  • Prof. Inline
  • ******
  • Posts: 3447
    • View Profile
    • Space Fractal
Re: inApp issues
« Reply #3 on: 2018-Jun-11 »
check in the function its self. There was bug in one of the versions, that just returned true (or was its false)? Not remember. But currectly im have no clue and also cannot checkitout as well.

its can also been a issue in the init as well (etc dev key is not set in strings.xml example). But its some time ago im did this one.
Greedy Mouse - Karma Miwa - Spot Race - CatchOut - Android Extras - is on a vacation trip, home before end of few days in jan.

Offline MrPlow

  • Prof. Inline
  • *****
  • Posts: 1300
    • View Profile
Re: inApp issues
« Reply #4 on: 2018-Jun-11 »
check in the function its self. There was bug in one of the versions, that just returned true (or was its false)? Not remember. But currectly im have no clue and also cannot checkitout as well.

its can also been a issue in the init as well (etc dev key is not set in strings.xml example). But its some time ago im did this one.

Thanks SF!
Is that a buf in glb code function or a function in Shop.java?
Comp:
Speccy-48k, Speccy-128k, Amigas, PCs

Offline spacefractal

  • Community Developer
  • Prof. Inline
  • ******
  • Posts: 3447
    • View Profile
    • Space Fractal
Re: inApp issues
« Reply #5 on: 2018-Jun-11 »
you might have init it wrong as well, etc item list march worng. you can log it out in the shop.java code. But again its some time ago, and cant revist it by now at all.
Greedy Mouse - Karma Miwa - Spot Race - CatchOut - Android Extras - is on a vacation trip, home before end of few days in jan.