Closed lcuis closed 2 years ago
Hello,
Our issue was due to a misunderstanding of what Adapty.getPurchaserInfo(forceUpdate:true)
is meant to be doing.
Sorry for the inconvenience.
Hello,
Our issue was due to a misunderstanding of what
Adapty.getPurchaserInfo(forceUpdate:true)
is meant to be doing.Sorry for the inconvenience.
Hi! I have the same problem :(What is your solution? How do you check the subscription status when you log in to the app?
Hello @OlegGrizzly ,
I went through my code history from that time. Unfortunately, there were lots of changes. However, regarding getPurchaserInfo
specifically, there were not that many.
I set forceUpdate
to false.
I check that the returned AdaptyPurchaserInfo
accessLevels
is not null and not empty before accessing the values.
I believe that at the time, going through this page helped me: https://docs.adapty.io/docs/ios-subscription-status
I wish you luck with this issue @OlegGrizzly !
Hi,
We get an astonishing behavior in the sandbox. When newly created app user logs in from Android, the
Adapty.getPurchaserInfo(forceUpdate:true)
returns a complete list ofaccessLevels
. Then, the same app user on iOS, also gets the complete list ofaccessLevels
. However, when the newly created app user first logs in from iOS, the same user gets an emptyaccessLevels
usingAdapty.getPurchaserInfo(forceUpdate:true)
from iOS and Android.Here is how we call
Adapty.getPurchaserInfo( forceUpdate:true)
:Here is how we call
Adapty.identify(userId)
:Here are our logs (edited to avoid sharing private information) with full Adapty verbosity when performing the identify and getPurchaseInfo (among other events) from iOS:
We looked at reasons for this inconsistent behavior within our app and our server. So far, we do not have any hunch.
Is there any potential reason for this from an Adapty perspective?