You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[pigeon] Expose custom object IDs for testing on Linux #156100
The way custom FlValue objects work on Linux, the ID they use is part of the API contract (to identify them, since there's no inherent runtime typing), but currently those assignments are an implementation detail of the generated Pigeon code. That's an issue for native unit tests, because in order to call fl_value_new_custom_object to make arguments to call handlers, the right ID is required.
This isn't high priority since it can be worked around by hard-coding the IDs in the tests, but that means that tests are subject to breakage when updating the Pigeon generation, which is obviously not ideal. We should make public constants for each of the Pigeon-generated class IDs, so that tests can be written using the constants, and get any updates automatically.
This isn't high priority since it can be worked around by hard-coding the IDs in the tests
It turns out this doesn't only affect tests; returning custom types in collections also requires being able to call fl_value_new_custom_object, because collections have to hold FlValue instances on Linux.
This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug, including the output of flutter doctor -v and a minimal reproduction of the issue.
Activity
[-][pigeon] Expose custom object IDs for testing[/-][+][pigeon] Expose custom object IDs for testing on Linux[/+]stuartmorgan-g commentedon May 21, 2025
It turns out this doesn't only affect tests; returning custom types in collections also requires being able to call
fl_value_new_custom_object, because collections have to holdFlValueinstances on Linux.6 remaining items
[pigeon] Use a const for custom type ids for gobject generated files …
[pigeon] Use a const for custom type ids for gobject generated files …
[pigeon] Use a const for custom type ids for gobject generated files …
[pigeon] Use a const for custom type ids for gobject generated files …
[pigeon] Use a const for custom type ids for gobject generated files …
[pigeon] Use a const for custom type ids for gobject generated files …
8929a93 [pigeon] Use a const for custom type ids for gobject generate…
Roll Packages from 03a6abb to 25d4fa4 (5 revisions) (#170743)
[pigeon] Use a const for custom type ids for gobject generated files …
github-actions commentedon Jul 1, 2025
This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug, including the output of
flutter doctor -vand a minimal reproduction of the issue.[pigeon] Use a const for custom type ids for gobject generated files …
[pigeon] Use a const for custom type ids for gobject generated files …
[pigeon] Use a const for custom type ids for gobject generated files …