Post not yet marked as solved
The feedback ID is FB10566496.
Thanks,
Cliff
When configuring the app id on the developer site there are two tabs: "Capabilities" and "App Services". Ensure that WeatherKit is enabled in both of these.
There is no issue with visualBounds. My entity had an unexpected child that was throwing off the dimension caculation.
That's great, arthurfromberlin. Thank you!
Post not yet marked as solved
dup response due to forum web site weirdness -
Post not yet marked as solved
Thank you. It doesn't center the object but with your help I'm closer to that goal. Thanks again!
Post not yet marked as solved
Thanks for the explanation, gchiste.
Would it be possible to provide some example code to determine the target transform? While I understand your answer, I'm flailing a little trying to make it work.
Thanks again,
Spiff
The complete answer is that ARView has a cameraMode property which is equivalent to the argument in the initializer.
arView.cameraMode = .nonAr // for example
How I missed this is beyond me :-)
Although I marked this as the correct answer it is in fact incomplete. This changes the background but the camera is in fact still active, while you move the camera, the relative orientation of the device changes.
This can be achieved by setting the background in the environment:
// disable camera
arView.environment.background = .color(.white)
// enable camera
arView.environment.background = .cameraFeed()
Post not yet marked as solved
Hi,
I can't reproduce it myself, I'm just seeing the crashes in Firebase. Is there a workaround that I might employ? This will cause me to pull back a feature from production. Is there any documentation of the bug? Thanks!
Post not yet marked as solved
It's January 2, 2022 and this still occurs.
Post not yet marked as solved
This has been addressed in a recent update and works correctly now.
