We’ve confirmed that in the "SingularSDK.cs" file included in the Singular SDK, the method "BuildIOSPurchaseAttributes" sends the product’s localizedPrice under the "pp" attribute.
However, in the case of "BuildAndroidPurchaseAttributes", the product’s localizedPrice is sent under the "r" attribute. Based on our tests, the iOS side also needs to send the price using the "r" attribute in order for the in-app revenue to be recorded properly.
This issue requires investigation and appropriate action.
We’ve confirmed that in the "SingularSDK.cs" file included in the Singular SDK, the method "BuildIOSPurchaseAttributes" sends the product’s localizedPrice under the "pp" attribute.
However, in the case of "BuildAndroidPurchaseAttributes", the product’s localizedPrice is sent under the "r" attribute. Based on our tests, the iOS side also needs to send the price using the "r" attribute in order for the in-app revenue to be recorded properly.
This issue requires investigation and appropriate action.