I agree - and security-wise prefer it to the pre-hook solution we were considering...
We are looking into it.
Jake - I've sent you a question in the support chat - wondering what the timelines for your app are...
Paul.
You can bypass the peer dependencies by adding --legacy-peer-deps flag to your npm install. After modifying package.json, then use npm-install-peers to install the rest of peer dependencies.
Solved:
IDK if this is the right approach but I am using brainCloud's LitJson and JSONMapper. I will map out the things I need and put it into an object of variables I chose to parse out.
Update:
Authentication seems to be going well. I can automatically sign user in using ANON, and attach an email and pass.
I can also log a user in using existing email and pass and getAnonID and store it and proceed to use that AnonID to use AnonID on startup for silent authentication.
However, if user selects anon account but then the user decides to log into an existing email and pass account, how would I go about deleting the new ANON account the user decides to "throw" away?
(Post the answer from brainCloud chat channel)
Actually, there is a workaround that you can perform the tournament rewards adjustments,
Turn off the auto claim
Add a post-hook to Authenticate instead <- where auto-claim would normally run
And in the post-hook look to see if they have tournament rewards, and if they do, claim them there - performing any award adjustments that need to be made.
@David-St-Louis-0
On my last question, can you restrict API calls to only be from a specific web domain or mobile app is? Google Api's allowed to restrict calls to firebase to be specifically from an web domain, or the specific app ID's.
Another way to ask it, is there any way to restrict API calls to from a specific location?
Thanks again,
-Chad