dskuza
commented
6 days ago I don't think it's exactly what you're looking for, but there are logs you can enable that log to console certain events as things are happening. You can enable them via RiveLogger.isEnabled = true. We've been talking internally about the "best" way to export the usable exports from .riv files; there are a few options, so we're investigating a few to see what works well cross-platform.
I'd love to have a debug option that allows printing all artboard names (and subartboards), assets names, inputs, text runs and their paths, etc.
It's not always obvious what is available or if the riv file is configured correctly. Printing them in code will help ensure the right paths and options are used and help with debugging any issues with layers that may not be exported correctly.