Titanium JIRA Archive
Titanium SDK/CLI (TIMOB)

[TIMOB-24036] Camera viewport is sized wrong if showControls: false w/ sdk 5.5.1.GA and iOS 10

GitHub Issuen/a
TypeBug
PriorityNone
StatusClosed
ResolutionNot Our Bug
Resolution Date2016-10-15T13:32:25.000+0000
Affected Version/sn/a
Fix Version/sn/a
Componentsn/a
Labelsn/a
ReporterStephen Feather
AssigneeEric Merriman
Created2016-10-14T14:53:12.000+0000
Updated2017-03-21T20:50:24.000+0000

Description

Expectation

That camera viewport use the entire screen

Actual

Camera viewport only uses a portion of the screen
Ti.Media.showCamera({
    cancel: function() {alert('camera cancelled');},
    error: function() {alert('camera error');},
    success: function() {alert('camera success');},
    mediaTypes: [Ti.Media.MEDIA_TYPE_PHOTO],
    showControls: false
  });

Attachments

FileDateSize
cameratest.zip2016-10-15T13:32:36.000+000033051

Comments

  1. Stephen Feather 2016-10-14

       showControls: false
       
    !http://content.screencast.com/users/Stephen_Feather/folders/Jing/media/23cc2afb-71e1-40f3-8704-495b368616c0/00000035.png!
  2. Stephen Feather 2016-10-14

       showControls: true
       
    !http://content.screencast.com/users/Stephen_Feather/folders/Jing/media/5e6f2729-01b5-4655-b239-1839ef209e2f/00000036.png!
  3. Hans Knöchel 2016-10-14

    This is very likely a native behavior, see the screenshots in [this](http://stackoverflow.duapp.com/questions/39124794/uiimagepickercontrollers-cameraviewtransform-is-ignoring-scaling-and-transla/39342257#39342257), [this](https://forums.developer.apple.com/thread/60888) and [this](http://stackoverflow.com/questions/2674375/uiimagepickercontroller-doesnt-fill-screen) thread regarding it. So you might want to use the suggested 2D-transformation if you want to prevent the scaling.
  4. Hans Knöchel 2016-10-15

    Resolving issue, please see the attached native project to reproduce the issue natively. You can work around this by applying a 2D-matrix as discussed in the above-linked threads.
  5. Lee Morris 2017-03-21

    Closing this ticket as the issue is not our bug.

JSON Source