Mainland China cannot access revenuecat ! How to solve it?

Hello,

Cesar from RevenueCat here,

We are aware of the situation and the team is looking into solutions to mitigate it

​@Cesar 

Use from China mainland, It looks like api.revenuecat.com DNS poisoning. 

DNS resolve to  104.244.46.5 or 173.252.105.21 which should not correct ip

```

  dig api.revenuecat.com

; <<>> DiG 9.10.6 <<>> api.revenuecat.com
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 42053
;; flags: qr rd ra ad; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;api.revenuecat.com.        IN    A

;; ANSWER SECTION:
api.revenuecat.com.    247    IN    A    104.244.46.5

;; Query time: 9 msec
;; SERVER: 192.168.1.1#53(192.168.1.1)
;; WHEN: Fri Dec 13 21:18:09 CST 2024
;; MSG SIZE  rcvd: 52

```
 

The correct ip should be 

```

dig api.revenuecat.com

; <<>> DiG 9.10.6 <<>> api.revenuecat.com
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 22188
;; flags: qr rd ra; QUERY: 1, ANSWER: 6, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;api.revenuecat.com.        IN    A

;; ANSWER SECTION:
api.revenuecat.com.    21    IN    A    3.211.205.154
api.revenuecat.com.    21    IN    A    52.200.45.40
api.revenuecat.com.    21    IN    A    54.205.69.102
api.revenuecat.com.    21    IN    A    18.213.158.48
api.revenuecat.com.    21    IN    A    34.198.224.250
api.revenuecat.com.    21    IN    A    54.174.193.192

;; Query time: 2 msec
;; SERVER: 172.29.143.254#53(172.29.143.254)
;; WHEN: Fri Dec 13 21:20:48 CST 2024
;; MSG SIZE  rcvd: 132
```

You may need multiple solutions. A solution for emergency repair (as a large number of users are already suing me, it can be imagined that there will still be many negative reviews on the App Store after today). Once the temporary solution is resolved, you may need to have a new backup plan. In order to prevent such problems in the future, there should still be similar problems in Chinese Mainland in the foreseeable future.

I hope you team can find out the reason as soon as possible. I am working hard to appease the users. 

We recommend setting the `proxyURL` property to `https://api.rc-backup.com/` before initializing the RevenueCat SDK. Make sure this happens before configuring the SDK:

We are working on finding a more permanent solution.

https://www.revenuecat.com/docs/getting-started/configuring-sdk#configuration-for-users-in-mainland-china

1Purchases.proxyURL = URL(string: "https://api.rc-backup.com/")!

​@Cesar 
Really appreciated for quick response. 
I think for permanent solution is provide an fallback mechanism.  if RevenueCat SDK  can provide dynamic proxyURL configure  and error report callback that will be useful, so developer can decide to use proxy it self.