Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

RevenueCat purchases not updating in Google/Firebase Analytics. #1089

Open
5 tasks done
Agusioma opened this issue Jun 24, 2023 · 4 comments
Open
5 tasks done

RevenueCat purchases not updating in Google/Firebase Analytics. #1089

Agusioma opened this issue Jun 24, 2023 · 4 comments

Comments

@Agusioma
Copy link

Describe the bug
A clear and concise description of what the bug is. The more detail you can provide the faster our team will be able to triage and resolve the issue. Do not remove any of the steps from the template below. If a step is not applicable to your issue, please leave that step empty.

  1. Environment
    1. Platform: Android(Firebase Analytics)
    2. SDK version: 6.0.0
    3. OS version: Android
    4. Android Studio version: Android Studio Flamingo | 2022.2.1
    5. How widespread is the issue. Percentage of devices affected: 100%
  2. Debug logs that reproduce the issue: N/A. It's a thirsparty integration issue
  3. Steps to reproduce, with a description of expected vs. actual behavior:
    The same issue under discussion here.
  4. Other information (e.g. stacktraces, related issues, suggestions how to fix, links for us to have context, eg. stackoverflow, etc.)

Additional context
RevenueCat purchases not updating in Google/Firebase Analytics.

@Agusioma Agusioma added the bug label Jun 24, 2023
@RCGitBot
Copy link
Contributor

👀 We've just linked this issue to our internal tracker and notified the team. Thank you for reporting, we're checking this out!

@tonidero
Copy link
Contributor

Hi @Agusioma! Thanks for reaching out!

Could you provide more details about your setup and how you're testing this?

In the meantime, this is the documentation for our firebase integration: https://www.revenuecat.com/docs/firebase-integration.

Please make sure you've followed all those steps. If the issue persists, please send us some logs so we can take a closer look.

@Agusioma
Copy link
Author

@tonidero yes I followed all the steps. No logs coming out, just an empty response in the firebase integrations logs. Below is an example of the request body:

{
  "app_instance_id": "dx_pao6MSRWf9SOZb_DkhX",
  "events": [
    {
      "name": "purchase",
      "params": {
        "affiliation": "PLAY_STORE",
        "app_id": "appbXXXX",
        "coupon": "",
        "currency": "KES",
        "environment": "SANDBOX",
        "event_id": "c3771909-8e89-4912-b722-188d9c70521f",
        "expiration_at": 1687607589990000,
        "is_renewal": true,
        "is_trial_conversion": false,
        "items": [
          {
            "affiliation": "PLAY_STORE",
            "item_id": "rc_sub_premium:pro"
          }
        ],
        "original_app_user_id": "$RCAnonymousID:02967b5b1ca34b7a99629b707c54aedd",
        "original_transaction_id": "GPA.3373-4651-9140-88706",
        "period_type": "NORMAL",
        "presented_offering_id": "gold-offer",
        "product_id": "rc_sub_premium:pro",
        "purchased_at": 1687607289990000,
        "transaction_id": "GPA.XXX3-46XX-9140-88706..3",
        "value": 500
      }
    }
  ],
  "user_id": "$RCAnonymousID:02967b5b1ca34b7a99629b707c54aedd"
}

And here is the response:

"empty"

And response headers if they may help:

{
  "Alt-Svc": "h3=\":443\"; ma=2592000,h3-29=\":443\"; ma=2592000",
  "Cache-Control": "no-cache, no-store, must-revalidate",
  "Content-Length": "0",
  "Content-Type": "text/plain",
  "Cross-Origin-Resource-Policy": "cross-origin",
  "Date": "Sat, 24 Jun 2023 11:53:00 GMT",
  "Expires": "Fri, 01 Jan 1990 00:00:00 GMT",
  "Last-Modified": "Sun, 17 May 1998 03:00:00 GMT",
  "Pragma": "no-cache",
  "Server": "Golfe2"
}

@tonidero
Copy link
Contributor

Hi @Agusioma, let me ask the team and we will get back to you.

@vegaro vegaro removed the bug label Aug 25, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants