We have an AR app in the stores that allows people to drop virtual “time-capsules” in the real world so you can place any kind of digital content at any location.
The AR part of the app uses world-tracking only, so we’re using the rear-facing camera for this. However, to let people shoot selfies (and place them as memories), we also need to switch to the front camera temporarily.
Currently, the only way to do that with AR Foundation is to enable face-tracking (Face Manager). However, enabling this package also enables the TrueDepth APIs, which we don’t actually need.
Because of this, Apple keeps rejecting our app. Their argument is: You’re not using TrueDepth features, so you have to disable that API. However, there is no other way to switch the cameras in AR Foundation, so we’re pretty stuck. We thought about implementing a face filter (like a butterfly on your nose every time you shoot a selfie), just to please Apple, but that would be quite ridiculous to the users.
Does anybody know another way to switch cameras if in AR mode, or how to convince Apple that this is a limitation of Unity we cannot resolve?
I got a similar message by apple, I wasn’t using TrueDepth so I simply removed it. But if you use it, you should try to explain to apple where do you use it and, in your case, why do you need it.
Good luck
@dnlcl I tried explained this to them a couple of times, but they just keep rejecting the update. I will now escalate this to their higher level reviewers, as I am in a complete deadlock here. We definitely need access to the front camera (to let users shoot selfies), which forces us to activate FaceManager and thus TrueDepth, but we don’t need any TrueDepth functionality. Removing the face tracking package is not an option for us, unless we’d find another way to access the front camera while using ARKit at the same time. We have tried, but without success. There was a feedback from a Unity dev in another thread that the problem lies in ARKit, so they can’t do much about it. And we’re kept in limbo :-/
I understand, it’s not a nice situation. You can also try to ask to the apple dev forum (maybe I shouldn’t suggest other forum than this), so you can hopefully save time or get more solutions about it.
@dnlcl Thanks for that hint, will do! Funny side-note: Apple accepted the app after I wrote them another elaborate explanation, and I was very happy about this. But then I noticed that this version had a bad bug, which I then wanted to correct, so I filed another update. And this one got rejected again, because of this. So I am stuck with a version now that is not even working correctly. This is driving me nuts.