I am attempting to publish my OAuth2.0 app but I am getting rejected due to the requested scopes. My use case closely matches the “Creation & Productivity Tools” category but is getting rejected because it is (mistakenly) categorizing my application as “Analytics & Insights Tools”.
What is the driver behind category selection?
Hi, did you review this? https://en.help.roblox.com/hc/en-us/articles/37924211313044-Creator-Third-Party-App-Policy
What is your app about?
I have.
This is the description for my app: * allows you to view and manage assets, manage your group members and roles, manage experiences/places, and send/receive updates from your groups.
It is an iOS app (testflight beta) which takes advantage of the APIs for viewing and managing groups, experiences, and assets.
The original iteration and app description did fit the analytics category but it is completely different from when I first created it.
edit: I have not made any requests with the additional scopes yet, I have been using just the openid and profile scopes along with mock data if that makes a difference.
Our moderators need to review the application, so I recommend building it out more first before sending it for review again. We don’t pre-approve skeletons of applications.
Got rejected again for wrong category. On the website provided there is a TestFlight link available as well as screenshots showing the apps functionality.
Got it, we’re looking into it.
@Hooksmith Hey, not sure if you check mentions, but I also am running into this issue.
I am currently self hosting an authentik instance, and for it I wish to enable Roblox as an enrollment way into the application.
Inside of authentik, I have set it up so when the user gets redirected back, authentik, via a custom python script, checks whether the user meets the requirements to enroll, by checking the user’s groups - aka checking whether the user is any of the listed groups, and if so, which rank he is.
This application grants very sensitive access based on what groups you are in on Roblox - including PII - so rejecting my application for this puts that at risk.
My application gets categorized as “Account Linking Tools”, which while it is not incorrect, I cannot properly bind user accounts unless they also allow me to check what groups they are part of. The fact that applications get automatically denied because you are using scopes that are hard set depending on a mere few types of applications is bizzare to me, and I’m hoping you can help me out (:
Cheers!
Hey, please use the appeal process if you think your app was incorrectly denied or if you believe the determined category is incorrect. If you hit issues still and believe there is an issue, please file a bug report.