Hi
My inapp has been working fine and other users have purchased successfully but wondering are there version of android that dont like the AE 2.9 version of in-app purchase?
im upgraded the StoreKit somewhere last year or this year to support inapp purchase v3, which was required.
the lastest version im uses is openiab-0.9.7.2.jar. If you uses older version, you should update AE and imply the changes, which was required (mostly sku and key configuration was changed a little bit, because some configuration was needed to been done directly in OnCreate()).
Also make sure to do something offline for some days before rechecking, which can been happens when device is in flymode or no connection.
Thanks SF,
how does the offline thing work? do i create a secret text file key?
I am using
openiab-0.9.7.2
So thats okay, other buyers are fine, just this buyer from canada is having issues i have asked for android device and android version info too.
also inapp purchases is asycron and might have caused some issues with that. Im not sure what happens at all. If its rooted, its can been property a issue as well. But im not sure.
After its validated, create a text file with a crypted date on it. Delete it after a week or such, so a revalidate is required. Here you need to do that by your self.
Thanks SF
Will do...
SF, the user tells me they are using Galaxy 5s and android 6.0.1
So could the "Documents" folder issue have any bearing here?
its could. Its more safe to use APPDATA, rather than DOCUMENT folder. Im thinks im should swap those two, but im did not do that to avoid compatible issue. So im leaved as its are.
On some devices, you cannot write to the document folder.
Rather than swapping, can you not do a background test? If one fails then try/use the other.
Quote from: Ian Price on 2016-Sep-19
Rather than swapping, can you not do a background test? If one fails then try/use the other.
Sounds like a good idea :)
Would probably need to use in conjunction with DOESFILEEXIST()?
Porvided the fail doesn't cause crashes?
On OUYA it's crashed after os update..... I'm not remember it's was write or read.
You can property check for read and then write to APPDATA.