Heads up! We're sunsetting this forum to streamline our community space.
join us on Discord for support, updates, and all things Snap AR! See you there!
join us on Discord for support, updates, and all things Snap AR! See you there!
Comments
-
Thanks for looking into this, @stevenxu Here is what the test page renders for me. no smoke unfortunately. It works in LS and Snap so I feel like I am missing something obvious. I am running this in a React App, so I am going to try this in a more vanilla JS setup. I can also share the project files if you need them
-
okay @JacekC I can confirm I am getting a good token, and doing the web flow from the docs, but I am getting a 403 when attempting this call: push2Web.subscribe(token, session, cameraKit.lensRepository); https://api-kit.snapchat.com/com.snap.camerakit.v3.PushToDevice/ListenLensPush The above repo is now public. Line 120 in…
-
@JacekC Your example works. It must be user error :). I'll let you know if I can't get it working. Thanks for looking!
-
using staging keys and the staging OAuth clientID's are returning a 401 for me :disappointed: Not sure what I'm missing repo for the curious: https://github.com/s-r-jones/camera-kit-web-test
-
Ideally you want to be using environment variables. Often times you can set these up with your host. Many popular hosts have key management features or services. https://www.smashingmagazine.com/2023/05/safest-way-hide-api-keys-react/
-
@arashp sorry for the delay in responding I somehow missed the notification. I will try your suggestion today. My test scenario is set up like this: Created custom landmarker of my living room with default custom location template. No changes to the template other than using my test location ID. Thanks for your help, ya'll…
-
thank you @stevenxu !
-
Thanks, Michael!
