They can ban the app from app stores for using any non-system interface to request permissions, like they do for payments.
That is a very normal practice on Android. The fact that Snapchat decides that pestering the user for the permission is acceptable I find to be a very strange design decision.
If you have an interface that looks like "requestPermissions(...)" or something like that and have a case where users can reject permissions forever without nags, then how do you handle users who inadvertently deny permissions forever? One solution is to just nag forever, if you can.
Another workaround is to enable permissions manually through settings, but you need to make errors loud and obvious with workaround instructions and people interpret the issue as a bug in your code rather than a feature of the platform.
This is a problem on MacOS, just as an example.
v11.25.0.29 Beta for me
> in house permission request
That's what I had feared. I'd expand the scope of "the system" to include Play store rules.
Why they haven't done so already is a mystery to me.
The issue is that Snapchat (in your case, as I don't have this happen on v11.23.3.36) is told that they wont get the permission and wont be able to ask for it either.
And so they perform their own inhouse permission request to you.
There is nothing that can be done from the system's point of view for that.