It looks like orbot is using a new enough version of tor and snowflake to take advantage of this feature, but when I connect I still don't see the log messages in the tor log. I think they might be getting lost within iptproxy.
This isn't urgent, but I'd recommend this feature because it often informs us on how to modify the snowflake bridge line by region and it could be useful for the orbot support team as well.
From @cohosh here: https://github.com/guardianproject/orbot/issues/741
To help users debug snowflake connectivity issues, we recently added a feature to send snowflake connection messages to the tor log (see https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snowflake/-/issues/40062, https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snowflake/-/issues/40044). This has been very useful for us in figuring out how and where snowflake is failing from user reports, since users can easily copy and paste the log from the tor browser app. Here's an example of us using this feature recently to unblock snowflake in TM.
It looks like orbot is using a new enough version of tor and snowflake to take advantage of this feature, but when I connect I still don't see the log messages in the tor log. I think they might be getting lost within iptproxy.
This isn't urgent, but I'd recommend this feature because it often informs us on how to modify the snowflake bridge line by region and it could be useful for the orbot support team as well.