morpher | Laravel package for managing data changes | Database library

Apple Developer Documentation says:

To update a SceneKit model of a face actively tracked in an AR session, call this method in your ARSCNViewDelegate object’s renderer(_:didUpdate:for:) callback, passing the geometry property from the ARFaceAnchor object that callback provides.

The official documentation discourages using the InMemory provider for any non-trivial database queries:

we use the EF in-memory database when unit testing something that uses DbContext. In this case using the EF in-memory database is appropriate because the test is not dependent on database behavior. Just don't do this to test actual database queries or updates.

The InMemory provider won't run any joins for you which is what I was trying to do. The alternatives are using LocalDb or SqLite.

I will explain the concept here, but if you may need to see those things as a complete project you are welcome to refer to the code that I followed from a book “App Development with Swift” by Apple Education, 2019, particularly the Guided Project in the end of Chapter 3A.

Below you can see the sample screenshot. In the app you can add elements by touching the empty place on the SceneView or when your touch collides with another object (plane). Also, there is a logic for object removal

So, basically, one way to be able to remove nodes from the scene is to keep track of them in the ViewController with a special array var placedNodes = [SCNNode](). That way you can clear the view from all the nodes (for example by creating Button Action "Clear")

Another nice addition that you may grasp from Apple's developers is utilizing not a tap gesture recognizer, but by overriding touchesBegan/touchesMoved, this may give you more flexibility in terms of what you can do with touch gestures, particularly, you can get its location in the SceneView by calling touch.location(in: sceneView).

So, touchesBegan/touchesMoved allow you to locate the places that were tapped by user. This may be used for adding/removing objects on the SceneView

Hope that this will help!

Setting android:launchMode="singleInstance" to the activity will cause only one instance of that activity to run. Meaning when your activity has been opened once via deeplink that instance is running. When you open the second link you expect your UI to get updated but since the instance was still running the activity's onCreate does not get called, which is why you see the views from earlier link.( Another point is when singleInstance is set it won't allow any other activity in stack.)

You can get more info in the official docs .

Now, even though onCreate is never called but onResume and onNewIntent methods do get called when singleInstance is set. Though onNewIntent is usually mentioned to work with singleTop, from my experience it does get called on when any of the three single flags are set.

So you need to override either of the two and write the code to update your UI in these. Also note that onResume does get called when your activity is created the very first time after onCreate so if that's where you place the code you might want to optimize to avoid reloading the same thing twice and everytime onResume gets called like after returning from background. In which case onNewIntent() does seem like a better option.

Hope this was of some help to you.

Update: As requested, you can find the edited code below

Could be an issue with the transactions but it's hard to say without more context.

In applySomeChanges you can try to use an explicit transaction

There could be three potential problems causing your model to show hard edges at animation:

• insufficient number of polygons in 3D models (low-poly models)
• source and target models have different number of polygons
• models have lamina faces, non-manifold geo, or non-planar faces

Supposedly, you may have all the listed problems at once or just one of them.

you are force unwrapping the result of Budle.main.path..., since this is failing it means your resource is not loaded correctly.

Make sure your sound files are bundled with your app. You can check this by going to your project settings, then under "Build Phases" add the files to the "Copy Bundle Resources" section if they are not already there.