Question about Key Generation and Builds
We have a Build that has passed submission. We are about to submit a new one but would like to generate some keys. Can we specify which build the keys will download or will this always give the user the latest submitted build to get approval? If the keys are build specific are these no longer valid when the new version is approved? Also if a game is on applab but moving to the store, would the game need to be moved over before you are able to generate the keys?
Users cannot redeem Product Key
Our users cannot redeem the Product Keys created from the developer dashboard: https://developer.oculus.com/manage/applications/[appid]/oculus-keys/ The previously working process was to visit page: https://secure.oculus.com/redeem-code/ and enter their product key. Now the field will not accept the full product key which is 5 groups of 5 alphanumeric characters plus 4 dashes (29 chars). The input field has a max-length of 25 so the product key gets cut off and is rejected for being invalid.I can't see any add-on keys on my developer dashboard
Hi, I'm trying to work with Add-On keys for our game. I've generated few hundred keys and was able to download them, but they are never appearing on my side in a Keys => Add-On section, I've attached a screenshot how it's looks like on my side (guy from tech support was able to see the keys on his side and asked me to create a topic here, since it's looks like a dashboard bug).
Unable to track Meta Keys
We're planning a rolled out release of our App Lab app using Meta keys to give to our early users. We thought we would be able to track various campaigns with different sets of keys from the developer dashboard, but our test keys are not showing up at all. Is tracking a feature only available once the app is officially released on app lab? Or only for Quest store apps? Or is it simply not available?
