Skip to content

[camera_avfoundation] Pigeon file specifies suspicious Objective-C output folders #168312

@andynewman10

Description

@andynewman10

Steps to reproduce

  1. Create a Flutter project with the camera package and a local copy of the camera_avfoundation package (I use a dependency override and a path declaration)
  2. From the camera_avfoundation folder, type dart run pigeon --input pigeons/messages.dart

Expected results

messages.g.m and messages.g.h should be generated in the (recently introduced) camera_avfoundation_objc folder.

Actual results

messages.g.m and messages.g.h are generated in the camera_avfoundation folder. This looks wrong to me.

objcHeaderOut and objcSourceOut (PigeonOptions in messages.dart) should specify ios/camera_avfoundation/Sources/camera_avfoundation_objc, not ios/camera_avfoundation/Sources/camera_avfoundation, unless I am mistaken. As the code is currently written, messages.g.m, for instance, gets generated here, where it can clearly be seen that no file is currently committed. Shouldn't it be generated there?

Using camera_avfoundation 0.9.19.

Code sample

Code sample
[Paste your code here]

Screenshots or Video

Screenshots / Video demonstration

[Upload media here]

Logs

Logs
Not relevant.

Flutter Doctor output

Doctor output
Using Pigeon 22.7.4 and Flutter 3.29.3 on macOS.

Metadata

Metadata

Assignees

Labels

P2Important issues not at the top of the work listp: cameraThe camera pluginp: pigeonrelated to pigeon messaging codegen toolpackageflutter/packages repository. See also p: labels.platform-iosiOS applications specificallyteam-iosOwned by iOS platform teamtriaged-iosTriaged by iOS platform team

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions