Hi Michael! @bakura10
Not sure if it’s related to app-owned metafields, but they mentioned that it can’t read runtime context. And disclaimer for the rest of this post - I have not tested anything with app-owned metafields..
Another possible related post: Visible_if doesn't seem exactly compatible with dynamic data sources - #2 by misha
Not sure if the following will even work. But having value_from_metafield
visible and then assigning that field a dynamic source linked to your metafield, should at least. But I see that wouldnt work from a theme developer perspective…
{
"type": "text",
"id": "value_from_metafield",
"label": "Value from app.metafields.foo.bar"
"visible_if": "{{ false }}",
"default": "{{ app.metafields.foo.bar }}"
},
{
"type": "header",
"content": "app.metafields.foo.bar has a value!",
"info": "some text...",
"visible_if": "{{ section.settings.value_from_metafield == blank }}"
}