Closed acmancera closed 11 months ago
It seems this was not a problem with the SDK itself, but with our other tracks not being up to date. If anyone else gets to this issue, check that all the tracks for your app in the play store are updated before trying something else.
@acmancera How do you resolve this issue?
I have upgraded to the latest version "2.15.0"
, but I noticed that our client initialization code sets collectDeviceId
to true
, does it solve this problem by removing this or setting it to false
?
In our project we actually don't have that variable set in our initialization and it's up in the Play Store today, so if you're still seeing this error that might be related.
exactly, we set that variable to true incidently. Unsettibg that just works. Thanks
On Fri, Aug 4, 2023 at 04:37 Alexandro C Mancera @.***> wrote:
In our project we actually don't have that variable set in our initialization and it's up in the Play Store today, so if you're still seeing this error that might be related.
— Reply to this email directly, view it on GitHub https://github.com/segmentio/analytics-react-native/issues/865#issuecomment-1664614931, or unsubscribe https://github.com/notifications/unsubscribe-auth/A3WDLESFUARWCDBXP7YXBDDXTQDXNANCNFSM6AAAAAA3AGGNCM . You are receiving this because you commented.Message ID: @.***>
We just received that our app has been removed due to this issue:![image](https://github.com/segmentio/analytics-react-native/assets/111389799/44a1751e-de79-49a5-900a-028a688af11f)
We're currently on the newest version of the react native package, and can't find the problem for this in the code.
analytics-react-native
version: 2.15.0Steps to reproduce
Build the app using analytics-react-native version 2.15.0 and then deploy it to the Google Play Store.
Expected behavior
The app should be published without any problems.
Actual behavior
The app is rejected and/or removed from the Google Play Store because of it is not compliant with Google Play Policies.