Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[feature request] Expose "enabled on console" boolean #76

Open
danydev opened this issue Nov 30, 2021 · 2 comments
Open

[feature request] Expose "enabled on console" boolean #76

danydev opened this issue Nov 30, 2021 · 2 comments

Comments

@danydev
Copy link

danydev commented Nov 30, 2021

While working with Bugfender, we think would be useful to add to the sdk a method to know if the current device is in "debug" mode. Or in other words if we enabled the device through the Bugfender web console.

That would allow us to send additional logs or enable additional verbose options on 3rd party SDKs, that usually we would not print/enable to avoid too much overhead.

@danydev danydev changed the title [feature request] [feature request] Expose "enabled on console" boolean Nov 30, 2021
@jgimenez
Copy link
Member

jgimenez commented Dec 1, 2021

Hi there, thanks for the suggestion. We'll take it into account for future versions.

Please note the SDK is asynchronous, meaning the moment when you log and the moment when the SDK talks to our server might not be the same. This means there is, by design, no reliable way to tell if the device is enabled or not at the moment of logging.

As a workaround, you could use a feature flag from your server, an S3 bucket or a tool like https://configcat.com.

@danydev
Copy link
Author

danydev commented Dec 1, 2021

Thanks, I agree, I think it's a nice-to-have feature even with such limitation.

Temporarily we inserted a "hidden gesture" to perform to enable those additional logs. We can do it this way since we enable bugfender's debug mode during a video call with the final customer, so we can instruct him to do so.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants