Exploring differences in 'Create File Object' (image) between iPhone and Android

Hi, cummunity!

When testing the “Create File Object” function with different settings on Android and iPhone devices, I noticed some disparities in behavior, particularly regarding the “Use Device Camera” option. Here are my observations:

With “Use Device Camera” Disabled:

  • Android: The process takes you directly to the image library, bypassing the option to take a photo.
  • iPhone: It offers a choice between accessing the “Image Library” and the option to “Take Photo.”

With “Use Device Camera” Enabled:

  • Both Android and iPhone: You’re led straight to the camera interface, without the opportunity to select from the image library.

From these tests, I’ve deduced that disabling the setting provides more versatility on the iPhone, as it allows both library access and camera use. Conversely, on Android, you’re restricted to one mode of operation at a time.

I’m curious to know why there’s a variation in functionality between iPhone and Android devices. Has anyone else encountered this and found a solution to enable both photo upload and capture on both platforms? Could utilizing two separate “Create File Object” actions with different “Use Device Camera” settings be an effective workaround?

Hi there!
Good observation!
We don’t have much control over these API’s unfortunately as they are design choices made by developers of these operating systems. In android the default behaviour is to open the image library when selecting a file, whilst in iOS the the default behaviour is for the user to choose between accessing the image library or taking a new photo.
You could, however, check the users operating system from App variables and determine the behaviour in the action that way.

Hi, and thanks for the reply!

Using the App variables is a good tip for a workaround! I will us that to determine the behaviour for the users.