Subscription API Test Fail
Hi, I am unable to test IAPs. I have followed this guide https://developers.meta.com/horizon/documentation/unity/ps-iap-test My organisation is verified, I have a test user, which can be granted test add-ons. And I can consume them using the API on my server. However, I have tried multiple times to buy a subscription through the horizon mobile app, logged in as the test user. I used the card details provided in the documentation above, and also added the cards using the test user menu "manage test cards" modal. I always get the same message, in the test menu and in the mobile app purchase. Not sure what to try next.
Detect what release channel the application is running on or get current release channel.
Is there away to tell if an application build is running on ALPHA/BETA/ … etc. I'd like to test out different content depending if it's on a given release channel, something like get current release channel. This way I can build the application once and migrate it down the release channel pipeline without having to rebuild for each channel if all I'm doing is changing a pointer.
Not Being Able to Use Platform SDK on Quest Without Pitch, Is this True?
I bought the quest excited like a baby to begin developing and messing around, reading that it will be completely open to developers. My understanding was that only if you want to get in to the store do you have to a pass the pitch process. However after a few weeks of getting my development pipeline set up I seem to have run in to a brick wall. Access to the platform SDK. That is the whole reason I dove for the quest, the ease of avatar importing, the rooms etc, just to develop and collaborate with my friends. To get comfortable with the the tools. And then maybe start working on a production pitch. Needless to say I am now enraged. Probably in an irrational manor. But please, can we talk about this? Am I wrong, is there a way to do it? I've essentially gone from a quest evangelist to a depressed dev kicking a can. I was like, really fucking excited for this. using oculus quest with unreal engine oculus source fork 4.22
