RevenueCat project setting, I keep entering my In-app purchase key configuration but it does not allow me to select “save changes” and when I come back to the same setting page, I don’t see my entry in this section persisting. Has anyone countered this?
Userlevel 3
+5
Hi! Are you also making sure to add the Issuer ID to the appropriate field? It requires you to do so in order to save the in-app purchase key configuration.
+4
+4
Same as Apple Small Business Program start date. Even when I enter the date, the “Save Changes” button is grayed out and when I come back to the page, the field is blank.
Userlevel 3
+5
I can’t get the same behavior in Chrome but I was able to replicate it in Safari (which is what Victoria was using).
I _think_ this issue might stem from how the In-App Purchase key is now required. Apps that were created prior to key being required now get an invalid form on page load. Once we got the key upload for Victoria, the rest of the forms seemed to work okay.
I’m going to bring this back to my team since I think we own this to see what they say 🤷♂️ This specific issue is resolved but I’m not confident that we won’t see this error again 😇
+4
Thank you so much Josh!
+4
I had problem with trying to edit other fields as well, Josh. Might have stemmed from trying to upload the key earlier, but seemed like none of the field changes were detected by save button
+4
I am having this problem today!
I received an email to say my In-App Purchase key is invalid (I don’t know how that happened!).
Anyway, I upload a new key and replace the Issuer ID, but the Save button is always greyed out. When I refresh the page, it always has my old key.
Please advise how I can get my new key to save.
As of 5/31/24 this issue still persists. I am unable to access any IAPs or subscriptions from my apps because I am unable to save the .p8 key.
please fix this asap!
As of 5/31/24 this issue still persists. I am unable to access any IAPs or subscriptions from my apps because I am unable to save the .p8 key.
please fix this asap!
According to RC support, the temporary solution is to also integrate the App Store Connect API Key, they are aware of the issue.
Userlevel 3
+5
A fix to the dashboard has been deployed 🚀
There were validations for the existence of some App Store Connect API Key fields that shouldn’t have been happening. Sorry for any issues involved with this!
Reply
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.