Unexpected behavior with getProducts() within Config prior to activation

I’m seeing some interesting behavior right now where the getProducts() call is rejecting with an error “Bits transactions are not supported in the current context” during configuration prior to ‘Activating’ the extension. I have seen this within my own extension during Assets Uploaded, and was able to resolve it by activating the extension & heading back to configuration.

Not sure if this is expected behavior, but it would be ideal to be able to configure the extension & see Bit Products prior to the Content Creator activating the extension.

Let me know if you’d like any more information.