#LENS Canvas "freeze" in production when switching lenses (works in staging + localhost)

24 messages · Page 1 of 1 (latest)

sonic hinge
#

Hey everyone! Running into a weird issue with Camera Kit Web and hoping someone has seen this before.

The Problem:
When switching to a lens in production, the canvas freezes visually (but works perfectly in local host + staging).

Let me reiterate, when running this locally, it works fine as expected.

Setup:
Single-canvas approach (using session.output.live)
React app with Camera Kit integrated
Lens loads successfully, play("capture") completes without errors
Issue only happens in production, not staging

Has this happened to anyone before? It seems to be related to the 2 render targets perhaps, the "live" output and the "capture" one

Again, weird is that it's only happening on production - Maybe it's happening to someone else too before I lose my mind! lol thanks

Relevant Docs:
Camera Kit Web SDK: https://docs.snap.com/camera-kit/web/get-started
Canvas rendering: https://docs.snap.com/camera-kit/web/guides/rendering

  1. Using Chrome and it's reproducing for me but on Safari it's not happening.
  2. A friend using Chrome - checked as well, NO ISSUES for them
    3, Firefox WORKS for me, same computer

THREE different browsers THREE behaviors?!

sonic hinge
#

Looks to be related to play("capture") causing a FREEZE of the canvas that was showin LIVE?

sonic hinge
#

await this.session.play("capture") => FREEZE (only on production) WTF

mossy moat
#

Safari has a lot of limitations and rules, and you need to figure out what's causing the issue. Typically, it's sound issues.

sonic hinge
#

im using chrome though

#

It's weirdly working on Safari, actually not on Chrome lol, but not for me at least..

And there seems to be that discrepancy between staging and production.

I'm almost sure there's a bug somewhere on the SDK side

#

Heres a video showing it clearly @mossy moat , remove the [] in the URL

https://[]pub-3c65365ae401453196a7ffd04f58c0cc.r2.dev/1114%20(2).mp4

mossy moat
#

When you're working locally, you have no problem accessing the camera via HTTPS, but when you're in production, you might have problems with HTTPS, and you also need to specify a verified domain in Snap Production Stage.

sonic hinge
#

ohhhh wow okk intresting..

#

But it's partially working, that's what's weird.

#

I'm checking to see that angle now, will update shortly

#

"verified domain in Snap Production Stage" - Where is that done?

#

I've got all the different portals open lol. I'm ready to operate!

#

Also, it works fine on my staging server when deployed too.. So it seems only on when it's a production camera kit or whatever that's it happens.

#

there is no way to add WEB here!

#

@mossy moat

#

lol, so I'm starting to understand the issue... Why can't I have an app that's already for mobile also for web?

The question is now I have to create two completely separate apps. One for web, one for mobile... ?!

#

Although it was working for me fine, that's really the only bug, so that's super interesting that it works.. with an exception...

So i guess @mossy moat What is advised to do in my situation here?

mossy moat
#

@sonic hinge I work on the web and I haven't noticed any problems, everything works fine for me.

#

Maybe there are some problems with your API?

sonic hinge
#

No, the issue is that I have a mobile app. Everything is already set up and I also wanted to add web support.

But these seem like two distinct apps on the platform.

So I was using all of the credentials of the mobile app on the web

#

Since camera kit on web is a new feature, I obviously didn't have it up until recently. And I thought adding it would be straightforward in that sense, but it looks like I need to add a completely separate application.

Does that make sense?

mossy moat
#

It's hard for me to answer because I only use the Web , for iOS and Android I use native ARKit and ARCore

sonic hinge
#

got it, I thought you were a cat's nap, but I guess not. my bad