Kord Extensions•10mo ago

Sentry DSN not detected

So I was redoing how I start the Sentry extension, to use enableIfDSN instead of doing the null check myself, and I noticed the Sentry extension was failing to initialize, and reverted it and it is still failing. So I don't know if this could have been caused by the latest changes? My bot is unable to start now if a Sentry DSN is set. I put a breakpoint in SentryAdapter.init and I can see that the DSN is available: Then on Sentry.java, line 187, there is a applyOptionsConfiguration function, it takes optionsConfiguration (which still has the settings there) and options, which is empty. In the next call, init(options, globalHubMode), options is still empty. And this is causing the error:

Instance creation error : could not create instance for '[Singleton:'com.kotlindiscord.kord.extensions.sentry.SentryAdapter',binds:com.kotlindiscord.kord.extensions.sentry.SentryAdapter]': java.lang.IllegalArgumentException: DSN is required. Use empty string or set enabled to false in SentryOptions to disable SDK.

Instance creation error : could not create instance for '[Singleton:'com.kotlindiscord.kord.extensions.sentry.SentryAdapter',binds:com.kotlindiscord.kord.extensions.sentry.SentryAdapter]': java.lang.IllegalArgumentException: DSN is required. Use empty string or set enabled to false in SentryOptions to disable SDK.

Reverted to 1.7.0-SNAPSHOT made it work again. Even tried to upgrade to 1.8.0-SNAPSHOT again to see if the dependency change would make it refresh, but no 🙃