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
-
FYI @stevenxu there is another typo on top, it says v1.23.0 (should be v1.24.0)
-
Likewise, and thanks for the clarification!
-
@stevenxu i might be hallucenating, but im seeing on snap's website that there is no lens studio 4.48? Only 4.49 (and version before that was 4.46) https://ar.snap.com/download/v4-49 Is this a typo or am i missing something?
-
For those running into issue where you need to know when the agreements modal is showing, my solution was to use method swizzling to detect whenever a VC is being displayed (from the host vc that's presenting the agreements modal). Hereis code below: @objc func didPresentModalViewController() { SCLogging.infoLog("A view…
-
Thanks @stevenxu - A suggestion that could be greatly helpful in upcoming sdk versions: Being able to know when the Agreements modal is displayed (not only dismissed) LMK thoughts on it!
-
The expected usage would be that on every new installation of the app, the terms alert will appear for the user (but this does not seem to be the case).
-
@ForumChris thanks so much, that was the reaffirmation I needed it to continue working on it until I figured it out – which I have thankfully! What was useful (and lacking in docs) was where to use the custom API Provider in the iOS app (it must be done during setup when passing the various providers). After some more…
-
Thanks, really hoping to solve this one! 🙏🏻
-
Bumping :disappointed: Also, can anyone confirm this currently is working? Have yet to find one person who has implemented
-
@"Pico Alta" to save you time - my issue was the the lens was published by a version of Lens Studio which was not yet supported by the CameraKit sdk being used in the application. As noted, there is a delay sometime between lens studio release and camera kit release. LMK if that helps!
-
@ForumChris what do you think? could use your help!
-
Got it to work! After some more attempts, I ended up creating a custom lense media provider, and implemented the protocol methods. Then, you can pretty much handle things however you want. DM me if need help on this!
-
Seem to have found the missing piece - here is the info: /// Metadata for a media assettypedef struct { // If the asset is an image with a face present, a rect specifying the position of the face. Otherwise CGRectZero CGRect faceRect;} SCCameraKitLensMediaPickerAssetMetadata; For my use case, I believe it can be any value.
-
I've been able to create my own provider class that conforms to LensMediaPickerProvider. My last issue now, is to understand how I can create/get a SCCameraKitLensMediaPickerAssetMetadata value/obj to pass to the media picker provider delegate in the provider requestedApplicationOfOriginalAssets method. There really isn't…
-
Perhaps I found it - could it be this? NS_SWIFT_NAME(LensMediaPickerProviderMediaApplicationDelegate)/// Delegate responsible for applying media to a lens. This should not be implemented directly./// @note If you create a custom provider, you'll need to call the methods here from your provider. See notes on///…
-
Thanks @arashp - that's what I did, I create my own versions of the classes and was then able to modify the output size accordingly and make more customizations. That wasn't clear from docs initially but glad it works now :)
-
This was my issue! Working on downgrading Lens Studio now (struggling with finding where I can download older version though). Thanks Ankit
-
Update #2: I then added another Lens from the same developer, however this time - this newly added lens DID not appear via app. So now I've thoroughly troubleshot this issue and it appears to be Lens-related, not Lens group or Lens developer. Help!
-
Update #1: I was able to add new lenses via a "User Profile" source, to test out and see if it would work. I added a lense to the same Lense group which has been loaded into the app, and surprise - this new lense DOES appear. Perhaps there needs to be some approval as a "lense developer" to have your lenses used by other…
-
As a follow up, I've currently been able to get desired functionality doing two things: * Initialising the camera view controller with the relevant properties let lensesConfig = LensesConfig(cacheConfig: CacheConfig(lensContentMaxSize: 150 * 1024 * 1024)) let cameraKit = Session(sessionConfig: nil, lensesConfig:…
-
Was solved. Thanks!