Camera control fails with rear-facing camera on Motorola Droid Turbo running Android 6.0.1

[jladley]

I've been testing my PowerApp and I have a situation where the Camera control fails.  I've set the Camera property to the numeric ID 0 and this works on Iphones, IPads, and even some Android devices like the Galaxy s7 running Android 6.0.1.  However on a Motorola Droid Turbo running Android 6.0.1 the camera control will turn black when the camera property has been set to 0.  Interestingly the front-facing selfie camera will work when the camera property is set to 1.  I've set up a slider to increment the camera property, but 0 through 5 do not operate the rear-facing camera.  Furthermore once the PowerApp attempts to set the camera id to 0 on a Moterola Droid Turbo switching back to the front-facing selfie camera results in seeing a gray square with a light gray circle and a forward arrow.  If I switch back to the rear-facing camera at this point I see a gray circle with a light gray circle and a backwards arrow.  This tells me that 0 and 1 are probably the right ID's to use on the Motorola Droid Turbo, however using the rear-facing camera will break the camera control.  It will also prevent the native android camera application from being used on the phone until the phone is restarted. Can someone from the PowerApps team confirm that 0 and 1 are the correct camera parameters to use and that this is consistant from phone to phone?  In addition can someone from the PowerApps team replicate this bug or provide a workaround.  Perhaps this affects many other Android models...  Please help!

[v-micsh-msft]

Hi @jladley,

Please take a try to set the Camera  property with 2, see if this would help to identify the Camera under your Motorola Droid Turbo device.

According to the documentation:

Camera – On a device that has more than one camera, the numeric ID of the camera that the app uses.

Camera control in PowerApps

Based on the researching, the Camera ID defined under Addroid should be:

Back: 0

Front: 1

For IOS device, the defined ID is:

Unspecified = 0

Back = 1

Front = 2

I will try to make some tests on this, and if this issue has been confirmed from my side, I will forward this to the product team.

Regards

Michael Shao

[jladley]

Thank you Michael I set up a test application with just a camera control and text box and found the following.  

In my testing I found

For IOS adjusting the camera property resulted in

Back = 0

Front = 1

Back = Any number greater than 1

For Motoralla Droid Trubo Android 6.0.1

Back = Doesn't work

Front = 1

numbers greater than 1 show message "your camera isn't set up, or you're already using it."

I have attached photos to help the product team debug.  Thank you!

[v-micsh-msft]

Hi @jladley,

Thanks for the update.

I will forward this from my side.

Besides, would it be convenient for you to share your session ID with the problematic machine?

Better with the testing.

Thanks & Regards,

Michael

[Malcyt]

Is there a solution to this problem?

I have the same problem on a Google Pixel 3XL running Android 9. I can only use the selfie camera, which does not work for my application.

[hlazier]

Try 3 or 4

[Alxdean]

Same on Samsung 9. Camera stuck in selfie mode

[hlazier · Accepted solution]

Move away from Camera Control. Too many issues and lacks the Zoom Feature.
We are using Insert>Media>Add Picture function.
This utilizes the built in cell phone camera. With this method it will be compatible with all camera modes.
To get around the appres://blobmanager/ in flow follow this:

1) Create a PowerApps Button within MS Flow
2) Create a condition that can't be true. Example 1 is equal to 2
3) In the True side create "Send an email"
4) For Attachment Name and Attachment Content us the "Ask in PowerApps"
Congrats that is it. You can now do whatever you want with the image

[Alxdean]

I tried all options from -2 to 10 with no luck

[Alxdean]

Perfect workaround. I had the same issue on a Samsung Galaxy S9+, Android 8. The Add Picture option will solve the issue for now.