Closed karimsinouh closed 7 months ago
Hello, @karimsinouh. In order to help you we will need more information on your specific case including sensitive one. Could you please contact us using the support button on the bottom right of our documentation page?
This issue is stale because it has been open 7 days with no activity. Remove stale label or comment or this will be closed in 5 days.
This issue was closed because it has been stalled for 5 days with no activity.
@karimsinouh Did you ever find a solution for this? We are facing the same issue...
@SpertsyanKM can you please reopen the issue?
@WiseKodama unfortunately I couldn't find a solution. Didn't get help from the support either, so I switched to another billing library
@WiseKodama unfortunately I couldn't find a solution. Didn't get help from the support either, so I switched to another billing library
That's what I was afraid of... I am not getting a response from support either or any of the devs on GitHub... Thank you for letting me know.
Hello! I'm sorry for the late reply. We are facing a high volume of support requests now, that's why it takes some time to reply. But I really want to help you!
The problem from this issue depends on a variety of different things and to check all of them we might need some sensitive information from you, that is why we ask you to contact us via the support chat.
Hello! I'm sorry for the late reply. We are facing a high volume of support requests now, that's why it takes some time to reply. But I really want to help you!
The problem from this issue depends on a variety of different things and to check all of them we might need some sensitive information from you, that is why we ask you to contact us via the support chat.
I have provided code samples, Qonversion user IDs and exact issues. I have yet to receive a reply from support.
@karimsinouh I'm sorry to hear that. If I can fix that situation, I would be happy to.
@WiseKodama give me a while, I'll try to find your request
Found it. Let's continue our conversation there.
Found it. Let's continue our conversation there.
That's the one, though we also have a Native Android app that is facing the issue, that is why I "reopened" this issue as well.
Copying my reply here for historical purposes.
We had an issue on our side with handling Android consumable/non-consumable in-app purchases from the last two major versions of our SDKs (for Android SDK it's 7.0.0+). The bug has been relevant from the 9th of July till yesterday when we released the fix.
So if the problem occurs for consumable/non-consumable in-app purchases during the mentioned period, just try to reproduce it now - everything should work well.
HI, I have same problem for android-sdk version 8.0.1 Can you help me? What do you need information to help me?
@SpertsyanKM to lean on fellow colleague @WiseKodama's request, we're still experiencing the "empty entitlements map" issue after a successful (non-)consumable test in-app purchase (test Google Play card) on Android Qonversion SDK, both on 7.5.0 and 8.0.1. Could you doublecheck that Qonversion BE changes from last week didn't get reverted?
Order number: GPA.3394-1503-2423-20039
After successfully subscribing to a plan, the QonversionEntitlementsCallback callback returns an empty map. I can't know whether the subscription is active or not if the map is empty {} I'm using version 7.2.0